Re: Documention problems
| From: | Tomas V.V.Cox | Date: | Sun, 12 Aug 2001 12:31:09 +0000 |
| Subject: | Re: Documention problems | ||
| References: | 1 2 3 4 5 6 7 8 9 10 11 12 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-1400@lists.php.net to get a copy of this message | ||
Alexander Merz wrote:
>
> > Make PHPDoc to support multiple classes per file? (urgent priority
> It is only a speed issue. Ulf already test the behavior of parsing multiple
> class in one file and the the result was, that this could require a lot of time
> to track multiple classes ( up to 500% time per file and more!). He find a
> algorythm, which is really fast, to change this would result in a execution
> time of > 30min going through all PEAR-classes on a AMD K6/2-400, 128 MB ( at
> the moment ~300sec ).
Only a speed issue? So, we can not document PEAR because the doc tool is
not yet optimized? What's the problem of having a backgroud process
running all the night?
> Only solution for this means to write PHPDoc in C (or ASM), i wish you a lot of
> fun ( in Spain? Enviously...)
Ulf had part of a C parser implemented and some people offered help on
finish it, so it's seem that we finally will have it.
> I see, that a lot of the PEAR programmers wrote wrong PHPDoc comments, i'm the
> only one, who really runs PHPDoc over PEAR?
>
If I cann't document classes like PEAR, DB, XML_Parser, Getopt, Upload,
etc why would I want to do it?
Tomas V.V.Cox