Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:27858
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain troppoavanti.it from 82.188.186.202 cause and error)
Message-ID: <45C89EE2.6090800@troppoavanti.it>
Date: Tue, 06 Feb 2007 16:29:38 +0100
Organization: Wave Technologies S.r.l.
User-Agent: Thunderbird 1.5.0.9 (Windows/20061207)
MIME-Version: 1.0
To:  internals@lists.php.net
References: <011701c7482d$a39f6910$6500a8c0@zend.2k>    <28139bc0702040319p6a5cffdbi2e5999d7ebf48662@mail.gmail.com>    <45C6DCF5.1000102@dealnews.com> <45C7710D.5030205@zend.com>    <45C7747B.3070603@dealnews.com> <45C7766D.8050909@zend.com> <51602.216.230.84.67.1170718426.squirrel@www.l-i-e.com>
In-Reply-To: <51602.216.230.84.67.1170718426.squirrel@www.l-i-e.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] Syntactic improvement to array
From: t.andreatta@troppoavanti.it (Tullio Andreatta ML)

>> how it is different? How explaining array written as [] so much harder
>> that explaining array written as ()? What exactly constitutes the
>> problem?
> 
> Here's the difference:
> 
> You can Google for 'array' and learn a lot.
> 
> If you try to Google for [] you don't learn squat.
> 
> Try it and see.
> 
> So our 'newbie' at least has a good chance of figuring out array(1, 2,
> 3) on their own.  They've got must worse odds of figuring out [1,2,3]

Ok. So I propose more "searcheable" operators:

let($i, 1)                 ===     $i = 1
let($d, add($a, $b, $c))   ===     $d = $a + $b + $c
call(foo, $arg1, $arg2)    ===     foo($arg1, $arg2)

:-)

Our 'newbie' at least has a good chance of figuring out
    $a = [1,2,3]          vs.        $a = array(1,2,3)
is different than
    $a = foobar(1,2,3)

-- 
Tullio Andreatta

Disclaimer: "Please treat this email message in a reasonable way, or we
     might get angry" ( http://www.goldmark.org/jeff/stupid-disclaimers )