Hi Thomas, On 11/16/2010 01:32 PM, Maxime Thomas wrote:
> What are the limit cases for this one : Almost always camelCase ? I listed the cases directly below this point. Actually, only constants are an exception to the camelCase rule. > I would like to add a semantic rule to that about function naming. > Function names must be : > - Short > - Explicit > - Use verbs as first name : get, put, set, call, fetch, send... > - Be always lowered camelCased This kind of stuff is already documented here: http://incubator.apache.org/zetacomponents/community/implementation.html > I also would like to add another semantic rule about variable naming : > > - if attribute of class : must be camelCased > - if local variable : must be url styled : lowered and white caracters > escape with underscore I'm sorry, but that is not how we code in Zeta. We use camelCase everywhere and the idea should not be to change a coding standard, but to document it properly. > For comment, I guess we will follow the same as eZPublish, good rule of > thumb, or inherit from PEAR, a good start and easily pluggable into phpunit. > Do we have to set the encoding settings of the files (UTF-8, Unix Style) ? We use UTF-8 everywhere. For SVN you are best of with svn:eol-style set to native. Regards, Toby -- Tobias Schlitt http://schlitt.info GPG Key: 0xC462BC14 Want to hire me? Need quality assurance? http://qafoo.com eZ Components are Zeta Components now! http://bit.ly/9S7zbn
