Hello internals, by accident i added both E_STRICT and E_RECOVERABLE_ERROR to E_ALL while MFHing new features as discussed beforehand while decision was only to MFH E_RECOVERABLE_ERROR and not to put E_STRICT into E_ALL. See: http://oss.backendmedia.com/PhP52
Now the idea of E_STRICT is that core developers can inform users about changes in upcoming versions of php as early as possible. So developers should have E_ALL including E_STRICT enabled during development so that they are able to develop clean applications that most likely will work in the next version. On the production machines you would still either not use E_ALL or log only and don't show the errors in the application. That said i am about to not remove E_STRICT from E_ALL and MFH the php 6.0 to item just now. See: http://oss.backendmedia.com/PhP60 (add E_STRICT to E_ALL DONE (dmitry)) Since this is for the benefit of the users to prevent issues with changes in behavior from my opinion it is best to do this behavior change as early as possible, which is in my opinion 5.2 anyway. That said i'll let it in and if there is no valid argument against, i will put it into the NEWS file and the newly started README.UPDATE_5_2. Best regards, Marcus -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
