rfc:backslashnamespaces

Differences

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

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
rfc:backslashnamespaces [2008/10/25 13:54]
cellog fix error in Lukas's understanding of Classname->method()
rfc:backslashnamespaces [2017/09/22 13:28] (current)
Line 287: Line 287:
   * because \ is a single keystroke, it is possible to require \ prefix for all global functions/​classes/​constants,​ and conversion is minimally effortful (from personal experience trying to convert files to several namespace separators to see what it was like)   * because \ is a single keystroke, it is possible to require \ prefix for all global functions/​classes/​constants,​ and conversion is minimally effortful (from personal experience trying to convert files to several namespace separators to see what it was like)
   * code review ambiguities disappear permanently   * code review ambiguities disappear permanently
-  * name resolution order problems disappear if we decide that "foo/bar" or "​foo::​bar"​ is always prefixed with namespace name, and only short names like "​bar()"​ or "new bar" are checked for both "​nsname/bar()" and internal function "​bar()"​ or "class nsname/bar" and internal class "​bar"​. ​ "/foo/bar" is used for global scoping.+  * name resolution order problems disappear if we decide that "foo\bar" or "​foo::​bar"​ is always prefixed with namespace name, and only short names like "​bar()"​ or "new bar" are checked for both "​nsname\bar()" and internal function "​bar()"​ or "class nsname\bar" and internal class "​bar"​. ​ "\foo\bar" is used for global scoping.
   * code coverage of namespace-related code is so good, it is possible to be very confident of the correctness of the patch.   * code coverage of namespace-related code is so good, it is possible to be very confident of the correctness of the patch.
  
rfc/backslashnamespaces.txt · Last modified: 2017/09/22 13:28 (external edit)