So -1, and some rethinking needed about the way E_STRICT is used ('this is
the way you should do it' vs 'this is the way you will have to do it in
future')
Going on from there - if E_STRICT is now being touted as 'deprecated stuff
only', would it be a good idea to have something like E_DEVEL for 'advice'
issues like vars, semi-statics, etc etc etc - which would of course _never_
become part of E_ALL? Or was that the original intention for E_NOTICE?
Just a thought.
- Steph
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
