Re: [RFC] E_DEPRECATED
| From: | Pierre | Date: | Mon, 23 Oct 2006 19:29:31 +0000 |
| Subject: | Re: [RFC] E_DEPRECATED | ||
| References: | 1 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-26198@lists.php.net to get a copy of this message | ||
On Mon, 23 Oct 2006 21:08:57 +0200
helly@php.net (Marcus Boerger) wrote:
> Hello internals,
>
> after recent discussions (over the last three months)I finally made
> up my mind over E_STRICT, deprecation warnings and OOP
> messages/rules. My idea proposal is to do the following:
>
> - Add a new severity E_DEPRECATED
>
> - severities are used as follows:
> . E_DEPRECATED: Some language featre that is likely to go away.
> Eearlierst removal would be two minor versions or one major version
> later. That is something that gets deprecated in 5.2 can be removed
> in 5.4.0 or 6.0.0. However both marking it as deprecated as well as
> removing it would require a consensus on the list.
+1 If removed in the next major version only. -1 otherwise.
It is already a nightmare to remember or manage the various changes in
all last minor releases.
> You may respond with constructive ideas or complaints or go voting
> for all or single points here, use -1, 0, +1 only. Please do not
> reply for the sake of responding, use pure voting instead as we are
> running out of time for 5.2.0 otherwise.
+1 for the other points, even if we can expect 5.2.0 for early 2007 ;-)
-- Pierre