Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:115636
To: internals@lists.php.net
References: <7DA18959-3463-4AAE-ABE3-B9330FEE83D2@gmail.com>
 <CAGBsUrfoAT4CeiJvbNDczjiqRLLikdvmCfYe2BdUQDZudZ2w4w@mail.gmail.com>
 <A4C46EDC-5D29-4F3C-8F88-25C86D49B4B8@newclarity.net>
Message-ID: <0def35e8-f527-3362-2821-2535bc16f8c8@alec.pl>
Date: Fri, 6 Aug 2021 09:51:18 +0200
MIME-Version: 1.0
In-Reply-To: <A4C46EDC-5D29-4F3C-8F88-25C86D49B4B8@newclarity.net>
Content-Type: text/plain; charset=windows-1252
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] [RFC] Add parse_query_string as an alternative to
 parse_str
From: alec@alec.pl (Aleksander Machniak)

On 06.08.2021 09:45, Mike Schinkel wrote:
> I too would appreciate having a function in the PHP library that returns an array and that is named more intuitively than parse_str().
> 
> However, I would suggest naming it `parse_query()` instead of `parse_query_string()` as `_string()` is redundant and I see shorter function names being preferable when the intent of the function is clear.

I agree about the _string suffix removal. However, I know we have
parse_url() already, but parse_query() might be too generic. I would
suggest adding "http" to the name. And as we already have
http_build_query() I would rather see http_parse_query().

The RFC should target 8.2.

-- 
Aleksander Machniak
Kolab Groupware Developer        [https://kolab.org]
Roundcube Webmail Developer  [https://roundcube.net]
----------------------------------------------------
PGP: 19359DC1 # Blog: https://kolabian.wordpress.com