Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:74693
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.192.50 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <2F19394F-C75C-40E8-94C3-507FAA9ADE28@ajf.me>
References: <6E3D6B3F-1BD6-42A2-B59C-12B9D6D597ED@ajf.me>
	<538B6D49.3030402@sugarcrm.com>
	<2F19394F-C75C-40E8-94C3-507FAA9ADE28@ajf.me>
Date: Mon, 2 Jun 2014 10:55:24 +0200
Message-ID: <CAH-PCH4iX99NcQCnkZv4Nmp9GMqqmB+8z_qnqg_uaSbD9SA7Hw@mail.gmail.com>
To: Andrea Faulds <ajf@ajf.me>
Cc: Stas Malyshev <smalyshev@sugarcrm.com>, PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=001a11c11d12514bf404fad68e4c
Subject: Re: [PHP-DEV] [RFC] Bare Name Array
From: tyra3l@gmail.com (Ferenc Kovacs)

--001a11c11d12514bf404fad68e4c
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On Sun, Jun 1, 2014 at 8:37 PM, Andrea Faulds <ajf@ajf.me> wrote:

>
> On 1 Jun 2014, at 19:13, Stas Malyshev <smalyshev@sugarcrm.com> wrote:
>
> > You can already do stringKey =3D> 3 :)
>
> Yes, but then you=E2=80=99ll get:
>         Notice: Use of undefined constant stringKey - assumed 'stringKey'
> in Command line code on line 1
>
> > And saving characters is not really
> > a big priority.
>
> Well, we already replaced array() with []. I think it is reasonable to
> consider saving characters in other places. It=E2=80=99s not a *big* prio=
rity, no,
> and we shouldn=E2=80=99t do it excessively, but if common cases are cumbe=
rsome, we
> should try to deal with them.
>
> Array literals with string keys and dereferencing arrays with string keys
> are extremely common in PHP. So I think this reduction would benefit most
> users, especially those who deal with JSON and the like (which I do a lot
> in my on code), as this makes declaring arrays to be serialised more
> convenient. Also, foobar: just looks nicer than =E2=80=9Cfoobar=E2=80=9D =
=3D>, especially
> when you have syntax highlighting.
>
>
originally JSON(or what it ended up as JSON) didn't require the keys to be
quoted, but it didn't took too long to bump into a reserved keyword and
realize that it is better to require the keys to be quoted:
https://www.youtube.com/watch?v=3D-C-JoyNuQJs#3m30s

--=20
Ferenc Kov=C3=A1cs
@Tyr43l - http://tyrael.hu

--001a11c11d12514bf404fad68e4c--