summaryrefslogtreecommitdiff
path: root/CODING_STANDARDS
diff options
context:
space:
mode:
authorMarcus Boerger <helly@php.net>2004-01-21 20:18:09 (GMT)
committerMarcus Boerger <helly@php.net>2004-01-21 20:18:09 (GMT)
commit2a8300e03d9f6ef62f4e2f91f0a8c1d2c848709b (patch)
tree0ef8ee774974e3fd370f642c4708641001e2d7d1 /CODING_STANDARDS
parent17d420e5f7dd51343fb9c75762c8bb67007e176a (diff)
downloadphp-2a8300e03d9f6ef62f4e2f91f0a8c1d2c848709b.tar.gz
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
Diffstat (limited to 'CODING_STANDARDS')
-rw-r--r--CODING_STANDARDS17
1 files changed, 16 insertions, 1 deletions
diff --git a/CODING_STANDARDS b/CODING_STANDARDS
index 9feb43b..bf9854b 100644
--- a/CODING_STANDARDS
+++ b/CODING_STANDARDS
@@ -133,7 +133,22 @@ Naming Conventions
[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'.