Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:83389 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 17378 invoked from network); 21 Feb 2015 13:43:30 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 21 Feb 2015 13:43:30 -0000 Authentication-Results: pb1.pair.com smtp.mail=mailing@pascal-martin.fr; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=mailing@pascal-martin.fr; sender-id=pass Received-SPF: pass (pb1.pair.com: domain pascal-martin.fr designates 91.121.85.26 as permitted sender) X-PHP-List-Original-Sender: mailing@pascal-martin.fr X-Host-Fingerprint: 91.121.85.26 ns362529.ip-91-121-85.eu Received: from [91.121.85.26] ([91.121.85.26:53796] helo=pascal-martin.fr) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 4C/26-08895-F7B88E45 for ; Sat, 21 Feb 2015 08:43:28 -0500 Received: from [192.168.0.3] (home.squalenet.net [82.225.233.238]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by pascal-martin.fr (Postfix) with ESMTPSA id 8F4FDE011B for ; Sat, 21 Feb 2015 14:43:24 +0100 (CET) Message-ID: <54E88B7C.3090002@pascal-martin.fr> Date: Sat, 21 Feb 2015 14:43:24 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.4.0 MIME-Version: 1.0 To: internals@lists.php.net References: <54D71AD2.8030104@gmail.com> In-Reply-To: <54D71AD2.8030104@gmail.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Subject: Re: [PHP-DEV] [RFC] [VOTE] Parameter skipping RFC From: mailing@pascal-martin.fr ("Pascal Martin, AFUP") Le 08/02/2015 09:14, Stanislav Malyshev a écrit : > I'd like to announce a vote on parameter skipping RFC: > https://wiki.php.net/rfc/skipparams Hi, After discussing this RFC with other people at AFUP, we would be -1. Basically, even though not having to specify the default-value for some parameters could be useful in some situations, this approach doesn't "feel right" and we would really prefer something like named-parameters (even if this RFC is not incompatible with named-parameters and they most likely won't make it for PHP 7.0). Thanks -- Pascal MARTIN, AFUP - French UG http://php-internals.afup.org/