Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:83419
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.216.172 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <54E88B7C.3090002@pascal-martin.fr>
References: <54D71AD2.8030104@gmail.com>
	<54E88B7C.3090002@pascal-martin.fr>
Date: Sat, 21 Feb 2015 19:47:40 +0000
Message-ID: <CAKxcST9qmum7+jziEeod20Ycb72WXtzrLa49ZnFOWmWmewozOQ@mail.gmail.com>
To: "Pascal Martin, AFUP" <mailing@pascal-martin.fr>
Cc: PHP Internals List <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=001a11376a721ab1f2050f9e7149
Subject: Re: [PHP-DEV] [RFC] [VOTE] Parameter skipping RFC
From: dragoonis@gmail.com (Paul Dragoonis)

--001a11376a721ab1f2050f9e7149
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

I see a LOT of "no" votes against this RFC but can't find the thread
outlining the reasoning for such resistence.

Could someone link me to this somehow?

On Sat, Feb 21, 2015 at 1:43 PM, Pascal Martin, AFUP <
mailing@pascal-martin.fr> wrote:

> Le 08/02/2015 09:14, Stanislav Malyshev a =C3=A9crit :
>
>> 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 "fee=
l
> right" and we would really prefer something like named-parameters (even i=
f
> 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/
>
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>

--001a11376a721ab1f2050f9e7149--