Re: PHPDoc renderer not working
| From: | Antonio Carlos Venancio Junior | Date: | Sun, 28 Apr 2002 03:55:03 +0000 |
| Subject: | Re: PHPDoc renderer not working | ||
| References: | 1 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-5850@lists.php.net to get a copy of this message | ||
Jesus,
Just for curiosity: I tried about 3 times to generate documentation for
3 files and never get it to work. =)
We are just trying to continue Ulf's work and release something stable
(yeah, it's beta yet). We have a lot of improvements to make.
And I didn't know about this other project, that seems a brother of
PHPDoc (maybe a clone).
Why don't merge both works and make an "Official" PHPDoc engine using
all our skills and time ?
What do you all think about that? =)
On Sat, 2002-04-27 at 21:48, Jesus M. Castagnetto wrote:
> You might want to take a look at phpdocu.sourceforge.net
>
> In (informal) tests running PHPDoc (using the web interface, which works OK
> btw), and phpdocu (command line interface). The second one was faster, mainly
> because it did not generate intermediate XML files.
>
> When running PHPDoc on pear/Math_Vector (local version, with several
> modifications, like addition of unit tests and more examples), I had to stop
> the run after 2.5 hours (yes *hours*). In contrast phpdocu took 46 seconds to
> produce the documentation.
>
> The second documentation tool, has its quirks, but on the other hand allows
> documentation to be associated w/ packages, functions, define(), etc. And seems
> to be OK w/ tags like:
>
> @see NameOfOtherClass
>
> which PHPDoc reports as incorrect, even though it is correct according to
> JavaDoc specs. I like PHPDoc, it is more complete than phpdocu, but if I have
> to wait for hours vs seconds, then guess what will be the tool that I will use
> on a day to day basis.
--
Cya
+++
Antonio CVS .: organiKa :.
"We use only recicled bits"
floripa@organiKa.com.br
http://www.organiKa.com.br
Key fingerprint = 9F5B 31B0 C52A 4C4D 3A37 3A9F 7304 2779 5BBE B073
Attachment: [application/pgp-signature] This is a digitally signed message part signature.asc
Attachment: [application/pgp-signature] This is a digitally signed message part signature.asc