Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:90403
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 74.125.82.41 as permitted sender)
MIME-Version: 1.0
Reply-To: bishop@php.net
Sender: bishop.bettini@gmail.com
In-Reply-To: <CAF+90c9nn9MQoZ237VUHwG+Jx8woawuUCJpY4ORJ4wkTtw9qDw@mail.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> <CAEYWF=6dvT44UcuP4JxQsw4Kx4_sUrdFD3b8Otbtbe_KtGMANg@mail.gmail.com>
 <CAF+90c9nn9MQoZ237VUHwG+Jx8woawuUCJpY4ORJ4wkTtw9qDw@mail.gmail.com>
Date: Fri, 8 Jan 2016 21:21:12 -0500
Message-ID: <CAEYWF=7_z=1gRDMsfJM53Aa-7+XXoSnxhS5Tf-8MPaRNUD9cYA@mail.gmail.com>
To: Nikita Popov <nikita.ppv@gmail.com>
Cc: Rowan Collins <rowan.collins@gmail.com>, Stas Malyshev <smalyshev@sugarcrm.com>, 
	PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=001a11432ede4778350528dd5d68
Subject: Re: [PHP-DEV] [RFC] On-Demand Name Mangling
From: bishop@php.net (Bishop Bettini)

--001a11432ede4778350528dd5d68
Content-Type: text/plain; charset=UTF-8

On Fri, Jan 8, 2016 at 9:39 AM, Nikita Popov <nikita.ppv@gmail.com>
wrote: I still don't like this part:
>
>
> > As written, one can't: the engine emits the error as soon as it mangles
> a variable, at most one time per startup. While that's annoying, it's also
> informative: someone's hitting your application in a way that may not
> expect.
>
> Even if it's only a single deprecation warning instead of multiple, it's
> still a deprecation warning that I, as the application author, have
> absolutely no control over. For me, a deprecation warning indicates that
> there is some code I must change to make that warning *go away*.
>
> Sure, it's informative. But it's enough to be informative about this
> *once*, rather than every time a user makes an odd-ish request.
>
> If we don't want to introduce an ini setting (against which there are good
> reasons, as you have outlined) I'd just mark this as deprecated with a nice
> red box in the documentation and upgrading guide, and commit to dropping it
> in 8.0, but not throw actual deprecation notices.
>

Agreed. Updated RFC. In summary:

   - The docs for 7.1 will say mangling is deprecated in 8.0 and that a
   polyfill to avoid a BC break will be available for download
   - The 8.0 code will completely remove all superglobal name mangling

I feel we're pretty close on this, but of course comments appreciated:
https://wiki.php.net/rfc/on_demand_name_mangling

--001a11432ede4778350528dd5d68--