Andi Gutmans wrote:
At 07:55 PM 11/18/2003 -0500, Mike Robinson wrote:
Ilia Alshanetsky wrote:
> On a related note, since a major PHP version is now being
> released, perhaps it is the time to finally remove old
> deprecated functionality that in many cases deprecated for
> years. I propose that we agree on a certain version as a
> minimum and remove all deprecated functionality that was
> marked as such prior to that version.
I think this is a good idea, and this really should happen
before PHP-5 goes gold. The negative impact and effects can
be minimized by a prominent entry in the migration and/or
NEWS documents.
Just to make it clear, doing an if() at run-time for E_STRICT isn't
something we'd want to do in every place. It's best if we'd do it
mostly during compilation stage or only in places at run-time where it
really isn't a big deal. Some of the suggestions didn't take this into
account.
About the deprecation, I think it's OK to have a mode where deprecated
functionality doesn't work, but we should definitely leave it in for
now to allow people to make an easier transition. Maybe the best
solution is to allow people something like --disable-deprecated which
gets rid of them, and connect the deprecated functionality to E_STRICT.
Andi
I agree with --disable-deprecated, it seems to be the best option. Do
you think it would be relevant to have a php.ini option for this?
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
