Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:89990
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 74.125.82.50 as permitted sender)
MIME-Version: 1.0
Reply-To: bishop@php.net
Sender: bishop.bettini@gmail.com
In-Reply-To: <5687FEC0.8010103@gmail.com>
References: <CAEYWF=7Px5LWGdGqHdmVwt_tWd-XAUhZzUFoOa_rDmtpi88BAA@mail.gmail.com>
 <CAF+90c_T7KZPy3h-yiak+09NZMF7UR9h8fjc-E-Vf7btFfBnLw@mail.gmail.com>
 <CAEYWF=6A4mpS5Y1KU+jZzU9hyS=ViysS_O6_5p6vMb8zmQHgvQ@mail.gmail.com> <5687FEC0.8010103@gmail.com>
Date: Mon, 4 Jan 2016 11:16:49 -0500
Message-ID: <CAEYWF=6dvT44UcuP4JxQsw4Kx4_sUrdFD3b8Otbtbe_KtGMANg@mail.gmail.com>
To: Rowan Collins <rowan.collins@gmail.com>, Stas Malyshev <smalyshev@sugarcrm.com>, 
	Nikita Popov <nikita.ppv@gmail.com>
Cc: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=001a114b6fc47be2f60528847406
Subject: Re: [PHP-DEV] [RFC] On-Demand Name Mangling
From: bishop@php.net (Bishop Bettini)

--001a114b6fc47be2f60528847406
Content-Type: text/plain; charset=UTF-8

On Sat, Jan 2, 2016 at 11:45 AM, Rowan Collins <rowan.collins@gmail.com>
wrote:

> On 02/01/2016 03:09, Bishop Bettini wrote:
>
>> But, even without a setting, there's an escape hatch: userland can
>> polyfill
>> the mangling behavior using extract.  The updated RFC demonstrates an
>> algorithm.
>>
>
> I'm not that comfortable with requiring / encouraging the use of extract()
> - a rather awkward function which clobbers your local variable space in
> unpredictable ways - to write the polyfill. The fact that the clobbering is
> necessary / useful for extract() is wholly unrelated to the need for BC in
> super-global arrays.
>
> It would be more useful to expose a method or regex constant to userland
> so that the mangling can actually be done in place on appropriate arrays:
>

I've updated the on-demand name mangling RFC
<https://wiki.php.net/rfc/on_demand_name_mangling> in light of all feedback
so far.  The crux being:

   - If an app requires name mangling:
      - As of 7.1, the app will get one E_NOTICE per startup warning of the
      impending removal of name mangling
      - As of 8.0, the app will need to include a polyfill package and add
      one line of code to its bootstrap.  (Safe to include the
polyfill prior to
      the release of 8.0.)
   - If an app does not need name mangling, there's no effect, no notices,
   nothing needed

Thanks!

--001a114b6fc47be2f60528847406--