ID: 46755 Updated by: fel...@php.net Reported By: david at grudl dot com -Status: Bogus +Status: Assigned Bug Type: Scripting Engine problem Operating System: * PHP Version: 5.3.0alpha3 -Assigned To: +Assigned To: cellog
Previous Comments: ------------------------------------------------------------------------ [2008-12-29 01:41:46] david at grudl dot com 1) The warning says "The use statement with non-compound name 'Foo' has no effect". This is not correct. I have posted example which show it HAS effect. Try it run in PHP. 2) "...the leading backslash is unnecessary and not allowed, as import names must be fully qualified, and are not processed relative to the current namespace." This is nonsense. If they are not processed relative, Foo is fully qualified - why developers MUST use leading backslash in some cases and MUST NOT is other cases - in all cases it is fully qualified. This should be fixed in documentation. Please, change status to Open. ------------------------------------------------------------------------ [2008-12-28 23:47:02] fel...@php.net "Note that for namespaced names (fully qualified namespace names containing namespace separator, such as Foo\Bar as opposed to global names that do not, such as FooBar), the leading backslash is unnecessary and not allowed, as import names must be fully qualified, and are not processed relative to the current namespace." This explain it. ------------------------------------------------------------------------ [2008-12-28 23:33:34] david at grudl dot com I have read it. Please, change status to Open. ------------------------------------------------------------------------ [2008-12-28 21:08:29] fel...@php.net Read: http://docs.php.net/manual/en/language.namespaces.importing.php ------------------------------------------------------------------------ [2008-12-19 17:19:57] david at grudl dot com It would be very nice if the error was fixed, because it is difficult to test alpha3 with a tons of Warnings: The use statement with non-compound name 'Nette' has no effect :-( ------------------------------------------------------------------------ The remainder of the comments for this report are too long. To view the rest of the comments, please view the bug report online at http://bugs.php.net/46755 -- Edit this bug report at http://bugs.php.net/?id=46755&edit=1
