Differences

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

--- pear:rfc:pear2_class_naming [2009/09/20 17:35] – base Exception name is required, not optional ashnazg
+++ pear:rfc:pear2_class_naming [2009/09/20 19:01] – that should be #4 ashnazg
@@ Line 4: / Line 4: @@
   * Title: PEAR2 Class Naming Conventions
   * Version: 0.2.0
-  * Status: Draft
+  * Status: Ratified
   * Type: Informative Document
   * Wiki link:  http://wiki.php.net/pear/rfc/PEAR2_Class_Naming
   * Last Updated:  September 20th, 2009
+  * Passed:  September 20th, 2009
 ==== Author(s) Information ====
@@ Line 34: / Line 35: @@
 New guidelines for PEAR2:
   * 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 =====
@@ Line 49: / Line 50: @@
 The only exception to the Interface suffix requirement is the base package exception, which must be named simply "Exception". [3]
+One benefit of the suffix rather than a prefix is in alphabetical-based visual listing of classes.  Using prefixes would result in all unrelated abstract classes being listed togther... the same result would apply to all unrelated intefaces.
 ===== Examples =====