Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:64757
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: fail (pb1.pair.com: domain rafaeldohms.com.br does not designate 74.125.82.47 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <50ED98E4.7010009@garfieldtech.com>
References: <50ED4C18.3090806@zerocue.com>
	<CAFMT4NpvrCH1qhxcRXQpmgbTe7Tk7nBgj1ACeTjGfO6azD98gw@mail.gmail.com>
	<CAAyV7nEaOB0KZNPte3WttJV96Pp36wnGATW7ow+120PcFsd1Wg@mail.gmail.com>
	<CAFMT4NreD_UYENocdCimkb_3o72a9p9GGkNAjKyOBKUQmKABYQ@mail.gmail.com>
	<CAAyV7nGdT0UVLeaWcJMOjT8gGCOL1qy7GKcBJCY9L4Z-XpkK9g@mail.gmail.com>
	<CAFMT4NrGdYETXHOujjRJqaxq5z0ELUQZ8LXjrg=GB7d35vtjdg@mail.gmail.com>
	<50ED98E4.7010009@garfieldtech.com>
Date: Wed, 9 Jan 2013 17:29:52 +0100
Message-ID: <CAOhuFvY+Z=T6bxWQckPSCTBO-T3md359M2vyvPqLL8yYYuQfRg@mail.gmail.com>
To: Larry Garfield <larry@garfieldtech.com>
Cc: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=047d7bf0d33065089e04d2dd92cd
Subject: Re: [PHP-DEV] - True Annotations
From: listas@rafaeldohms.com.br (Rafael Dohms)

--047d7bf0d33065089e04d2dd92cd
Content-Type: text/plain; charset=ISO-8859-1

On Wed, Jan 9, 2013 at 5:20 PM, Larry Garfield <larry@garfieldtech.com>wrote:

> On 1/9/13 9:31 AM, Levi Morrison wrote:
>
>> they are nearly syntactically identical to executable code.
>>>
>>
>> "nearly" is the keyword there. They lack the ending semi-colon. Sure,
>> this might mean PHP has to actually use an abstract syntax tree, but
>> that's long overdue in my opinion. I know others disagree. This is
>> only tangentially related, so I won't say more.
>>
>
> Even if the parser is adjusted to cope with that, it's still an extremely
> subtle difference for developers to keep track of.  Consider the following
> procedural snippets:
>
> @Foo[narf]
> function something($narf) {}
>
> @Foo[narf];
> function something($narf) {}
>
> The first one says that $narf should pass @Foo validation.
>
> The second one says to call the function Foo with the string constant
> "narf", and then define a function called something().
>
> That's the sort of subtle bug that's just begging for someone to make an
> honest typo and spend the next 6 hours tracking it down, until he realizes
> what he did and proceeds to bang his head against his desk in frustration
> for missing such a "simple" error.
>
> Let's not subsidize the headache drug manufacturers with PHP syntax
> decisions. :-)
>
> --Larry Garfield
>
>

I agree with the risks here.

But i also really prefer a Token: <content>  approach then a [open token]
<content> [close token] approach

Can we use a combination? like:

@annot: Foo[narf]



-- 
Rafael Dohms
PHP Evangelist and Community Leader
http://doh.ms
http://wwwamsterdamphp.nl

--047d7bf0d33065089e04d2dd92cd--