pear:rfc:pear2_class_naming
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionLast revisionBoth sides next revision | ||
pear:rfc:pear2_class_naming [2009/09/20 18:07] – RFC passed ashnazg | pear:rfc:pear2_class_naming [2009/09/20 19:28] – bump to 1.0 due to ratification; note incorporation into PEAR2 Standards ashnazg | ||
---|---|---|---|
Line 3: | Line 3: | ||
==== Document Information ==== | ==== Document Information ==== | ||
* Title: PEAR2 Class Naming Conventions | * Title: PEAR2 Class Naming Conventions | ||
- | * Version: | + | * Version: |
- | * Status: | + | * Status: |
* Type: Informative Document | * Type: Informative Document | ||
* Wiki link: http:// | * Wiki link: http:// | ||
* Last Updated: | * Last Updated: | ||
* Passed: | * Passed: | ||
+ | |||
+ | This RFC has been incorporated into the PEAR2 Standards ([[pear/ | ||
==== Author(s) Information ==== | ==== Author(s) Information ==== | ||
Line 35: | Line 37: | ||
New guidelines for PEAR2: | New guidelines for PEAR2: | ||
* syntax/ | * syntax/ | ||
- | * such suffixing is required for abstract classes and interfaces, for additional clarity to non-native English readers | + | * such suffixing is required for abstract classes and interfaces, for additional clarity to non-native English readers |
===== Issues ===== | ===== Issues ===== | ||
Line 50: | Line 52: | ||
The only exception to the Interface suffix requirement is the base package exception, which must be named simply " | The only exception to the Interface suffix requirement is the base package exception, which must be named simply " | ||
+ | One benefit of the suffix rather than a prefix is in alphabetical-based visual listing of classes. | ||
===== Examples ===== | ===== Examples ===== |
pear/rfc/pear2_class_naming.txt · Last modified: 2017/09/22 13:28 by 127.0.0.1