Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:93487
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.161.172 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <CAEKnhAEmGdNhrEJ9=2-JD+VFx5Nr+7ZK==-77myUe_6YJD=qWQ@mail.gmail.com>
References: <CAF+90c_Qi6=iQK=wjCBUreMmt9KiUyh3bZfn_roTJDEC-++EBg@mail.gmail.com>
	<CAEKnhAEmGdNhrEJ9=2-JD+VFx5Nr+7ZK==-77myUe_6YJD=qWQ@mail.gmail.com>
Date: Tue, 24 May 2016 18:37:27 +0200
Message-ID: <CAF+90c-5bx9TwOa30KQ+vNbOeuR+o71jMVGZeO5cifymMpO3bg@mail.gmail.com>
To: Jakub Zelenka <bukka@php.net>
Cc: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=001a114d749025c26c0533992c0d
Subject: Re: [PHP-DEV] Allow empty property names
From: nikita.ppv@gmail.com (Nikita Popov)

--001a114d749025c26c0533992c0d
Content-Type: text/plain; charset=UTF-8

On Sun, May 8, 2016 at 5:04 PM, Jakub Zelenka <bukka@php.net> 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 that
> more as a limitation and inconsistency between array and object decoding.
> It's more an edge case anyway so I don't think there should be a big
> concern. I think that it makes sense to hear if anyone would be against it
> in json but I think that the limitation could go away already as it has
> been discussed more than a month ago and I don't see any real objections.
>
> @Nikita: if you merge it, I will be happy to create a PR for json...
>
> Cheers
>
> Jakub
>

Sorry for the delay, I've merged the patch now:
https://github.com/php/php-src/commit/674297c7e41013c2c34d770051714518d0586271

Nikita

--001a114d749025c26c0533992c0d--