Ilia Alshanetsky wrote:
I've been reading people's replies to Marcus' RFC in regard to
E_DEPRECATED and it seems that some people have expressed the want to
delay 5.2 until mucking around with error handling is done one way or
another. My simple answer to this is no.
SIMPLE QUESTION - I've just been through the exercise of finally moving
everything to 5.1.6 after testing everything. I'd dropped back to 5.0.4
simply because 5.0.5 cause problems with nearly all of my sites and
could not be used. Are any of the 'rule changes' in 5.2 going to cause
the same compatibility problems as 5.0.5 did - if so and E_DEPRECATED is
the correct state for these changes then it needs sorting before release
rather than once again releasing code that just causes problems.
At the very least we need a proper statement of what could be broken
rather than the comments buried somewhere in the release notes ?
--
Lester Caine - G8HFL
-----------------------------
L.S.Caine Electronic Services - http://home.lsces.co.uk
Model Engineers Digital Workshop -
http://home.lsces.co.uk/ModelEngineersDigitalWorkshop/
Treasurer - Firebird Foundation Inc. - http://www.firebirdsql.org/index.php
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
