[VOTE] Forbid dynamic calls to scope introspection functions

The RFC

https://wiki.php.net/rfc/forbid_dynamic_scope_introspection

is now in voting. The vote closes on 2016-05-24 with a required majority of
2/3.

I voted no. While I agree these appear to be exotic use cases, my quibble
boils down to the assumption these minimally exist in the wild. Several
templating systems rely on extract, and func_get_args drives several
framework collection classes. I can see userland invoking these inside of
array_map (etc) and dynamically.

I'd be a Yes if we start with a warning in 7.1 and then error in the next
major.

Hi internals,

The RFC

https://wiki.php.net/rfc/forbid_dynamic_scope_introspection

is now in voting. The vote closes on 2016-05-24 with a required majority
of 2/3.

Nikita

Thanks to a comment on Reddit, I realized that the function list in the RFC
is missing "assert() with a string argument" as a forbidden function. The
reason is that assert() with a string is really just a different way of
saying eval() -- so it will inherit the parent symbol table and may modify
it. I missed this because the function was also missing from the opcache
indirect var access list (remedied in 1).

I hope it's not a problem to add this case to the RFC even though it's
already in voting.

Nikita