ID: 46979 Updated by: dmi...@php.net Reported By: ladislav at marek dot su -Status: Assigned +Status: Closed Bug Type: Scripting Engine problem Operating System: * PHP Version: 5.3.0alpha3 Assigned To: dmitry New Comment:
This bug has been fixed in CVS. Snapshots of the sources are packaged every three hours; this change will be in the next snapshot. You can grab the snapshot at http://snaps.php.net/. Thank you for the report, and for helping us make PHP better. Previous Comments: ------------------------------------------------------------------------ [2009-01-01 02:52:52] cel...@php.net assign to namespace maintainer ------------------------------------------------------------------------ [2008-12-31 09:36:09] ladislav at marek dot su Yes, but bug isn't fixed, 'use ArrayObject' is same as 'use \ArrayObject' manual is wrong. Please consider importing non-compound class or namespace names without \ prefix (remove invalid warning). ------------------------------------------------------------------------ [2008-12-30 23:49:09] fel...@php.net Duplicated of Bug #46755 ------------------------------------------------------------------------ [2008-12-30 23:38:25] ladislav at marek dot su Description: ------------ Currently php throws bogus warning with non-compound name in use statement. Reproduce code: --------------- namespace My; use Foo; new Foo\Bar; Expected result: ---------------- Fatal error: Class 'Foo\Bar' not found in ... Actual result: -------------- Warning: The use statement with non-compound name 'Foo' has no effect in ... Fatal error: Class 'Foo\Bar' not found in ... 'use Foo' has effect, because fully qualified name isn't My\Foo\Bar but Foo\Bar. ------------------------------------------------------------------------ -- Edit this bug report at http://bugs.php.net/?id=46979&edit=1
