rfc:namespaces

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
rfc:namespaces [2008/09/16 00:05] – quote greg about Issue 12 patch jochemrfc:namespaces [2008/09/16 01:47] – test1.php's ouputs have one mistake shenkong
Line 108: Line 108:
 <code> <code>
 defined('DEBUG'): YES (expect YES) defined('DEBUG'): YES (expect YES)
-defined('my::test::ns::DEBUG_2'): NO (expect YES)+defined('MY::TEST::NS::DEBUG_2'): NO (expect YES)
 defined('my::test::ns::DEBUG_2'): NO (expect NO) defined('my::test::ns::DEBUG_2'): NO (expect NO)
 defined('my::test::ns::debug_2'): NO (expect NO) defined('my::test::ns::debug_2'): NO (expect NO)
Line 758: Line 758:
 > >
 > If a fully qualified name is prefixed with function:: or const:: it will only check the namespace function/const.  Here is a test demonstrating how it works: > If a fully qualified name is prefixed with function:: or const:: it will only check the namespace function/const.  Here is a test demonstrating how it works:
- +> 
-ns_071.inc: +ns_071.inc: 
-<code php>+<code php>
 <?php <?php
 namespace foo; namespace foo;
Line 773: Line 773:
 ?> ?>
 </code> </code>
-ns_071.phpt: +ns_071.phpt: 
-<code php>+<code php>
 --TEST-- --TEST--
 071: name conflict, function/static method, constant/class constant 071: name conflict, function/static method, constant/class constant
Line 876: Line 876:
   * [[php-internals@119874502923978|Suggestion: Namespace implementation]]   * [[php-internals@119874502923978|Suggestion: Namespace implementation]]
  
-Nothing has been filtered on the basis of relevance!+//Nothing has been filtered on the basis of relevance BUT some threads may not be listed due to the 'limitations' of the marc.info search functionality!//
  
  
rfc/namespaces.txt · Last modified: 2017/09/22 13:28 by 127.0.0.1