note 92607 added to language.namespaces.rules

The term "autoload" mentioned here shall not be confused with __autoload function to autoload objects. Regarding the __autoload and namespaces' resolution I'd like to share the following experience: ->Say you have the following directory structure: - root | - loader.php | - ns | - foo.php ->foo.php <?php namespace ns; class foo { public $say; public function __construct() { $this->say = "bar"; } } ?> -> loader.php <?php //GLOBAL SPACE <-- function __autoload($c) { require_once $c . ".php"; } class foo extends ns\foo // ns\foo is loaded here { public function __construct() { parent::__construct(); echo "<br />foo" . $this->say; } } $a = new ns\foo(); // ns\foo also loads ns/foo.php just fine here. echo $a->say; // prints bar as expected. $b = new foo; // prints foobar just fine. ?> If you keep your directory/file matching namespace/class consistence the object __autoload works fine. But... if you try to give loader.php a namespace you'll obviously get fatal errors. My sample is just 1 level dir, but I've tested with a very complex and deeper structure. Hope anybody finds this useful. Cheers! ---- Server IP: 69.147.83.197 Probable Submitter: 201.1.136.131 ---- Manual Page -- http://www.php.net/manual/en/language.namespaces.rules.php Edit -- https://master.php.net/note/edit/92607 Del: integrated -- https://master.php.net/note/delete/92607/integrated Del: useless -- https://master.php.net/note/delete/92607/useless Del: bad code -- https://master.php.net/note/delete/92607/bad+code Del: spam -- https://master.php.net/note/delete/92607/spam Del: non-english -- https://master.php.net/note/delete/92607/non-english Del: in docs -- https://master.php.net/note/delete/92607/in+docs Del: other reasons-- https://master.php.net/note/delete/92607 Reject -- https://master.php.net/note/reject/92607 Search -- https://master.php.net/manage/user-notes.php