Mm, indeed there is just one fine.
I do not know if this is intended though as pear packages are split into several
files. I'm ccing Alexander Merz, who did the peardoc2 stuff, just in case.
As for the move there is nothing planned at the moment, afaik.
My opinion (and that's just me) is that new documentation should be be done into
peardoc2 directly and that effort has to be made to move peardoc to peardoc2 thus
phasing out peardoc.
For PECL we first have to know if the rule is one-file-per-package.
Arnaud.
> I'm looking in: peardoc/peardoc2/en/pecl/ right now and each
> extension has just one file. In regards to phpdoc, it
> would look like:
>
> peardoc/peardoc2/en/pecl/{extensionname}/*.xml
>
> Currently it's just:
>
> peardoc/peardoc2/en/pecl/{extensionname}.xml
>
> We all agree they should move but the question is when
> and how. Regarding that list Goba, just as long as for
> example:
>
> php.net/cybercash
>
> Redirects to some useful information on the matter life will
> be good for everyone. And it will remain BC :)
>
> Regards,
> Philip
>
>
> On Thu, 28 Nov 2002, Gabor Hojtsy wrote:
>
> > > The peardoc format will be phased out for peardoc2 which
> > > uses several files, that is one per function, one for constants, etc.
> > >
> > > It makes sense to document PECL in the pear manual since PECL is in pear.
> >
> > Well, actually this what I wanted to hear :) I also think that moving
> > PECL module's manuals to PECL is the way to go. Those extensions are
> > mostly rarely used... We can make up a list in the manual about moved
> > extensions and some text about why this happened / happens...
> >
> > Goba
> >
> >
>
>
> --
> PEAR Documentation List Mailing List (http://pear.php.net/)
> To unsubscribe, visit: http://www.php.net/unsub.php
>
--
PHP Documentation Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
