Re: Doc Comments cause parser errors
| From: | Andrei Zmievski | Date: | Wed, 02 Apr 2003 15:38:12 +0000 |
| Subject: | Re: Doc Comments cause parser errors | ||
| References: | 1 2 3 4 5 6 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-605@lists.php.net to get a copy of this message | ||
> >This problem bites just about any places where people used /** */ as
> >comments.
> >For example:
> >if ($a > 5) { /** This is a smart check *.
> >}
> >
> >IMO, we can't break BC this badly.
>
> Ah, that's right. We probably need to rethink our strategy then, and tie
> doc comments to the relevant tokens that follow them. Not a very easy task
> I think.
Actually the doc comment has to start with "/**\n" and end with "*/", so
the above will work just fine (because I have a rule for doc comments
with unticked_statement). The only issue right now is making rules for
doc comments before class/namespace vars and constants. If I could get
some help with that from Zeev/Andi/Stas, it'd be great.
-Andrei http://www.gravitonic.com/
A room without books is like a body without a soul.
-- Marcus Tullius Cicero (106-43 B.C.)