Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:48041 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 58886 invoked from network); 21 Apr 2010 14:07:06 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 21 Apr 2010 14:07:06 -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 209.85.218.219 cause and error) X-PHP-List-Original-Sender: sv_forums@fmethod.com X-Host-Fingerprint: 209.85.218.219 mail-bw0-f219.google.com Received: from [209.85.218.219] ([209.85.218.219:45435] helo=mail-bw0-f219.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 0B/E4-63467-8860FCB4 for ; Wed, 21 Apr 2010 10:07:05 -0400 Received: by bwz19 with SMTP id 19so15386bwz.1 for ; Wed, 21 Apr 2010 07:07:00 -0700 (PDT) Received: by 10.204.134.193 with SMTP id k1mr517810bkt.165.1271858820374; Wed, 21 Apr 2010 07:07:00 -0700 (PDT) Received: from pc ([83.228.56.37]) by mx.google.com with ESMTPS id a11sm1967475bkc.9.2010.04.21.07.06.58 (version=SSLv3 cipher=RC4-MD5); Wed, 21 Apr 2010 07:06:59 -0700 (PDT) Message-ID: <9102D8214A9042BFAD507219161F8660@pc> To: "Derick Rethans" , "Ryan Panning" Cc: , "Stanislav Malyshev" , "Adi Nita" References: <4BCE44B8.6060600@zend.com> <4BCEFC93.7010508@gmail.com> Date: Wed, 21 Apr 2010 17:06:55 +0300 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="ISO-8859-1"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.5843 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5579 Subject: Re: [PHP-DEV] A critique of PHP 6 From: sv_forums@fmethod.com ("Stan Vassilev") >> > > 4. PARAMETER ORDER. >> > Two letters: BC. >> > Changing variable order in an existing function is a big fat BC break. >> > And >> > if we put such a bomb into a new version, what would be the incentive >> > for >> > people to use it? So that apps would have to be shipped in 2 versions, >> > for >> > the old php and the new php? >> >> Is this something that could be fixed if it's moved to a namespace? The >> new >> "alias" can have the "correct" order but original function can have the >> old >> order. > > No, it would me having two implementations. > > Derick There's only one way to both maintain BC during a "transition" period, and fix flaws to prepare for the next 10 years. And that's having two implementations. The original one will gradually be deprecated and eventually removed. Regards, Stan Vassilev