Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:49737
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain mohiva.com designates 78.46.69.5 as permitted sender)
Message-ID: <4C928AD2.9090807@mohiva.com>
Date: Thu, 16 Sep 2010 23:23:30 +0200
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.8) Gecko/20100903 Lightning/1.0b2pre Thunderbird/3.1.2
MIME-Version: 1.0
To: internals@lists.php.net
References: <AANLkTinGFY8OobnjxEm6EDZyrqrTtvMJdceFMgAcGb7t@mail.gmail.com>
In-Reply-To: <AANLkTinGFY8OobnjxEm6EDZyrqrTtvMJdceFMgAcGb7t@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] docBlock Parser RFC
From: christian.kaps@mohiva.com (Christian Kaps)

 Am 16.09.2010 22:56, schrieb Chad Fulton:
> Hello,
>
> Based on comments from the annotations thread, I have created a
> docBlock parser RFC at http://wiki.php.net/rfc/docblockparser
>
> This RFC does not deal with annotations per se, but only with the idea
> of adding a function to the Reflection extension which would parse
> docBlocks according to a set docBlock syntax into a simple associative
> array containing three elements: short description, long description,
> and an array of tags.
>
> This is only meant to aid meta-data retrieval for classes and does not
> automatically instantiate anything objects.
>
> The RFC was meant to conform to existing convention on the formatting
> of docBlocks - so one major way to improve it would be to note any
> inconsistencies with accepted practice.
>
> Feel free to improve in any other way as well, of course.
>
> Thanks,
> Chad
>
Hi Chad,

the RFC looks for me like a built-in PHPDocumentor parser. This can be
useful. The problem for me is that I cannot parse the file level doc
block. What is with tags like @Validator('blabla'). I cannot find an
example for this scenario.

Greetings,
Christian