Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:49741 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 88196 invoked from network); 16 Sep 2010 23:25:41 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 16 Sep 2010 23:25:41 -0000 Authentication-Results: pb1.pair.com header.from=chadfulton@gmail.com; sender-id=pass; domainkeys=bad Authentication-Results: pb1.pair.com smtp.mail=chadfulton@gmail.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.214.170 as permitted sender) DomainKey-Status: bad X-DomainKeys: Ecelerity dk_validate implementing draft-delany-domainkeys-base-01 X-PHP-List-Original-Sender: chadfulton@gmail.com X-Host-Fingerprint: 209.85.214.170 mail-iw0-f170.google.com Received: from [209.85.214.170] ([209.85.214.170:55802] helo=mail-iw0-f170.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id F4/04-15036-477A29C4 for ; Thu, 16 Sep 2010 19:25:41 -0400 Received: by iwn37 with SMTP id 37so1697245iwn.29 for ; Thu, 16 Sep 2010 16:25:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:mime-version:received:in-reply-to :references:from:date:message-id:subject:to:cc:content-type; bh=4Yoky6gBUY5/wHyx5UTz5Nl1AazpF1ug33F82q8ZuHw=; b=OHSPEhv6lnTFznUf1Z6T485P9Ccu/aJcWOEXueKEK3Dqk/Eefnnc8DK1AVJvnG/Xi6 lOl1QjmwbPDC5cRQh+OuK2BE55Jzs/1ZgLfXwu/FIkLPCFmAKSCz2ryk3XI3ukU4oFpM zfK2TOSqA55bX+riyB29yKpcPdgdT8t8eJuTk= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; b=cnvX2svHV7BarL1OOlKR/20a9MzLQX0zWKcYPMRHIdQ7BjggVoaBhbOqygNjF1F6XJ 7vHykwGJfg7mEiDLXdy2TUb0CirEiw47jh7atx6ef4N04/++6MHW5Fd/hTd41oSieuS7 ktZ/j1MRm+EE8cGLaCrSZMBNmyp1s+jRF/I5M= Received: by 10.231.118.28 with SMTP id t28mr3401291ibq.131.1284679538116; Thu, 16 Sep 2010 16:25:38 -0700 (PDT) MIME-Version: 1.0 Received: by 10.231.0.234 with HTTP; Thu, 16 Sep 2010 16:25:18 -0700 (PDT) In-Reply-To: <4C928AD2.9090807@mohiva.com> References: <4C928AD2.9090807@mohiva.com> Date: Thu, 16 Sep 2010 16:25:18 -0700 Message-ID: To: Christian Kaps Cc: internals@lists.php.net Content-Type: text/plain; charset=ISO-8859-1 Subject: Re: [PHP-DEV] docBlock Parser RFC From: chadfulton@gmail.com (Chad Fulton) Hello! That is a good point, there would be no file-level doc block in the RFC. Here is my reasoning for not including it in the RFC: Since the motivation for this came from the desire for metadata for PHP structures, it seemed inappropriate to include metadata at the file level (since it's not a php structure). As for the @Validator('blahbla'), I had thought it could be replicated with: /** * @Validator blahbla */ How to do multiple arguments would be up to user-land functions that used the parsed doc comments, but one possibility is: /** * @Validator foo bar baz */ then when you wanted to retrieve these, you could do explode(' ', $tags['Validator']); or similar. However, more specific syntax could be added to allow "arguments" in the doc block tags. I just feel like in this case absolute simplicity is important. Chad On Thu, Sep 16, 2010 at 2:23 PM, Christian Kaps wrote: > 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 > > -- > PHP Internals - PHP Runtime Development Mailing List > To unsubscribe, visit: http://www.php.net/unsub.php > >