Hi Marcus,
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.
I'd back the majority over this. Changes from E_STRICT to fatal in minor
versions is out of the question; most people still use PHP 4.3.*, and this
is something you're failing to consider here.
<snip />
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.
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.
You already know I agree with you over that, but thousands don't.
The real problem when we're talking about moving PHP into this century is
that most people liked it as it was... We really, really need an easy
upgrade path, preferably an automated one. And we still don't have that
today.
- Steph
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
