Hi,
Although this change may cause confusion, but it would be beneficial to
many users as a security counter measure.
For instance, there is CVE-2013-2065 for Ruby
http://www.ruby-lang.org/en/news/2013/05/14/taint-bypass-dl-fiddle-cve-2013-2065/
I suppose this change allow us "monkey patch" PHP
Your solution is flawed, it would not allow autoloading a function that has the
same
(namespaced) name as a builtin.
Example:
// autoloadable function
namespace foo {
// make arg order consistent
function array_filter($callback, $input) {
return \array_filter(
2013/5/2 Igor Wiedler
> No, I want to keep autoloading out of this proposal. It is way beyond the
> scope of the namespacing issue and also incredibly complex.
>
> That said, this RFC may be useful for implementing autoloading in the
> future, as it addresses one of the things that makes function
No, I want to keep autoloading out of this proposal. It is way beyond the scope
of the namespacing issue and also incredibly complex.
That said, this RFC may be useful for implementing autoloading in the future,
as it addresses one of the things that makes function autoloading hard, which
is be
Hi,
Are you going to cover autoloading of functions too?
Regards,
Sebastian
2013/5/2 Igor Wiedler
> Hi internals,
>
> Since there's been no major objection to this proposed RFC, I will go
> ahead and create it on the wiki. I will amend it to address some of the
> points that were discussed so
