On Thu, Aug 8, 2013 at 5:11 PM, Ferenc Kovacs <tyr...@gmail.com> wrote:
> Hi, > > I've just bumped into https://bugs.php.net/bug.php?id=65322 recently, and > I would like you get some opinions on the issue. > Personally I think that it is a really bad design to introduce > pedantic(E_STRICT) errors which can break basic functionality of the engine > (calling the registered autoloader), so if there is no viable solution to > make the autoloader work for these kind of errors, I would like to propose > removing the offending errors and make it a rule to not add compile-time > non-fatal errors until the problem is resolved. > > ps: on a related note, somehow I got the feeling that Lester complaining > that E_STRICT errors fataling/crashing the application migrated to PHP 5.4 > was related to this problem, and I'm a bit sad that we didn't managed to > figure this out back then. > > -- > Ferenc Kovács > @Tyr43l - http://tyrael.hu > for the record this is a known(as reported) since 2007: https://bugs.php.net/bug.php?id=42098 and reported again in 2011: https://bugs.php.net/bug.php?id=54054&edit=2 do we agree with the resolution from the 2007, eg. it is fine that there an undefined list of errors (from all and any error level) which behave differently than most others (as it won't trigger the autoloader) and even an E_STRICT error can blow up a reasonably written application (an expected error occurs, which happens to be compile time, which will trigger the autoloader, which will fail to autoload it's dependencies, which will generate class not found fatal error). I expect much more similar reports now that people start to migrate to 5.4/5.5 where E_STRICT is part of E_ALL(and that the error reporting infrastructure in an average application is more likely to depend on autoloading nowadays). -- Ferenc Kovács @Tyr43l - http://tyrael.hu
