Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with
or
.
Download ZIP
Browse files

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
  • Loading branch information...
commit 2a8300e03d9f6ef62f4e2f91f0a8c1d2c848709b 1 parent 17d420e
Marcus Boerger authored
Showing with 16 additions and 1 deletion.
  1. +16 −1 CODING_STANDARDS
View
17 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'.
Please sign in to comment.
Something went wrong with that request. Please try again.