Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:78689
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.223.172 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <C12D441D-81CB-4270-8CE3-5A8BF2B27238@ajf.me>
References: <CALW=WECCELQOZpqB3foM6T+Qz+0v3hWT-mdTgCmGApEG4vxNcg@mail.gmail.com>
 <CAGAGxbZfDd5QaQ5iW+_pJzcHDHQztG_H_9JVyv4XT4BDaLVczw@mail.gmail.com>
 <CADUqk8UNnSL7C5_RDoNNFsdpuBoAFwdmzanaF9+GkeLN_gQkhQ@mail.gmail.com>
 <CAEZPtU44YsM1s_zJqPhAEu6cbqxh4k=A35qOd_z=XWErNf5wPA@mail.gmail.com>
 <5457AF2F.90808@php.net> <5457BDB7.8070701@garfieldtech.com>
 <CAFMT4NrgLzzpMt5Vm_Q84hXJ65U2jjqtLFm=ALYqwtiyxp0LjA@mail.gmail.com>
 <CAEZPtU4urLHc9FM0GohQJwkZD-TYKTVuPXcUMXsG5cAScHz3mw@mail.gmail.com>
 <54589A8D.3020607@sugarcrm.com> <CAEZPtU5qfcjCrcWRKW+ETF4uBp46rwVbv9nCdJoSUF+M+wKQdA@mail.gmail.com>
 <CAEPJdumXG9TC7xG8-YmGbQiwPMzwYvE_jXWvOQuNmz+U_=+ZaQ@mail.gmail.com>
 <1C3F4FA3-ABD5-4F6F-A898-F63AC1C723D5@ajf.me> <54591A76.8070302@sugarcrm.com>
 <967E30E5-71CB-40F8-9AE2-733D327DE197@ajf.me> <CAFp73XtxhW6t0k5TMa5n1ErC_7vur55Sa9oLtUM1P+X1Wugemg@mail.gmail.com>
 <545945A5.2090204@sugarcrm.com> <C12D441D-81CB-4270-8CE3-5A8BF2B27238@ajf.me>
Date: Tue, 4 Nov 2014 17:42:56 -0500
Message-ID: <CAFp73Xu++tT7fXE878i8CsibwNtiVJFcHQtzXi-iZA6=FXqeFA@mail.gmail.com>
To: Andrea Faulds <ajf@ajf.me>
Cc: Stas Malyshev <smalyshev@sugarcrm.com>, Benjamin Eberlei <kontakt@beberlei.de>, 
	Pierre Joye <pierre.php@gmail.com>, Levi Morrison <levim@php.net>, 
	PHP internals <internals@lists.php.net>, Larry Garfield <larry@garfieldtech.com>
Content-Type: multipart/alternative; boundary=001a113ecd9a7126bf05071030aa
Subject: Re: [PHP-DEV] Annotation PHP 7
From: guilhermeblanco@gmail.com ("guilhermeblanco@gmail.com")

--001a113ecd9a7126bf05071030aa
Content-Type: text/plain; charset=UTF-8

Hi,

By dealing with annotations in docblocks will force the Annotations parser
to *much* smarter than you imagine.

Currently in Doctrine Annotations implementation, @param and @Param are
considered different not only by first character to be uppercased, but
rather because a class also exist in that namespace and also because it's
an @Annotation.
Smarter I mean that you'll have to build a rejection list of
non-standardized annotations, such as phpdoc and phpunit. It also makes
pretty hard to parse emails.
You can see the list of ignored names as part of
https://github.com/doctrine/annotations/blob/master/lib/Doctrine/Common/Annotations/AnnotationReader.php#L48

Regards,


On Tue, Nov 4, 2014 at 5:20 PM, Andrea Faulds <ajf@ajf.me> wrote:

>
> > On 4 Nov 2014, at 21:31, Stas Malyshev <smalyshev@sugarcrm.com> wrote:
> >
> >> This brings the next piece of the puzzle. We have to update lexical and
> >> semantical understanding of PHP. Taking Java's approach (@) does not
> >> work in PHP, because it conflicts with error supression. Same thing
> >
> > Except for the mental context, how @ conflicts with errors? Suppression
> > is always in runtime context and applied to expressions, annotations are
> > always outside of it and apply to declarations. Unless of course you
> > want to annotate variables and closures, but I'm not sure annotating
> > expressions is such a good idea anyway
>
> At the top-level, @ is a shift/reduce conflict due to ambiguity between
> statement annotation and expression.
>
> Though it might be possible to work around that with the AST (ew).
>
> --
> Andrea Faulds
> http://ajf.me/
>
>
>
>
>


-- 
Guilherme Blanco
MSN: guilhermeblanco@hotmail.com
GTalk: guilhermeblanco
Toronto - ON/Canada

--001a113ecd9a7126bf05071030aa--