Hi Tobias, What are the limit cases for this one : Almost always camelCase ?
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 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 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) ? Regards, Max 2010/11/16 Tobias Schlitt <[email protected]> > Hi, > > for another project I needed to give advice on the coding standard used > by Apache Zeta Components. There is some very old version of the eZ > Publish coding style in [1] (from 2001) but no reliable, recent source. > So I think we should document our coding style on the website. > > Please complete / correct my following brainstorming: > > - Indentation with 4 spaces > - After a "{" > - On breakup of long lines (> 78 chars) after a "(" > - "{" and "}" on a new line > - 1 space after "(" and before ")" > - No space after "[" and before "]" > - 1 space after "," > - 1 space before and after "." > - Almost always camelCase > - classes always start with ezc followed by an upper case char > - constants all in upper case with "_" > > 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 >
