Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:106229
MIME-Version: 1.0
References: <c-17aa9-jy55foba-cru125=b8ivs7@2.gethop.com> <CAF+90c9ZRT92UVK5ig_wkkgEzXAWG+fgYdNR6KGj8zKcuKRJ+A@mail.gmail.com>
In-Reply-To: <CAF+90c9ZRT92UVK5ig_wkkgEzXAWG+fgYdNR6KGj8zKcuKRJ+A@mail.gmail.com>
Date: Thu, 18 Jul 2019 09:08:05 +0200
Message-ID: <CAOWwgpmYsqY_E5Mh7KM88ByuDTJmzF69xqYAmHzFOt4rrHAeSA@mail.gmail.com>
To: Nikita Popov <nikita.ppv@gmail.com>
Cc: Arnold Daniels <arnold.adaniels.nl@gmail.com>, PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="000000000000250b01058def46fa"
Subject: Re: [PHP-DEV] Stop replacing dots with underscores in query, post and
 cookie parameters for PHP 8?
From: nicolas.grekas+php@gmail.com (Nicolas Grekas)

--000000000000250b01058def46fa
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Le mar. 16 juil. 2019 =C3=A0 09:51, Nikita Popov <nikita.ppv@gmail.com> a =
=C3=A9crit :

> On Tue, Jul 16, 2019 at 3:40 AM Arnold Daniels <
> arnold.adaniels.nl@gmail.com>
> wrote:
>
> > Hi,
> >
> > PHP replaces dots with underscores for $_GET, $_POST and $_COOKIE. This
> > behavior once made sense because of Register globals. The explanation i=
n
> > the manual also still implies that query and post parameters are
> converted
> > to variables (see
> >
> https://php.net/manual/en/language.variables.external.php#language.variab=
les.external.dot-in-names
> ).
> > Register globals has been removed since 5.4.0 and thus this behavior
> serves
> > little purpose.
> >
> > I think it would be good to remove the conversion in PHP 8, as it's a
> > general cause of confusion and annoyance for anyone who comes across it=
.
> >
> > Is there a good reason to keep this behavior in PHP 8?
> >
>
> This has been discussed a few times already, and I think that everyone
> agrees that this behavior should go, but not necessarily on the migration
> path. There is an RFC here:
> https://wiki.php.net/rfc/on_demand_name_mangling
> I think that the latest version of that RFC, that basically proposes to
> drop the behavior and tell people to use a polyfill is fine.
>


The RFC doesn't tell about parse_str(), while this is the userland variant
of this.
I think it could be useful to make parse_str accept a third argument
starting with PHP 7.4!
That would allow userland code to opt-in for the new behavior asap, and
would provide the core implementation for ppl that want to keep the current
behavior for PHP8.

Makes sense?

Nicolas

--000000000000250b01058def46fa--