Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:115650
MIME-Version: 1.0
References: <7DA18959-3463-4AAE-ABE3-B9330FEE83D2@gmail.com>
 <CAGBsUrfoAT4CeiJvbNDczjiqRLLikdvmCfYe2BdUQDZudZ2w4w@mail.gmail.com>
 <f45b55bd-1ce6-4e28-9eda-13c2603c8eb2@www.fastmail.com> <cd281c28-f380-29e2-7393-c08012afda1f@gmail.com>
In-Reply-To: <cd281c28-f380-29e2-7393-c08012afda1f@gmail.com>
Date: Fri, 6 Aug 2021 20:42:51 +0100
Message-ID: <CAGBsUrcouFmbfcwb+inYJvsdDmDfWwjnGZ=YzCLUoZVAQg2=wg@mail.gmail.com>
To: Rowan Tommins <rowan.collins@gmail.com>
Cc: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="00000000000058ef3405c8e93ee7"
Subject: Re: [PHP-DEV] Re: [RFC] Add parse_query_string as an alternative to parse_str
From: tekiela246@gmail.com (Kamil Tekiela)

--00000000000058ef3405c8e93ee7
Content-Type: text/plain; charset="UTF-8"

Hi Internals,

Thanks for all the feedback. I have changed the name to http_parse_query as
it looks like more people prefer that name. I have also updated
https://wiki.php.net/rfc/parse_str_alternative for 8.2 (sorry for the
confusion) and I added open points.
I hear two concerns currently about this RFC. Please note that my intention
was to provide a simple drop-in replacement. However, I agree that there is
a lot of room for improvement in this area, so I highly appreciate your
comments on how we can best tackle these open points.
I will not open this RFC for voting any time soon, as I want to let the
conversation run through to see what other options/concerns people have.
Please feel free to share your comments on what you think is the right path
to improve this functionality in PHP.

Regards,
Kamil

--00000000000058ef3405c8e93ee7--