Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:52646
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.212.42 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:date:message-id:subject:from:to
         :cc:content-type:content-transfer-encoding;
        b=Cen3O0rQuvJz+UgDFDO3J3S4Uls5mMfp9wqi5/thEu/Z4PE/5szOupLXGg9fSjGGBW
         ML2gFjQZ2sCkFAaCF1bl5XKwgHC530cU1eohYUeDsZ+uYzksBGzewjoRCkGr4nXcVQma
         Zin8ovUjZkVo84pYqEb4Zw1Lk9Lu44vZ9S/LQ=
MIME-Version: 1.0
In-Reply-To: <BANLkTi=KDLrWRHs8Po8MtpksDZFkGYWfwA@mail.gmail.com>
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>
	<BANLkTi=KDLrWRHs8Po8MtpksDZFkGYWfwA@mail.gmail.com>
Date: Wed, 1 Jun 2011 11:55:10 +0200
Message-ID: <BANLkTimrX8iHYBzjnfyPToa+-jZ=RkvJxA@mail.gmail.com>
To: dukeofgaming <dukeofgaming@gmail.com>
Cc: "Ford, Mike" <M.Ford@leedsmet.ac.uk>, Etienne Kneuss <colder@php.net>, 
	"internals@lists.php.net" <internals@lists.php.net>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Subject: Re: [PHP-DEV] Re: RFC: Short syntax for Arrays (redux)
From: rumi.kg@gmail.com (Rune Kaagaard)

Big +1 on the patch. The ":" although a better choice would be
asymmetric to how its done inside array().

On Wed, Jun 1, 2011 at 11:50 AM, dukeofgaming <dukeofgaming@gmail.com> wrot=
e:
> After that argument, I think I'm against ":" now too. +1 to "=3D>"
>
> 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 =3D> 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=3D>2, 'a'=3D>'b'], and -several million (=
for
>> style) for any syntax involving colons.
>>
>> Cheers!
>>
>> Mike
>> =A0--
>> Mike Ford,
>> Electronic Information Developer, Libraries and Learning Innovation,
>> Leeds Metropolitan University, C507 City Campus,
>> Portland Way, LEEDS, =A0LS1 3HE, =A0United Kingdom
>> E: m.ford@leedsmet.ac.uk =A0 =A0 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
>>
>