rfc:backslashnamespaces

Differences

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

Link to this comparison view

Next revisionBoth sides next revision
rfc:backslashnamespaces [2008/10/25 06:32] – created cellogrfc:backslashnamespaces [2008/10/25 06:41] – add small codebase change to advantages of both removal and Stas's option cellog
Line 34: Line 34:
   * no naming conflicts possible between functions/static methods, class constants/namespace constants   * no naming conflicts possible between functions/static methods, class constants/namespace constants
   * no syntax changes for those using namespaces for classes   * no syntax changes for those using namespaces for classes
 +  * probably the smallest codebase change
  
 ==== Problems ==== ==== Problems ====
Line 170: Line 171:
  
   * if classname->method() is used, it solves the ambiguity issue   * if classname->method() is used, it solves the ambiguity issue
 +  * Definitely the smallest codebase change
  
 ==== Problems ==== ==== Problems ====
Line 179: Line 181:
   * it redefines a long-established definition of ->, which is not necessarily a problem, but could be confusing for both existing and new users   * it redefines a long-established definition of ->, which is not necessarily a problem, but could be confusing for both existing and new users
   * only educated users would ever think to look for -> unless a massive PR campaign is mounted, which would also make PHP look disorganized.  This is simply a political and NOT a technical problem.   * only educated users would ever think to look for -> unless a massive PR campaign is mounted, which would also make PHP look disorganized.  This is simply a political and NOT a technical problem.
 +  * does not solve the deeper problems inherent in ::
  
 ===== Use \ as namespace separator ===== ===== Use \ as namespace separator =====
rfc/backslashnamespaces.txt · Last modified: 2017/09/22 13:28 by 127.0.0.1

Page Tools