Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:52909
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain seancoates.com from 64.15.79.181 cause and error)
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable
Date: Sat, 4 Jun 2011 21:30:49 -0400
Message-ID: <084D2F1E-87E7-44CF-B8B6-47A250AD928D@seancoates.com>
To: PHP internals <internals@lists.php.net>
Mime-Version: 1.0 (Apple Message framework v1084)
Subject: Object and Array Literals
From: sean@seancoates.com (Sean Coates)

Hello.

I've posted a RFC concerning Object and Array Literals on the wiki: =
https://wiki.php.net/rfc/objectarrayliterals

Please read, and if you have a comment that is not already covered in =
the RFC, raise it here. I'm definitely open to discussion, but I would =
really love to keep this discussion civil.

To get the ball rolling, here are a few points that I think we need to =
discuss:

	=95 Strictness of unquoted keys.
	=95 Support =3D> in addition to : as a key:value separator.
	=95 possibility of simply not supporting the \u### syntax for =
Unicode characters in literal strings (just like the rest of PHP).
	=95 Should mixed-format (numeric and associative arrays) be =
allowed? (e.g. [1,'two':2, 3])

I beg you to keep name-calling, conclusion-jumping, and general =
hostility out of this thread. Thanks for your attention.

S=