Re: Re: [RFC] E_DEPRECATED

From: Date: Mon, 23 Oct 2006 19:34:44 +0000
Subject: Re: Re: [RFC] E_DEPRECATED
References: 1 2  Groups: php.internals 
Request: Send a blank email to internals+get-26200@lists.php.net to get a copy of this message
On Mon, 2006-10-23 at 21:29 +0200, Pierre wrote: > 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. +1 with same sentiments. Cheers, Rob. -- .------------------------------------------------------------. | InterJinn Application Framework - http://www.interjinn.com | :------------------------------------------------------------: | An application and templating framework for PHP. Boasting | | a powerful, scalable system for accessing system services | | such as forms, properties, sessions, and caches. InterJinn | | also provides an extremely flexible architecture for | | creating re-usable components quickly and easily. | `------------------------------------------------------------'

« previous php.internals (#26200) next »