Req #26545 [Opn->Dup]: Cannot extract() variables into class scope

From: Date: Tue, 19 Aug 2014 16:11:03 +0000
Subject: Req #26545 [Opn->Dup]: Cannot extract() variables into class scope
References: 1  Groups: php.bugs 
Request: Send a blank email to php-bugs+get-187182@lists.php.net to get a copy of this message
Edit report at https://bugs.php.net/bug.php?id=26545&edit=1 ID: 26545 Updated by: levim@php.net Reported by: kmsluder at optonline dot net Summary: Cannot extract() variables into class scope -Status: Open +Status: Duplicate Type: Feature/Change Request -Package: Feature/Change Request +Package: *General Issues Operating System: Linux 2.4.2 PHP Version: 4.3.4 Block user comment: N Private report: N New Comment: Closing this as a duplicate of bug 10546. Previous Comments: ------------------------------------------------------------------------ [2014-03-05 20:22:42] narf at devilix dot net This looks like a duplicate of #10564 https://bugs.php.net/bug.php?id=10546 P.S.: The referenced pull request has been closed. ------------------------------------------------------------------------ [2009-02-27 08:07:44] james dot relyea at zifiniti dot com Adding in ability to specifiy scope would be highly useful for Objects. ------------------------------------------------------------------------ [2004-01-10 10:41:10] andrey@php.net What's the deal to use extract() to add dynamically member variables to the object? ------------------------------------------------------------------------ [2003-12-06 16:53:27] derick@php.net It's still not a bug as extract() was never meant to do this. Making it a feature-request. ------------------------------------------------------------------------ [2003-12-06 16:20:21] kmsluder at optonline dot net Note to anyone that says that the extra two lines aren't a big deal: it's a lot more than two if you need to emulate some of the more sophisticated (and rather useful) features of extract(). ------------------------------------------------------------------------ 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 https://bugs.php.net/bug.php?id=26545 -- Edit this bug report at https://bugs.php.net/bug.php?id=26545&edit=1

« previous php.bugs (#187182) next »