Inclusion of E_STRICT and E_RECOVERABLE_ERROR into E_ALL
Addition of support for dynamic statics ala: class foo {} foo::$bar = 1;
E_RECOVERABLE_ERROR's apparently going in anyway.
E_STRICT, I'd be all for including into E_ALL now if it weren't for the
'semi-statics' issue (complex) and the distributed INI default settings
(simple). If PEAR:isError() legal doesn't actually do the Engine any harm
then it'd make sense to keep it, purely as a BC consideration, in which case
it shouldn't really need an E_STRICT if the purpose of E_STRICT is to warn
about future BC breaks. Outside that, I personally find E_STRICT useful -
it's helped me diagnose mystery crashes before now - but it's really only
useful if it isn't over-used as an error level.
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')
As far as statics, there are no BC reasons not to do it that I can think
of, but it just seems wrong to me from a design perspective to allow
dynamic creation of static object properties.
It seems very PHP-ish to me to allow it. +1.
- Steph
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
