Re: PHPDoc comment problem

hi andrei, there are a bunch of problems with PHPDoc right now... one of the members of my team has been in contact with the author, and he says he's a bit busy but will continue to improve it. One of our big problems, is you don't seem to be able to name files, so it uses the paths, which in our case can get a little annoying :) it also doesn't seem to like @author tags. -a -- Alex Black, Head Monkey enigma@turingstudio.com The Turing Studio, Inc. http://www.turingstudio.com vox+510.666.0074 fax+510.666.0093 Saul Zaentz Film Center 2600 Tenth St Suite 433 Berkeley, CA 94710-2522 > From: andrei@ispi.net (Andrei Zmievski) > Newsgroups: php.pear > Date: 16 Oct 2000 13:47:26 -0700 > Subject: [PHP-PEAR] PHPDoc comment problem > > Hello, > > I've started playing around with PHPDoc and I noticed a slight problem. > It seems that if I have a function/variable comment that extends over > multiple lines, only the first line is parsed. For example: > > /** > * Controls whether config values of on/true/yes and off/false/no get > * converted to boolean values automatically. > * > * @access public > */ > > What gets put in .html file is this: > > boolean $booleanize > Controls whether config values of on/true/yes and off/false/no get > > > Is this a known problem? > > -Andrei > > "C combines all the power of assembly language with > all the ease of use of assembly language" -- trad > > -- > PHP Extension and Add-on Repository (PEAR) mailing list. > Documentation can be found at http://pear.php.net/doc/pear.html > To unsubscribe, e-mail: php-pear-unsubscribe@lists.php.net from the > mail address you subscribed with. >