Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:26226 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 6944 invoked by uid 1010); 24 Oct 2006 14:23:42 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 6929 invoked from network); 24 Oct 2006 14:23:42 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 24 Oct 2006 14:23:42 -0000 Authentication-Results: pb1.pair.com header.from=iliaal@gmail.com; sender-id=pass; domainkeys=good Authentication-Results: pb1.pair.com smtp.mail=iliaal@gmail.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 64.233.166.180 as permitted sender) DomainKey-Status: good X-DomainKeys: Ecelerity dk_validate implementing draft-delany-domainkeys-base-01 X-PHP-List-Original-Sender: iliaal@gmail.com X-Host-Fingerprint: 64.233.166.180 py-out-1112.google.com Linux 2.4/2.6 Received: from [64.233.166.180] ([64.233.166.180:41416] helo=py-out-1112.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 57/9F-30135-BE12E354 for ; Tue, 24 Oct 2006 10:23:40 -0400 Received: by py-out-1112.google.com with SMTP id t32so186224pyc for ; Tue, 24 Oct 2006 07:23:28 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:in-reply-to:references:mime-version:content-type:message-id:cc:content-transfer-encoding:from:subject:date:to:x-mailer:sender; b=o9yx48zIshy6bFCFF+L3dXFyrIYQq0Ybf1v8E+9+HqYQt++JS2xVN6T6d8iqjNPQTqUsmT4yr+23957V38iYosEwcbsBteBSn/axsz2znCgjTJF4q6m0mCDom9We6XC0SPmU/Bw0w7ATN9eBelenr+mn3w/PCCV1PF9pQpNTaMU= Received: by 10.65.251.17 with SMTP id d17mr7496592qbs; Tue, 24 Oct 2006 07:23:26 -0700 (PDT) Received: from ?192.168.1.6? ( [74.108.69.82]) by mx.google.com with ESMTP id e17sm746898qbe.2006.10.24.07.23.25; Tue, 24 Oct 2006 07:23:25 -0700 (PDT) In-Reply-To: <453D93C8.7020907@lsces.co.uk> References: <453D93C8.7020907@lsces.co.uk> Mime-Version: 1.0 (Apple Message framework v752.3) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-ID: Cc: internals@lists.php.net Content-Transfer-Encoding: 7bit Date: Tue, 24 Oct 2006 10:23:17 -0400 To: Lester Caine X-Mailer: Apple Mail (2.752.3) Sender: Ilia Alshanetsky Subject: Re: [PHP-DEV] Why 5.2 should not be delayed for E_DEPRECATED From: ilia@prohost.org (Ilia Alshanetsky) For this particular purpose there is a fairly detailed README.UPDATE_5_2 that details the major functionality changes that have happened in PHP 5.2 On 24-Oct-06, at 12:17 AM, Lester Caine wrote: > Ilia Alshanetsky wrote: >> I've been reading people's replies to Marcus' RFC in regard to >> E_DEPRECATED and it seems that some people have expressed the want >> to delay 5.2 until mucking around with error handling is done one >> way or another. My simple answer to this is no. > > SIMPLE QUESTION - I've just been through the exercise of finally > moving everything to 5.1.6 after testing everything. I'd dropped > back to 5.0.4 simply because 5.0.5 cause problems with nearly all > of my sites and could not be used. Are any of the 'rule changes' in > 5.2 going to cause the same compatibility problems as 5.0.5 did - > if so and E_DEPRECATED is the correct state for these changes then > it needs sorting before release rather than once again releasing > code that just causes problems. > > At the very least we need a proper statement of what could be > broken rather than the comments buried somewhere in the release > notes ? > > -- > Lester Caine - G8HFL > ----------------------------- > L.S.Caine Electronic Services - http://home.lsces.co.uk > Model Engineers Digital Workshop - http://home.lsces.co.uk/ > ModelEngineersDigitalWorkshop/ > Treasurer - Firebird Foundation Inc. - http://www.firebirdsql.org/ > index.php > > -- > PHP Internals - PHP Runtime Development Mailing List > To unsubscribe, visit: http://www.php.net/unsub.php > > Ilia Alshanetsky