Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:26200 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 46477 invoked by uid 1010); 23 Oct 2006 19:34:41 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 46459 invoked from network); 23 Oct 2006 19:34:40 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 23 Oct 2006 19:34:40 -0000 Authentication-Results: pb1.pair.com smtp.mail=robert@interjinn.com; spf=permerror; sender-id=unknown Authentication-Results: pb1.pair.com header.from=robert@interjinn.com; sender-id=unknown Received-SPF: error (pb1.pair.com: domain interjinn.com from 66.11.173.122 cause and error) X-PHP-List-Original-Sender: robert@interjinn.com X-Host-Fingerprint: 66.11.173.122 unknown Linux 2.5 (sometimes 2.4) (4) Received: from [66.11.173.122] ([66.11.173.122:39958] helo=blobule.interjinn.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 3F/10-39788-F491D354 for ; Mon, 23 Oct 2006 15:34:40 -0400 Received: by blobule.interjinn.com (Postfix, from userid 2000) id 1721B5AC6B4; Mon, 23 Oct 2006 15:34:45 -0400 (EDT) To: pierre.php@gmail.com Cc: internals@lists.php.net, Marcus Boerger In-Reply-To: <20061023212931.29366acc@pierre-u64> References: <1485570655.20061023210857@marcus-boerger.de> <20061023212931.29366acc@pierre-u64> Content-Type: text/plain Content-Transfer-Encoding: 7bit Organization: InterJinn Date: Mon, 23 Oct 2006 15:34:44 -0400 Message-ID: <1161632084.28653.19.camel@blobule> Mime-Version: 1.0 X-Mailer: Evolution 2.6.1 Subject: Re: [PHP-DEV] Re: [RFC] E_DEPRECATED From: robert@interjinn.com (Robert Cummings) 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. | `------------------------------------------------------------'