From: Derick Rethans Date: Wed, 3 Dec 2003 09:12:38 +0000 (+0000) Subject: - I am sure I reverted this before X-Git-Tag: php-5.0.0b3RC1~386 X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=61e8ab4e8d11f872f0e15e027341809f82f2feb6;p=php - I am sure I reverted this before --- diff --git a/CODING_STANDARDS b/CODING_STANDARDS index bf9854b7cd..9feb43b851 100644 --- a/CODING_STANDARDS +++ b/CODING_STANDARDS @@ -133,22 +133,7 @@ Naming Conventions [5] Variable names should be in lowercase. Use underscores to separate between words. -[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 +[6] 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'.