Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:91960
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.213.66 as permitted sender)
MIME-Version: 1.0
Sender: yohgaki@gmail.com
In-Reply-To: <CAGa2bXbQ++K6fpWsfwD=iLLxABo27Am41yUCFmSEoB67gGk9fQ@mail.gmail.com>
References: <CAF+90c_Qi6=iQK=wjCBUreMmt9KiUyh3bZfn_roTJDEC-++EBg@mail.gmail.com>
 <CAKws9z2iMp33XmFZdshAgWX07J3Yh41cDV73CyEBh2pOceNFkg@mail.gmail.com>
 <CADyq6sLdsT2k=L-ZYEZUP7N4uSFvUday21wkN2kSzPFePo3Row@mail.gmail.com>
 <CAGa2bXbPXWkwsswOMJ3i14KP-ej_HWABbJkHyeO43HVgd4c34w@mail.gmail.com>
 <CADyq6sLzgfBT_6LkLvSS92+YJnKKgSw5XBk8JbL5Z6cuaUjZCw@mail.gmail.com> <CAGa2bXbQ++K6fpWsfwD=iLLxABo27Am41yUCFmSEoB67gGk9fQ@mail.gmail.com>
Date: Sat, 26 Mar 2016 08:17:12 +0900
Message-ID: <CAGa2bXbgoFZD5-YFz3M9sNDy6C1g3J7+JJNAzj_dUJ3QVwPf1A@mail.gmail.com>
To: Marco Pivetta <ocramius@gmail.com>
Cc: Scott Arciszewski <scott@paragonie.com>, Nikita Popov <nikita.ppv@gmail.com>, 
	PHP internals <internals@lists.php.net>
Content-Type: text/plain; charset=UTF-8
Subject: Re: [PHP-DEV] Allow empty property names
From: yohgaki@ohgaki.net (Yasuo Ohgaki)

On Sat, Mar 26, 2016 at 8:08 AM, Yasuo Ohgaki <yohgaki@ohgaki.net> wrote:
> On Sat, Mar 26, 2016 at 8:00 AM, Marco Pivetta <ocramius@gmail.com> wrote:
>> On 25 March 2016 at 23:56, Yasuo Ohgaki <yohgaki@ohgaki.net> wrote:
>>>
>>> Hi all,
>>>
>>> On Sat, Mar 26, 2016 at 5:31 AM, Marco Pivetta <ocramius@gmail.com> 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 rejected like path parameter. IMHO.
>>
>>
>> The sequence "\0*\0" means "protected property", while the sequence
>> "\0Foo\0" means "private property of class Foo": that's been the case for a
>> looooong time :-)
>
> Oh. Was it? I've never used and encountered this. Thanks.
> I'll avoid null char as I use PostgreSQL JSONB extensively, though.
>
>> 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?

You mean PHP converts private/protected property to this form, not
currently used as JSON string.
I understand your point!

It would be good for PHP users supporting null chars in names, then.

Regards,

--
Yasuo Ohgaki
yohgaki@ohgaki.net