Derick Rethans wrote:
On Sun, 14 May 2006, Marcus Boerger wrote:
That said i am about to not remove E_STRICT from E_ALL and MFH the php
6.0 to item just now.
See: http://oss.backendmedia.com/PhP60 (add E_STRICT to E_ALL DONE (dmitry))
Since this is for the benefit of the users to prevent issues with
changes in behavior from my opinion it is best to do this behavior
change as early as possible, which is in my opinion 5.2 anyway.
That said i'll let it in and if there is no valid argument against, i
will put it into the NEWS file and the newly started README.UPDATE_5_2.
Yup, I agree on this.
The key point is that with reading the upgrading guide people will know
howto get the old behavior. I do not quite agree that this change is
necessary, but I guess the "ALL" in "E_ALL" implies it includes
everything, so its logical on that level.
regards,
Lukas
PS: Obviously this will be quite painful for PEAR, but I guess that is
partially the point here: create some pains to nudge people towards
writing PHP5 only code. Or maybe its just about covering our asses
against users who complain about us removing deprecated functionality
after a few minor releases.
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
