pear:rfc:pear2_class_naming

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
Next revisionBoth sides next revision
pear:rfc:pear2_class_naming [2009/09/20 18:10] – status bump ashnazgpear:rfc:pear2_class_naming [2009/09/20 19:01] – that should be #4 ashnazg
Line 35: Line 35:
 New guidelines for PEAR2: New guidelines for PEAR2:
   * syntax/scope hints in the class name must be suffixed rather than prefixed, e.g. abstract class FooAbstract {}   * syntax/scope hints in the class name must be suffixed rather than prefixed, e.g. abstract class FooAbstract {}
-    * 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 [4]
  
 ===== Issues ===== ===== Issues =====
pear/rfc/pear2_class_naming.txt · Last modified: 2017/09/22 13:28 by 127.0.0.1