On 02.05.2017 at 12:56, Andrey Andreev wrote: > With parse_str() usage without a second parameter being deprecated, I > was looking to possibly drop the behavior where it replaces spaces and > dots with underscores in the result array, and ... As it often turns > out - it's not that simple, because it re-uses the code that handles > GPC vars. > > I didn't even know this mangling happened with GPC vars. I can only > assume that's legacy from the the register_global days, as I certainly > don't see a reason for it now. Am I missing something? > > And more importantly, can we change that? It's a significant BC break, > yes, but the current behavior is horribly broken IMO.
This issue has been already brought to the list quite a while ago[1]. IMHO, the big problem is the subtle BC break. [1] <http://marc.info/?l=php-internals&m=144416398306733&w=2> -- Christoph M. Becker -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
