Hello internals, right now the fate of E_STRICT error messages is uncertain. A few people think those should change to fatal after a reasonable amount of time, is two years (e.g. 5.0.0) reasonable. A few even think a minor version like 5.1 to 5.2 is enough but the majortiy (at least i guess so) wants the change only on a major version change like 5.0 to 6.0.
Currently the manual says: <manual> 2048 E_STRICT (integer) Run-time notices. Enable to have PHP suggest changes to your code which will ensure the best interoperability and forward compatibility of your code. since PHP 5 </manual> So the RFC goes: Extend the manual to specify that issues reported by E_STRICT messages are most likely to become fatal errors in the next major version. RFC = Comments? Comment from myself: To have this working we need tests. For a start we need tests that trigger any E_STRICT present in php/zend c code. It might as well halp to turn on E_STRICT in E_ALL but oh , i say no more. Best regards, Marcus -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
