Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:74699
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain ravensight.org from 209.85.223.179 cause and error)
To: "'Andrea Faulds'" <ajf@ajf.me>,
	"'PHP internals'" <internals@lists.php.net>
References: <6E3D6B3F-1BD6-42A2-B59C-12B9D6D597ED@ajf.me>
In-Reply-To: <6E3D6B3F-1BD6-42A2-B59C-12B9D6D597ED@ajf.me>
Date: Mon, 2 Jun 2014 09:56:34 -0500
Message-ID: <001f01cf7e72$d94e1ba0$8bea52e0$@org>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
Thread-Index: Ac99w0n2kfYFI2LcQUyCDWRIxqhKZQArjdEQ
Content-Language: en-us
Subject: RE: [PHP-DEV] [RFC] Bare Name Array
From: bryan@ravensight.org ("Bryan C. Geraghty")

I don't like it because I think it reduces the readability of array
definitions too much. 

My preference is syntax that makes it easy for me to convey the meaning of
my code to YOU, at a glance. In general, this means consistency. Typing a
couple of extra characters for the sake of readability is perfectly
reasonable to me.

As far as the, "we did that, so we should do this" argument I've been seeing
a lot: Your feature should stand on its own within the ENTIRE context of the
language. Many mistakes have been made in the lifetime of PHP. Don't point
at any one feature and say that it's a good reason to include this feature.

Bryan