Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:64661 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 75004 invoked from network); 8 Jan 2013 09:04:44 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 8 Jan 2013 09:04:44 -0000 Authentication-Results: pb1.pair.com smtp.mail=mike.vanriel@naenius.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=mike.vanriel@naenius.com; sender-id=pass Received-SPF: pass (pb1.pair.com: domain naenius.com designates 83.96.159.14 as permitted sender) X-PHP-List-Original-Sender: mike.vanriel@naenius.com X-Host-Fingerprint: 83.96.159.14 linux35.webawere.nl Received: from [83.96.159.14] ([83.96.159.14:34258] helo=linux35.webawere.nl) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 5C/10-08647-A21EBE05 for ; Tue, 08 Jan 2013 04:04:43 -0500 Received: from linux24.webawere.nl ([188.122.88.105] helo=webmail.web-oke.nl) by linux35.webawere.nl with esmtpa (Exim 4.80.1) (envelope-from ) id 1TsV6p-0004NB-OP; Tue, 08 Jan 2013 10:04:35 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Date: Tue, 08 Jan 2013 10:04:35 +0100 To: Stas Malyshev Cc: Rasmus Schultz , In-Reply-To: <50EBDEEE.8070605@sugarcrm.com> References: <50EBDEEE.8070605@sugarcrm.com> Message-ID: X-Sender: mike.vanriel@naenius.com User-Agent: Web-Oke Webmail/0.7.1 X-Antivirus-Scanner: Seems clean. You should still use an Antivirus Scanner Subject: Re: [PHP-DEV] [RFC] Reflection annotations reader From: mike.vanriel@naenius.com (Mike van Riel) On 08.01.2013 09:55, Stas Malyshev wrote: >> First of all, there are already plenty of established userland >> implementations - so there is really no need for this. > > On the contrary, plenty of implementations means there's a need in > this > functionality, and it might be a good idea to have one standard > implementation if it can cover like 80% of use cases. I agree with Stas on this one; I have noticed that there is a real need to parse the meta-data from a DocBlock (not just tags, descriptions as well). phpDocumentor is an example but other projects benefit from this as well.