Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:52662
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain croscon.com from 66.46.182.54 cause and error)
Message-ID: <4DE62B09.6070308@croscon.com>
Date: Wed, 1 Jun 2011 08:05:29 -0400
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.17) Gecko/20110414 Thunderbird/3.1.10
MIME-Version: 1.0
To: internals@lists.php.net
References: <4DE5368A.6050603@moonspot.net>	<op.vwea48kbidpuyk@clk-0081.clk-domain> <BANLkTimtbkZGOx2w9sYCO+wja5K2sD8c=g@mail.gmail.com>
In-Reply-To: <BANLkTimtbkZGOx2w9sYCO+wja5K2sD8c=g@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] RFC: Short syntax for Arrays (redux)
From: marcel.esser@croscon.com (Marcel Esser)

My kneejerk reaction to this, as no one particularly important, is to 
not allow mixing those syntaxes.

I looked at the RFC a minute ago, and I read a reference to a parallel 
solution to this being named parameters. Which, I think, is not 
accurate. The problem with the array() notation is definitely at deep 
nesting levels. The fact that arrays as arguments suddenly look nicer is 
basically just a bonus. I really just don't want to type array() 
twenty-five times in the same data structure.

PS: That is not to say that I wouldn't love named parameters; I would 
adore them. I can't count how many times I've thought that a router 
would benefit enormously from being able to do that. However, using an 
array instead worked fine - and that is cool.

- M.

On 6/1/2011 8:01 AM, Arvids Godjuks wrote:
> My personal feel about this is that yes, short arrays are not bad, but
> things like
>
> $a = new A;
> $a[array()];
>
> just scare the crap of me when I see them. To me PHP is easy on syntax
> and it's good. When I see Ruby or Python code with all it's crazy
> magic I feel sick. Still one day I will have to learn one, but that
> doesn't mean PHP should go that way too (i'm not alien to system
> languages, I had some practice with Pascal, Delphi&  C some years ago,
> just wanted to go the WEB path so migrated to PHP).
>
> If it's not too much, it would be good to avoid such strange
> constructs at all, because people are mean and they tend to do bad
> things in code.
>