On 2017-05-03 13:55, Andrey Andreev wrote:
Hi Andrea,
On Tue, May 2, 2017 at 11:08 PM, Andrea Faulds wrote:
Hey Andrey,
Andrey Andreev wrote:
I'm not surprised by the suggestion for targeting 8.0, but perhaps we
could think of a way to conditionally disable the mangling in 7.x and
then remo
Hi Andrea,
On Tue, May 2, 2017 at 11:08 PM, Andrea Faulds wrote:
> Hey Andrey,
>
> Andrey Andreev wrote:
>>
>> I'm not surprised by the suggestion for targeting 8.0, but perhaps we
>> could think of a way to conditionally disable the mangling in 7.x and
>> then remove it entirely in 8?
>> I hate
Hey Andrey,
Andrey Andreev wrote:
I'm not surprised by the suggestion for targeting 8.0, but perhaps we
could think of a way to conditionally disable the mangling in 7.x and
then remove it entirely in 8?
I hate to say INI directives, but that's surely one way for a smoother
transition.
Another
Hi,
On Tue, May 2, 2017 at 5:07 PM, Christoph M. Becker wrote:
> 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 resul
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, becaus