Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:42008 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 63591 invoked from network); 21 Nov 2008 14:53:59 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 21 Nov 2008 14:53:59 -0000 Authentication-Results: pb1.pair.com header.from=sv_forums@fmethod.com; sender-id=unknown Authentication-Results: pb1.pair.com smtp.mail=sv_forums@fmethod.com; spf=permerror; sender-id=unknown Received-SPF: error (pb1.pair.com: domain fmethod.com from 69.16.228.148 cause and error) X-PHP-List-Original-Sender: sv_forums@fmethod.com X-Host-Fingerprint: 69.16.228.148 unknown Linux 2.4/2.6 Received: from [69.16.228.148] ([69.16.228.148:34362] helo=host.fmethod.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id B3/84-35761-68BC6294 for ; Fri, 21 Nov 2008 09:53:59 -0500 Received: from [83.228.56.37] (port=1326 helo=pc) by host.fmethod.com with esmtpa (Exim 4.69) (envelope-from ) id 1L3XOM-0007EG-JL for internals@lists.php.net; Fri, 21 Nov 2008 08:53:54 -0600 Message-ID: <54337AAE4E4046B297DF6189C48E3AC5@pc> To: "PHP Internals" 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> Date: Fri, 21 Nov 2008 16:53:43 +0200 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=response Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.5512 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5579 X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - host.fmethod.com X-AntiAbuse: Original Domain - lists.php.net X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - fmethod.com Subject: Re: [PHP-DEV] array_key_exists BC break From: sv_forums@fmethod.com ("Stan Vassilev | FM") > Hi! > >> Hmm, I really think we should simply maintain BC 100% but using the new > > BC 100% makes little sense - why usort can accept object but sort can't? > And functions like next/prev are useless with many types of objects. > Especialy think this through for the next >> 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. As a PHP user who'd want to migrate to 5.3 sooner than later, and uses those heavily, I'd rather not see BC breaks in a point release, even though just like you I see some WTF-s in the old behaviour. Full rethinking of this and consistently respecting the Array/Iterator interfaces would be great and needed for 6.0, though. Regards, Stan Vassilev