Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:83496
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.220.41 as permitted sender)
Message-ID: <54EA57A9.9090806@gmail.com>
Date: Sun, 22 Feb 2015 14:26:49 -0800
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:31.0) Gecko/20100101 Thunderbird/31.4.0
MIME-Version: 1.0
To: Paul Dragoonis <dragoonis@gmail.com>
CC: PHP Internals List <internals@lists.php.net>
References: <54D71AD2.8030104@gmail.com>	<54E88B7C.3090002@pascal-martin.fr> <CAKxcST9qmum7+jziEeod20Ycb72WXtzrLa49ZnFOWmWmewozOQ@mail.gmail.com>
In-Reply-To: <CAKxcST9qmum7+jziEeod20Ycb72WXtzrLa49ZnFOWmWmewozOQ@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] [RFC] [VOTE] Parameter skipping RFC
From: smalyshev@gmail.com (Stanislav Malyshev)

Hi!

> I see a LOT of "no" votes against this RFC but can't find the thread
> outlining the reasoning for such resistence.

I think my attempts to explain that this was a step towards named
params, not a contradiction with them, failed - people read it, say "we
understood it" and the say "no, we don't want it, we want named params
instead!". Well, let's hope somebody (not me) writes a patch for named
params instead. In the meantime, 7.0 will have neither.
-- 
Stas Malyshev
smalyshev@gmail.com