On Wed, May 31, 2006 at 06:24:35PM +0400, Antony Dovgal wrote:
>
> So that E_STRICT notices introduced in 6.x will become E_FATALs only in 7.0
> and so on.
That's pretty much what I was going to say.
To be clear, unlike the commit that was recently reverted, E_STRICT should
never be moved into E_ALL. What should change is the type of error the
behaviors trigger.
So, something from PHP 4 that triggers an E_STRICT in PHP 5 should trigger
an E_WARNING (or whatever) in PHP 6.
This leaves E_STRICT available for use in PHP 6 to tag deprecated items
from PHP 5 that will trigger E_WARNINGS in PHP 7.
And on and on...
--Dan
--
T H E A N A L Y S I S A N D S O L U T I O N S C O M P A N Y
data intensive web and database programming
http://www.AnalysisAndSolutions.com/
4015 7th Ave #4, Brooklyn NY 11232 v: 718-854-0335 f: 718-854-0409
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
