Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:26215 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 56926 invoked by uid 1010); 24 Oct 2006 01:17:41 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 56911 invoked from network); 24 Oct 2006 01:17:41 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 24 Oct 2006 01:17:41 -0000 Authentication-Results: pb1.pair.com header.from=kingwez@gmail.com; sender-id=pass; domainkeys=good Authentication-Results: pb1.pair.com smtp.mail=kingwez@gmail.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 66.249.82.229 as permitted sender) DomainKey-Status: good X-DomainKeys: Ecelerity dk_validate implementing draft-delany-domainkeys-base-01 X-PHP-List-Original-Sender: kingwez@gmail.com X-Host-Fingerprint: 66.249.82.229 wx-out-0506.google.com Linux 2.4/2.6 Received: from [66.249.82.229] ([66.249.82.229:61968] helo=wx-out-0506.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 01/23-39788-3B96D354 for ; Mon, 23 Oct 2006 21:17:41 -0400 Received: by wx-out-0506.google.com with SMTP id s18so2294907wxc for ; Mon, 23 Oct 2006 18:17:37 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=pQ5nibW5poCVg89DblwBM7/6xlIv70pEQRFQq9S3ZV+CZf9fqL6j+c3pKSmIVcH2kPGMqn/4TRexlT1yGKtKLIc/64m9SfkXlcD8GErNsKvwa0O8gb/N1oIT4fmhFOf8wGs1gyV7xpnWacUrJ3sy1Hh/9OwX+FvzME5l4B98JPI= Received: by 10.90.52.18 with SMTP id z18mr2784228agz; Mon, 23 Oct 2006 18:17:37 -0700 (PDT) Received: by 10.90.101.11 with HTTP; Mon, 23 Oct 2006 18:17:37 -0700 (PDT) Message-ID: <4e89b4260610231817r4f41e375oa46fa51b557dda2e@mail.gmail.com> Date: Mon, 23 Oct 2006 21:17:37 -0400 To: "Marcus Boerger" Cc: internals@lists.php.net In-Reply-To: <1485570655.20061023210857@marcus-boerger.de> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <1485570655.20061023210857@marcus-boerger.de> Subject: Re: [PHP-DEV] [RFC] E_DEPRECATED From: kingwez@gmail.com ("Wez Furlong") On 10/23/06, Marcus Boerger wrote: > . E_DEPRECATED: Some language featre that is likely to go away. s/likely/confirmed/. We can't speculatively deprecate a feature and then change our minds. (The {} vs [] thing with strings comes to mind). I don't think we need to set any firm ground rules for the deprecation timeline but should consider each change individually. A reasonable rule of thumb is to remove deprecated features no sooner than 1 minor release after the deprecation notice was added. Ideally, it should be in a major release. +1 > . E_STRICT any rule that reflects common strict standards, like OOP theory > that is considered harmless if not followed. For example the combination > 'abstract static' makes no sense in said theory but doesn't put our zend > engine in an unstable state. +1 Note that if we are going to treat implicit property setting as E_STRICT then we should exclude stdClass from generating those warnings, otherwise you can't work with deliberately created dynamic objects. > - We delay 5.2.0 and revisit all errors and change them according to the > new model. We also put any change into the upgrading file. +0. Let's just delay 5.2 long enough to make sure we haven't accidentally promoted E_STRICT to fatal errors in 5.2. --Wez.