Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:85074 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 70828 invoked from network); 16 Mar 2015 16:39:10 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 16 Mar 2015 16:39:10 -0000 Authentication-Results: pb1.pair.com smtp.mail=jan@horde.org; spf=softfail; sender-id=softfail Authentication-Results: pb1.pair.com header.from=jan@horde.org; sender-id=softfail Received-SPF: softfail (pb1.pair.com: domain horde.org does not designate 82.98.68.218 as permitted sender) X-PHP-List-Original-Sender: jan@horde.org X-Host-Fingerprint: 82.98.68.218 fra.ammma.de Linux 2.6 Received: from [82.98.68.218] ([82.98.68.218:56896] helo=fra.ammma.de) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id AA/F5-34940-B2707055 for ; Mon, 16 Mar 2015 11:39:09 -0500 Received: from ammma.de (fra2-hb [192.168.1.12]) by fra.ammma.de (Postfix) with ESMTPS id 9386D5B052B for ; Mon, 16 Mar 2015 17:39:04 +0100 (CET) Received: from mail.ammma.net (ns.ammma.mil [192.168.110.1]) by ammma.de (8.11.6/8.11.6/AMMMa AG) with ESMTP id t2GGd3F23894 for ; Mon, 16 Mar 2015 17:39:03 +0100 Received: from neo.wg.de (hydra.ammma.mil [192.168.110.1]) by mail.ammma.net (Postfix) with ESMTP id 6CBE9431BD for ; Mon, 16 Mar 2015 17:39:03 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by neo.wg.de (Postfix) with ESMTP id 0EA8F19082F1 for ; Mon, 16 Mar 2015 17:39:03 +0100 (CET) X-Virus-Scanned: Debian amavisd-new at wg.de Received: from neo.wg.de ([127.0.0.1]) by localhost (neo.wg.de [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QQRKluP21ksA for ; Mon, 16 Mar 2015 17:38:59 +0100 (CET) Received: from neo (localhost [IPv6:::1]) by neo.wg.de (Postfix) with ESMTPS id 2A53519083FA for ; Mon, 16 Mar 2015 17:38:59 +0100 (CET) Received: from 192.168.60.175 ([192.168.60.175]) by neo.wg.de (Horde Framework) with HTTP; Mon, 16 Mar 2015 17:38:59 +0100 Date: Mon, 16 Mar 2015 17:38:59 +0100 Message-ID: <20150316173859.Horde.RywHn_Pl6JrmO97ZubLJP7d@neo.wg.de> To: internals@lists.php.net In-Reply-To: User-Agent: Internet Messaging Program (IMP) H6 (7.0.0-git) Content-Type: text/plain; charset=utf-8; format=flowed; DelSp=Yes MIME-Version: 1.0 Content-Disposition: inline Content-Transfer-Encoding: 8bit Subject: Re: [PHP-DEV][RFC][VOTE][RESTART] Strict Argument Count On Function Calls From: jan@horde.org (Jan Schneider) References: Zitat von Marcio Almada : > Hi, > > As promised, the "Strict Argument Count" RFC vote was restarted: > > RFC: https://wiki.php.net/rfc/strict_argcount > PR: https://github.com/php/php-src/pull/1108 > > There was no need to update the BC break section. The only minor change was > the addition of the following section: > > https://wiki.php.net/rfc/strict_argcount#about_callbacks_invoke_and_dynamic_calls > > The voting will close in exactly 14 days counting from now. This is the > discussion summary so far http://markmail.org/thread/ol5s2vhw35ac2px3 > > Acknowledgments to Bob Weinand for offering a practical solution that will > help many in case the RFC passes. > > Thanks, > Márcio I voted no because I see the "Flexible" Interface Implementations mentioned in the RFC a valid and common use case, and the proposed solutions not suitable. You probably haven't found those during real code tests because it's commonly used to "migrate" or "extend" APIs. You add a new optional parameter to both the caller and callee of an API, with defensive coding so that both still work if that parameter is not available. This is done to not require new dependency versions. But you won't find those cases if you test complete software stacks, because in the most current version of both modules you will have the new parameter available. Beside that, your testing sample was pretty small. Jan. -- Jan Schneider The Horde Project http://www.horde.org/ https://www.facebook.com/hordeproject