Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:42005 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 11951 invoked from network); 21 Nov 2008 09:02:25 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 21 Nov 2008 09:02:25 -0000 Authentication-Results: pb1.pair.com header.from=mls@pooteeweet.org; sender-id=unknown Authentication-Results: pb1.pair.com smtp.mail=mls@pooteeweet.org; spf=permerror; sender-id=unknown Received-SPF: error (pb1.pair.com: domain pooteeweet.org from 88.198.8.16 cause and error) X-PHP-List-Original-Sender: mls@pooteeweet.org X-Host-Fingerprint: 88.198.8.16 bigtime.backendmedia.com Linux 2.6 Received: from [88.198.8.16] ([88.198.8.16:54954] helo=bigtime.backendmedia.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 5F/7E-06451-02976294 for ; Fri, 21 Nov 2008 04:02:25 -0500 Received: from localhost (unknown [127.0.0.1]) by bigtime.backendmedia.com (Postfix) with ESMTP id 6A2E9414405A; Fri, 21 Nov 2008 09:04:39 +0000 (UTC) X-Virus-Scanned: amavisd-new at backendmedia.com Received: from bigtime.backendmedia.com ([127.0.0.1]) by localhost (bigtime.backendmedia.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XvLwgeWUTY6d; Fri, 21 Nov 2008 10:04:38 +0100 (CET) Received: from [192.168.1.55] (f053003244.adsl.alicedsl.de [78.53.3.244]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: mls@pooteeweet.org) by bigtime.backendmedia.com (Postfix) with ESMTP id C84624144059; Fri, 21 Nov 2008 10:04:37 +0100 (CET) Cc: =?ISO-8859-1?Q?Johannes_Schl=FCter?= , Felipe Pena , Dmitry Stogov , PHP Internals Message-ID: <5991E942-3EC9-4BFE-8059-C50735DBAF4A@pooteeweet.org> To: Stanislav Malyshev In-Reply-To: <4926775D.5090904@zend.com> Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v929.2) Date: Fri, 21 Nov 2008 10:00:45 +0100 References: <4900DB81.4000805@zend.com> <4900E150.1010607@dynom.nl> <49018FC3.90302@gmail.com> <1224854888.19390.89.camel@goldfinger.johannes.nop> <490609A1.7090400@gravitonic.com> <1225199800.878.0.camel@localhost> <3F3445975B55414BB4A214B32E178657@pc> <4A4FE9BC-F000-4AEE-A68C-8EFEA9DCD154@pooteeweet.org> <4910D3E5.4020406@zend.com> <237D5067-10C6-4D25-8CCF-FEF9FE44F6F6@googlemail.com> <1225973406.5465.18.camel@felipe> <4925F83E.2060609@zend.com> <1227231361.3043.9.camel@goldfinger.johannes.nop> <4926775D.5090904@zend.com> X-Mailer: Apple Mail (2.929.2) Subject: Re: [PHP-DEV] array_key_exists BC break From: mls@pooteeweet.org (Lukas Kahwe Smith) On 21.11.2008, at 09:54, Stanislav Malyshev wrote: >> bigger release (presumably PHP 6.0) and come up with a set of >> interfaces for objects that allow them to more sensibly work with >> functions. > > We already have set of interfaces. They aren't just used > consistently. And that's a bug. We shouldn't let BC to prevent us > from fixing bugs. Especially BC with things that were never > documented to work at the first place and are working in half of > functions and don't work in others without any logical order. I am just worried that we do not have enough time to really think this through all the way. So in the end we might end up having to break BC once more in PHP 6.0. Also its not like we are fixing these bugs because users were submitting bug tickets about this (or have they?). regards, Lukas Kahwe Smith mls@pooteeweet.org