Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:84820
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain basereality.com from 209.85.160.169 cause and error)
MIME-Version: 1.0
In-Reply-To: <CAOsHV+s8WFbAVgQXnSJWHzPTLKQnMZUktO5-5bsBZ8a=AhhHQg@mail.gmail.com>
References: <CAOsHV+uYLVuOhva_wpyGouHg5c8+ajko0m8CN1aU2HARcyga3A@mail.gmail.com>
	<CAOsHV+s8WFbAVgQXnSJWHzPTLKQnMZUktO5-5bsBZ8a=AhhHQg@mail.gmail.com>
Date: Sun, 15 Mar 2015 11:33:02 +0000
Message-ID: <CA+kxMuSmd30hOQAnfXjXF7io_aEM4aCnTGigYuF0KZeDarz3bQ@mail.gmail.com>
To: marcio3w@gmail.com
Cc: PHP internals <internals@lists.php.net>
Content-Type: text/plain; charset=UTF-8
Subject: Re: [PHP-DEV][RFC][VOTE] Strict Argument Count On Function Calls
From: danack@basereality.com (Dan Ackroyd)

On 15 March 2015 at 06:59, Marcio Almada <marcio.web2@gmail.com> wrote:
> Hi,
>
> I received some requests to update the RFC with more information about BC
> breaks + possible minor adjustments regarding dynamic function calls.


Please can you stop abusing the RFC process?

This RFC is attempting to change the language. You received the
information about the BC breaks weeks ago, they aren't new items that
you just heard about for the first time today.. You opened the voting
and then closed it immediately when you realised the vote wasn't going
to sail through.

You're now making changes to the RFC and proposing to re-open voting
on the same day. How are people meant to have time to read and think
about the changes?

It's also going to be impossible for people to try the patch out, or
to measure it for performance hit.

The problem this RFC fixes is not a big enough problem to justify
making decisions about the language at the last minute, particularly
as the last version of the RFC I read breaks a whole load of valid
code.

cheers
Dan