Re: [PEPr] Comment on RFC::RFC_PackageVariableNamingConvention
| From: | Stefan Walk | Date: | Sat, 06 Aug 2005 01:23:15 +0000 |
| Subject: | Re: [PEPr] Comment on RFC::RFC_PackageVariableNamingConvention | ||
| References: | 1 2 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-39262@lists.php.net to get a copy of this message | ||
2005/8/4, Joe Stump <joe@joestump.net>:
> > I understand that's what Java does, but if I wanted to be writing
> > Java code,
> > I would be. PHP != Java, and I think the language (and PEAR) is mature
> > enough for decisions to be made on this topic without concerning
> > ourselves
> > too much with what the big kids are doing.
>
> I think you're missing the point here. The overwhelming position for
> OOP languages (which PEAR is all OOP) has been humpBack. Moving from
> Java to Python to Ruby to PHP it would make sense that of 3/4 use
> humpBack that we stay consistent with the rest just so people don't
> have to retrain their CS thought processes ... it makes for a
> smoother transition for people moving from Java to PHP for instance
> (of which there are a lot - more with PHP5 I suspect).
Ruby uses names_with_underscores for everything except constants, and
afaik python has a mix of nameswithoutseparator and
names_with_underscores (except class names again)...