Bug #64346 [Com]: Function name resolution and eval

From: Date: Tue, 21 Nov 2017 18:48:44 +0000
Subject: Bug #64346 [Com]: Function name resolution and eval
References: 1  Groups: php.bugs 
Request: Send a blank email to php-bugs+get-212663@lists.php.net to get a copy of this message
Edit report at https://bugs.php.net/bug.php?id=64346&edit=1

 ID:                 64346
 Comment by:         shiranai7 at hotmail dot com
 Reported by:        gen dot work at gmail dot com
 Summary:            Function name resolution and eval
 Status:             Open
 Type:               Bug
 Package:            *General Issues
 Operating System:   Ubuntu 12.10
 PHP Version:        5.4.12
 Block user comment: N
 Private report:     N

 New Comment:

Would it also be expensive to invalidate specific (not all) keys in the "literal cache"
each time a function or a constant is defined?

I'd avoid a global INI setting if possible.


Previous Comments:
------------------------------------------------------------------------
[2017-03-15 20:23:05] losborn at jnrcorp dot com

Related To: Bug #74253

------------------------------------------------------------------------
[2017-03-15 20:17:50] requinix@php.net

Related To: Bug #74253

------------------------------------------------------------------------
[2017-03-11 18:06:12] nikic@php.net

Related To: Bug #63201

------------------------------------------------------------------------
[2016-11-12 11:48:11] showerheadsuk at hotmail dot com

The same problem also applies to constants when accessing from a namespaced class - if the first the
time the constant is accessed it is defined globally but not in the local namespace, then that
global value will be used for all future accesses even if it is later defined in the local
namespace.

Since overriding global functions / constants is mostly used just for testing, could this be added
as a php.ini option, like 
literal_cache_disable = 1

------------------------------------------------------------------------
[2016-05-31 20:22:20] cmb@php.net

Related To: Bug #68541

------------------------------------------------------------------------


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=64346


--
Edit this bug report at https://bugs.php.net/bug.php?id=64346&edit=1


Thread (14 messages)

« previous php.bugs (#212663) next »