On Fri, Feb 6, 2015 at 6:02 AM, Yasuo Ohgaki <yohg...@ohgaki.net> wrote: > https://wiki.php.net/rfc/script_path > > It's work in progress, but I would like to start discuss. >
I don't really like it; but I don't really like most INI-based solutions. I agree that this is a problem with poorly written code, but at the same time I don't know that a good solution is to compensate in this regard. Bad programmers will always be bad programmers. Now we're giving them a crutch that almost encourages unchecked includes by relying on an INI configuration. What happens if you are using multiple libraries and they are each overriding their (and your) settings? It just feels messy. The same thing could be accomplished config-less with a callback system that is triggered on script includes (if any callback returns false, an error is thrown), but I think I'd dislike that for similar reasons. -- Matthew Leverton -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
