Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:604 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 3114 invoked from network); 2 Apr 2003 15:31:12 -0000 Received: from unknown (HELO localhost.localdomain) (65.198.110.5) by pb1.pair.com with SMTP; 2 Apr 2003 15:31:12 -0000 Received: (from andrei@localhost) by localhost.localdomain (8.11.6/8.11.6) id h32FUdv10274; Wed, 2 Apr 2003 10:30:39 -0500 X-Authentication-Warning: localhost.localdomain: andrei set sender to andrei@gravitonic.com using -f Date: Wed, 2 Apr 2003 10:30:39 -0500 To: Lance Lovette Cc: internals@lists.php.net, Andi Gutmans Message-ID: <20030402153038.GB10230@hyperion.gravitonic.com> Mail-Followup-To: Andrei Zmievski , Lance Lovette , internals@lists.php.net, Andi Gutmans References: <5.1.0.14.2.20030402091017.032db718@127.0.0.1> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4i Subject: Re: [PHP-DEV] Doc Comments cause parser errors From: andrei@gravitonic.com (Andrei Zmievski) On Wed, 02 Apr 2003, Lance Lovette wrote: > Can the purpose of doc comments be clarified? Why aren't class variables > important enough to document? I think everything exposed by a class - > variables, methods, constants, etc. - are all equally important and should > be documented. The problem is finding the storage for them. Classes/functions have internal structures that we can store doc comments in. Constants and variables, alas, don't. -Andrei http://www.gravitonic.com/ * Proximity bug: when the program crashes in front of important visitors. *