Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:27736
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain php.net from 88.217.2.121 cause and error)
To: Andi Gutmans <andi@zend.com>
Cc: internals@lists.php.net
In-Reply-To: <011701c7482d$a39f6910$6500a8c0@zend.2k>
References: <011701c7482d$a39f6910$6500a8c0@zend.2k>
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
Date: Sun, 04 Feb 2007 14:18:05 +0100
Message-ID: <1170595085.6832.468.camel@johannes.nop>
Mime-Version: 1.0
Subject: Re: [PHP-DEV] Syntactic improvement to array
From: johannes@php.net (Johannes =?ISO-8859-1?Q?Schl=FCter?=)

Hi Andi,

I'd like such a syntax enhancement.

These should be the results from the last time the issue was discussed:
http://devzone.zend.com/node/view/id/1474#Heading7

If I remember correct the main issues stated against it were
 - it's to perlish
 - Without keyword it's hard to find the documentation if you don't know
   that syntax

But I would still like having it :-)

johannes

On Sat, 2007-02-03 at 23:25 -0800, Andi Gutmans wrote:
> Hi,
> 
> I thought I may have brought this up a long time ago but couldn't find anything in the archives.
> For a long time already I've been thinking about possibly adding a new syntax for array(...) which would be shorter. I'd suggest
> [...]. While I am usually not in favor of having more than one way to do things, I think it'd look much more elegant especially (but
> not only) for nested arrays.
> 
> So what I'm thinking of is:
> array(1, 2, 3) == [1, 2, 3]
> array(1, 2, array("foo", "bar")) == [1, 2, ["foo", "bar"]]
> array("key" => 1, "key2" => 2) == ["key" => 1, "key2" => 2]
> 
> $arr = [1, 2, 3]
> vs.
> $arr = array(1, 2, 3)
> 
> Well enough examples given :)
> I think it's not worth doing unless there's overwhelming support as it's not desperately needed. But I'd be interested to hear
> people's thoughts. It seems implementation shouldn't be an issue but I'd have to dive a bit deeper.
> 
> Andi
>