[PEPr] Comment on RFC::RFC_PackageVariableNamingConvention
| From: | Matthew Weier O'Phinney | Date: | Fri, 05 Aug 2005 03:40:38 +0000 |
| Subject: | [PEPr] Comment on RFC::RFC_PackageVariableNamingConvention | ||
| References: | 1 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-39242@lists.php.net to get a copy of this message | ||
Matthew Weier O'Phinney (http://pear.php.net/user/weierophinney) has commented on the proposal
for RFC::RFC_PackageVariableNamingConvention.
Comment:
I am concerned by the phrase "if there is no strong case for the use of
lowercase_and_underscored variable naming" -- what is considered a
'strong
case'? who decides whether the case is strong?
I can thing of a number of scenarios where underscores would be
preferable:
when trying to separate acronyms (XMLHTTP vs. XML_HTTP, for instance --
and
don't get me started with changing that to XmlHttp), or when porting a
class
from another language to PHP -- where there may be a desire to keep the
variable
naming the same.
I agree with the idea of keeping variable naming consistent within a
class, but
in the end, I think such decisions are the realm of the individual
developer.
Since submissions need to be object oriented anyways, the public API is in
the
method names -- and these are already governed by the CS.
Proposal information:
http://pear.php.net/pepr/pepr-proposal-show.php?id=282
--
Sent by PEPr, the automatic proposal system at http://pear.php.net