Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:52645
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.213.170 as permitted sender)
DomainKey-Status: bad
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:from:date:message-id:subject:to
         :cc:content-type;
        b=sJpne4iPlzFMO9auAMozlsFXNOOOvJaJL5+Z/wAxYF+SlbFVQcRiK4jRCDTS4AMs61
         ibd48wxHYKSX5O4OV0tZ3c9h26qVjkW8VCEcNIJlTh73WVwK+UVwV0xBP//xw+BWT7xJ
         XcYhanGCUvAmiXxAi8wu/X24p7O3hLhvJ5fWk=
MIME-Version: 1.0
In-Reply-To: <3158105795AAC1408619EC8BA03384A90A2D1C@EXC-MBX02.leedsmet.ac.uk>
References: <CA0AE764.2E07%marcel.esser@croscon.com> <BANLkTikzAz_GEdp_n042CfgNMrWWHjWb7g@mail.gmail.com>
 <BANLkTinfH4t=2V=LaRHKKX-NRa5KbpqAZA@mail.gmail.com> <BANLkTimAuOHDZmwAaZ8M6hkCGwhwYW4Baw@mail.gmail.com>
 <3158105795AAC1408619EC8BA03384A90A2D1C@EXC-MBX02.leedsmet.ac.uk>
Date: Wed, 1 Jun 2011 04:50:43 -0500
Message-ID: <BANLkTi=KDLrWRHs8Po8MtpksDZFkGYWfwA@mail.gmail.com>
To: "Ford, Mike" <M.Ford@leedsmet.ac.uk>
Cc: Etienne Kneuss <colder@php.net>, "internals@lists.php.net" <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=0016e68deb776653e204a4a3759d
Subject: Re: [PHP-DEV] Re: RFC: Short syntax for Arrays (redux)
From: dukeofgaming@gmail.com (dukeofgaming)

--0016e68deb776653e204a4a3759d
Content-Type: text/plain; charset=ISO-8859-1

After that argument, I think I'm against ":" now too. +1 to "=>"

Could "{ }" be implemented for objects too then?.

Regards,

David

On Wed, Jun 1, 2011 at 4:36 AM, Ford, Mike <M.Ford@leedsmet.ac.uk> wrote:

> > -----Original Message-----
> > From: ekneuss@gmail.com [mailto:ekneuss@gmail.com] On Behalf Of
> > Etienne Kneuss
> > Sent: 01 June 2011 01:57
> > To: internals@lists.php.net
> > Subject: Re: [PHP-DEV] Re: RFC: Short syntax for Arrays (redux)
> >
> > +1 for a short array syntax.
> >
> > But only if you keep it consistent, PHP has always been using => for
> > key/val association, I don't see any reason to suddenly provide
> > "key":
> > "val", unless what you want is to confuse people.
>
> Hear, hear and hear, hear to that!
>
> ['a': 'b'] just feels completely un-PHP-like, and I'd be totally
> against it.
>
> If the desire is to have a "native" JSON syntax so that you can eval()
> imported JSON, then I'm completely anti that, too -- that's a case
> where I'd far rather be explicit and use json_decode(). And since, no
> matter how you slice it, you're never going to get a complete fit
> between native PHP structures and JSON encoding, I don't believe you
> should even try.
>
> I just can't see the problem with saying: PHP arrays (and maybe
> objects?) look like *this*, and if you want to import/export them
> from/to a JSON representation, there are functions to do it like
> *this*. This seems to be the perfectly sensible approach of other
> languages I've used recently (although my perl is somewhat out-of-date,
> and my python even more out-of-daterer and minimal at that!). Even
> ECMAScript is going down the route of explicit conversion with
> JSON.parse() and JSON.stringify() in ECMAScript 5!
>
> All in all, still +1 for [1, 2=>2, 'a'=>'b'], and -several million (for
> style) for any syntax involving colons.
>
> Cheers!
>
> Mike
>  --
> Mike Ford,
> Electronic Information Developer, Libraries and Learning Innovation,
> Leeds Metropolitan University, C507 City Campus,
> Portland Way, LEEDS,  LS1 3HE,  United Kingdom
> E: m.ford@leedsmet.ac.uk     T: +44 113 812 4730
>
>
>
>
>
>
> To view the terms under which this email is distributed, please go to
> http://disclaimer.leedsmet.ac.uk/email.htm
>

--0016e68deb776653e204a4a3759d--