Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:93008
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.220.48 as permitted sender)
To: Dmitry Stogov <dmitry@zend.com>, Nikita Popov <nikita.ppv@gmail.com>,
 PHP internals <internals@lists.php.net>
References: <CAF+90c_5WDZdqjdAHS+=rufE16Y+Xx-+X6Z4QquBb-64eAec6w@mail.gmail.com>
 <BY2PR0201MB1784089CBCE39900E9A3EDD5BF660@BY2PR0201MB1784.namprd02.prod.outlook.com>
Message-ID: <1f808395-7385-5bef-d379-cd56886ac85e@gmail.com>
Date: Sat, 30 Apr 2016 15:35:45 -0700
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:45.0)
 Gecko/20100101 Thunderbird/45.0
MIME-Version: 1.0
In-Reply-To: <BY2PR0201MB1784089CBCE39900E9A3EDD5BF660@BY2PR0201MB1784.namprd02.prod.outlook.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] Forbid dynamic calls to scope
 introspection/modification functions
From: smalyshev@gmail.com (Stanislav Malyshev)

Hi!

> I think it's better to keep this email as RFC, at least for documentation of BC break purpose.
> I'm not sure if we need 2 week discussion + 2 weeks voting for this.
> I think 1 week voting should be enough?

It should be at least 2 weeks discussion, as it's a language change, as
for voting, depends on when it happens. End of May, for example, has
holidays in the US. But in general if RFC happens soon-ish, there's no
reason to rush.

And, of course, this does require an RFC - this is a substantial
behavioral change that breaks BC (however weird the broken cases are).
-- 
Stas Malyshev
smalyshev@gmail.com