Re: [PHP-DEV] Allow empty property names

On Tue, May 24, 2016 at 5:37 PM, Nikita Popov wrote: > On Sun, May 8, 2016 at 5:04 PM, Jakub Zelenka wrote: > >> Hi, >> >> I have been thinking about it and I would be ok with removing _empty_ in >> 7.1. That inconsistency is quite annoying and I never liked

Re: [PHP-DEV] Allow empty property names

On Sun, May 8, 2016 at 5:04 PM, Jakub Zelenka wrote: > Hi, > > I have been thinking about it and I would be ok with removing _empty_ in > 7.1. That inconsistency is quite annoying and I never liked it. If we can > rid of it, that would be great! I realise the BC concern but I see

Re: [PHP-DEV] Allow empty property names

Hi, I have been thinking about it and I would be ok with removing _empty_ in 7.1. That inconsistency is quite annoying and I never liked it. If we can rid of it, that would be great! I realise the BC concern but I see that more as a limitation and inconsistency between array and object decoding.

Re: [PHP-DEV] Allow empty property names

On Sat, Mar 26, 2016 at 12:17 AM, Yasuo Ohgaki wrote: > On Sat, Mar 26, 2016 at 8:08 AM, Yasuo Ohgaki wrote: > > On Sat, Mar 26, 2016 at 8:00 AM, Marco Pivetta > wrote: > >> On 25 March 2016 at 23:56, Yasuo Ohgaki

Re: [PHP-DEV] Allow empty property names

On Sat, Mar 26, 2016 at 8:08 AM, Yasuo Ohgaki wrote: > On Sat, Mar 26, 2016 at 8:00 AM, Marco Pivetta wrote: >> On 25 March 2016 at 23:56, Yasuo Ohgaki wrote: >>> >>> Hi all, >>> >>> On Sat, Mar 26, 2016 at 5:31 AM, Marco Pivetta

Re: [PHP-DEV] Allow empty property names

Hi Yasuo, On 26 March 2016 at 00:08, Yasuo Ohgaki wrote: > > Not suggesting allowing "\0" for property names: the example just shows > > creating a public, private and protected property with an empty name. > > Could you show some real world example use cases? > I've been

Re: [PHP-DEV] Allow empty property names

Hi Marco, On Sat, Mar 26, 2016 at 8:00 AM, Marco Pivetta wrote: > On 25 March 2016 at 23:56, Yasuo Ohgaki wrote: >> >> Hi all, >> >> On Sat, Mar 26, 2016 at 5:31 AM, Marco Pivetta wrote: >> > var_dump((object) ['' => 'foo']); >> >

Re: [PHP-DEV] Allow empty property names

Hi Yasuo, On 25 March 2016 at 23:56, Yasuo Ohgaki wrote: > Hi all, > > On Sat, Mar 26, 2016 at 5:31 AM, Marco Pivetta wrote: > > var_dump((object) ['' => 'foo']); > > var_dump((object) ["\0*\0" => 'foo']); > > var_dump((object) ["\0Foo\0" => 'foo']); > >

Re: [PHP-DEV] Allow empty property names

Hi all, On Sat, Mar 26, 2016 at 5:31 AM, Marco Pivetta wrote: > var_dump((object) ['' => 'foo']); > var_dump((object) ["\0*\0" => 'foo']); > var_dump((object) ["\0Foo\0" => 'foo']); Allowing null char would be too much. We reject null char in path parameters, it should be

Re: [PHP-DEV] Allow empty property names

On 25 March 2016 at 21:19, Scott Arciszewski wrote: > On Fri, Mar 25, 2016 at 1:45 PM, Nikita Popov > wrote: > > > Hi internals, > > > > Currently we do not allow (*) creating empty property names on objects, > > i.e. > > > > $obj->{''} = 42; > > >

Re: [PHP-DEV] Allow empty property names

On Fri, Mar 25, 2016 at 1:45 PM, Nikita Popov wrote: > Hi internals, > > Currently we do not allow (*) creating empty property names on objects, > i.e. > > $obj->{''} = 42; > > is illegal. While empty property names are unlikely to be useful per se, > they are

[PHP-DEV] Allow empty property names

Hi internals, Currently we do not allow (*) creating empty property names on objects, i.e. $obj->{''} = 42; is illegal. While empty property names are unlikely to be useful per se, they are problematic for deserialization of foreign formats like JSON. To avoid this issue {"": null} will