Am 29.04.2016 um 11:48 schrieb Nikita Popov:
> Welcome to another edition of "crazy PHP edge-cases you don't want
> to know about".
I love and hate these edge cases at the same time :)
> I'd like to introduce a restriction that forbids performing dynamic calls
> to scope introspection and modific
I'm all in favour of this. It makes the language much more predictable and
amenable to optimisation and static analysis overall, at the cost of what
IMO is a very, very minor BC break.
To think that all this time, functions I've written which accept a callable
could be passed something like "extra
Hi!
> I think it's better to keep this email as RFC, at least for documentation of
> BC break purpose.
> I'm not sure if we need 2 week discussion + 2 weeks voting for this.
> I think 1 week voting should be enough?
It should be at least 2 weeks discussion, as it's a language change, as
for voti
uld be enough?
and I'm sure, it should pass.
Thanks. Dmitry.
From: Nikita Popov
Sent: Friday, April 29, 2016 12:48:48 PM
To: PHP internals
Subject: [PHP-DEV] Forbid dynamic calls to scope introspection/modification
functions
Hi internals!
Welcome
Hi internals!
Welcome to another edition of "crazy PHP edge-cases you don't want to know
about".
I'd like to introduce a restriction that forbids performing dynamic calls
to scope introspection and modification functions. "Dynamic calls" here
means things like $fn(), call_user_func($fn) and array