cvs: php-src / CODING_STANDARDS

From: Date: Wed, 21 Jan 2004 20:18:10 +0000
Subject: cvs: php-src / CODING_STANDARDS
Groups: php.cvs 
Request: Send a blank email to php-cvs+get-25809@lists.php.net to get a copy of this message
helly Wed Jan 21 15:18:10 2004 EDT Modified files: /php-src CODING_STANDARDS Log: All technical reasons that prevented us from studlyCaps are solved and all current extensions as well as the whole PEAR framework follow this rule. So for consistency i readd it. # Also we had the discussion onece and decided for this. # Lookup the archieves http://cvs.php.net/diff.php/php-src/CODING_STANDARDS?r1=1.27&r2=1.28&ty=u Index: php-src/CODING_STANDARDS diff -u php-src/CODING_STANDARDS:1.27 php-src/CODING_STANDARDS:1.28 --- php-src/CODING_STANDARDS:1.27 Wed Dec 3 04:12:38 2003 +++ php-src/CODING_STANDARDS Wed Jan 21 15:18:09 2004 @@ -133,7 +133,22 @@ [5] Variable names should be in lowercase. Use underscores to separate between words. -[6] Classes should be given descriptive names. Avoid using abbreviations +[6] Method names follow the 'studlyCaps' (also referred to as 'bumpy case' + or 'camel caps') naming convention, with care taken to minimize the + letter count. The initial letter of the name is lowercase, and each + letter that starts a new 'word' is capitalized. + + Good: + 'connect()' + 'getData()' + 'buildSomeWidget()' + + Bad: + 'get_Data()' + 'buildsomewidget' + 'getI()' + +[7] Classes should be given descriptive names. Avoid using abbreviations where possible. Each word in the class name should start with a capital letter, with words underscore delimited. The class name should be prefixed with the name of the 'parent set'.

« previous php.cvs (#25809) next »