Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:53370
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain analysisandsolutions.com from 166.84.1.89 cause and error)
Date: Sat, 18 Jun 2011 22:56:55 -0400
To: PHP Internals List <internals@lists.php.net>
Message-ID: <20110619025655.GA14388@panix.com>
References: <084D2F1E-87E7-44CF-B8B6-47A250AD928D@seancoates.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
In-Reply-To: <084D2F1E-87E7-44CF-B8B6-47A250AD928D@seancoates.com>
User-Agent: Mutt/1.5.20 (2009-06-14)
Subject: Re: [PHP-DEV] Object and Array Literals
From: danielc@analysisandsolutions.com (Daniel Convissor)

Hi:

I wasn't keen on earlier proposals for the [] array syntax.  Sean, your
case is laid out in a clear manner and addresses my concerns.  I like
this RFC.


> 	* Strictness of unquoted keys.

Keys should be quoted.  At the very least, unquoted keys should raise an
E_NOTICE.


> 	* Support => in addition to : as a key:value separator.

I guess.


> 	* possibility of simply not supporting the \u### syntax for Unicode
>   characters in literal strings (just like the rest of PHP).

It'd be nice to have, but not essential.


> 	* Should mixed-format (numeric and associative arrays) be allowed?
> 	(e.g. [1,'two':2, 3])

Yes, just like JSON (kind of) and PHP support.

Thanks,

--Dan

-- 
 T H E   A N A L Y S I S   A N D   S O L U T I O N S   C O M P A N Y
            data intensive web and database programming
                http://www.AnalysisAndSolutions.com/
 4015 7th Ave #4, Brooklyn NY 11232  v: 718-854-0335 f: 718-854-0409