Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:589 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 7864 invoked from network); 2 Apr 2003 06:31:37 -0000 Received: from unknown (HELO jdi.jdimedia.nl) (212.204.192.51) by pb1.pair.com with SMTP; 2 Apr 2003 06:31:37 -0000 Received: from jdi.jdimedia.nl (jdi.jdimedia.nl [212.204.192.51]) by jdi.jdimedia.nl (8.12.4/8.12.4) with ESMTP id h326VZ3A024762; Wed, 2 Apr 2003 08:31:36 +0200 Date: Wed, 2 Apr 2003 08:31:35 +0200 (CEST) X-X-Sender: derick@jdi.jdimedia.nl To: Sascha Schumann cc: Andi Gutmans , Sebastian Bergmann , internals@lists.php.net In-Reply-To: Message-ID: References: <5.1.0.14.2.20030402091017.032db718@127.0.0.1> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: Re: [PHP-DEV] Doc Comments cause parser errors From: derick@php.net (Derick Rethans) On Wed, 2 Apr 2003, Sascha Schumann wrote: > On Wed, 2 Apr 2003, Andi Gutmans wrote: > > > AFAIK, doc comments are for classes and functions only. I think this is > > what's important because interfaces are functions not variables. > > Hm, so my PHP 4-stylish code would cause a parse error, if it > contained a valid character like a "*" after the initiation > sequence "/*"? Sounds indeed like something we don't want, as almost all the documentors use this. Derick -- "my other box is your windows PC" ------------------------------------------------------------------------- Derick Rethans http://derickrethans.nl/ PHP Magazine - PHP Magazine for Professionals http://php-mag.net/ -------------------------------------------------------------------------