On 16-May-06, at 7:50 PM, Marcus Boerger wrote:
Hello Ilia,
Wednesday, May 17, 2006, 1:26:37 AM, you wrote:
Inclusion of E_STRICT and E_RECOVERABLE_ERROR into E_ALL
+1
While doing all the stuff we wanted for 5.2 we also added
E_RECOVERABLE_ERROR. This includes stuff that was E_ERROR before
hand. And right now we didn't even start to systematically convert
all error modes in the extension directory as we started to do in
HEAD.
This can stay as it does not impact on the operation of existing
application and is actually required, otherwise previously fatal
errors will be bypassed.
That said you most likely have to fix your error_reporting anyway or
just don't care at all since you use settings that just work yor you.
Even if you were to release a new version of software today in
anticipation of a the 5.2 release few months down the road most of
your users will still use old versions while their ISP may have
already upgraded their PHP.
An argument i heared was that some applications that deal with
error_reporting might get into trouble with this. I have a solution to
that: we simply revert all the engine changes, or even better simply
rebranch 5.1.4 again and do not do any progress other than fixing bugs
and focusing on PHP 6.0.
I don't think anyone is suggesting that we revert everything, but we
do need to work on minimizing the impact of our changes on our users
in minor releases.
Ilia Alshanetsky
Advanced Internet Designs Inc.
[EMAIL PROTECTED]
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
