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
Last revisionBoth sides next revision
pear:rfc:pear2_class_naming [2009/09/20 19:00] – highlight reference #3 ashnazgpear: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: 0.2.0+  * Version: 1.0.0
   * Status: Ratified   * Status: Ratified
   * Type: Informative Document   * Type: Informative Document
Line 9: Line 9:
   * Last Updated:  September 20th, 2009   * Last Updated:  September 20th, 2009
   * Passed:  September 20th, 2009   * Passed:  September 20th, 2009
 +
 +This RFC has been incorporated into the PEAR2 Standards ([[pear/rfc/pear2_standards]]).
  
 ==== Author(s) Information ==== ==== Author(s) Information ====
Line 35: Line 37:
 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 [3]+    * 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

Page Tools