Re: [PEPr] Comment on RFC::RFC_PackageVariableNamingConvention

Lukas Smith wrote:

Lukas Smith (http://pear.php.net/user/lsmith) has commented on the proposal for RFC::RFC_PackageVariableNamingConvention. Comment: While I personally prefer underscores for variable names, just because that differntiates them nicely from methods I would also agree with other commentors that I would prefer a simple "pick one and stick to it rule". That being said there are situations where camelCaps are not useful, like when mapping column names from a database, since alot of RDBMS will not enable you to maintain campelCaps inside associtative fetches. Proposal information: http://pear.php.net/pepr/pepr-proposal-show.php?id=282 Sure its just like its not useful when automatically mapping method names between php4 and JavaScript since you can't actually get the case out of php. But really I think all this says its purely a style point, and legislating it will just cause problems who need to do whats best for there needs. Which btw is what has happened with method names, where people aren't following the standard they implement because they have to follow pears.

A good example where requiring _ in variable names would cause problems would be in any code implementing a w3c standard api where CamelCase with the first letter capitalized is always used. Oh and I think the ( at the end does a great job of telling me whats a method :-P -josh