Bug #60022 [Asn]: "use statement [...] has no effect" depends on leading backslash

From: Date: Tue, 15 Jul 2014 11:12:10 +0000
Subject: Bug #60022 [Asn]: "use statement [...] has no effect" depends on leading backslash
References: 1  Groups: php.bugs 
Request: Send a blank email to php-bugs+get-186620@lists.php.net to get a copy of this message
Edit report at https://bugs.php.net/bug.php?id=60022&edit=1 ID: 60022 Updated by: yohgaki@php.net Reported by: nikic@php.net Summary: "use statement [...] has no effect" depends on leading backslash Status: Assigned Type: Bug Package: Scripting Engine problem -PHP Version: 5.4.0beta1 +PHP Version: * Assigned To: dmitry Block user comment: N Private report: N New Comment: This exists in all versions http://3v4l.org/SCXWd Previous Comments: ------------------------------------------------------------------------ [2011-10-16 11:08:05] nikic@php.net Only thing this could "break" is that the "You seem to be trying to use a different language..." message would be triggered for "use \strict;" too. If that's a problem I can modify the patch to not throw in that case. ------------------------------------------------------------------------ [2011-10-11 09:04:08] nikic@php.net The following patch has been added/updated: Patch Name: patch.txt Revision: 1318323848 URL: https://bugs.php.net/patch-display.php?bug=60022&patch=patch.txt&revision=1318323848 ------------------------------------------------------------------------ [2011-10-09 17:27:35] nikic@php.net Description: ------------ The "The use statement with non-compound name '%s' has no effect" warning is only thrown when the use statement doesn't have a leading backslash. It should be thrown in both cases as they are semantically equivalent. (Patch is trivial: Get rid of the is_global arg altogether.) Test script: --------------- <?php namespace { use Exception; } namespace { use \Exception; } // http://codepad.viper-7.com/vN34cx Expected result: ---------------- Two warnings. Actual result: -------------- One warning. ------------------------------------------------------------------------ -- Edit this bug report at https://bugs.php.net/bug.php?id=60022&edit=1

« previous php.bugs (#186620) next »