> Bonjour monsieur, je m'appelle Olivier Chane-Hoong j'ai 22ans, je suis actuellement
> en formation de développeur informatique à l'AFPA de la Réunion et dans le cadre
> d'un exposé, j'ai choisi comme théme PHP. Ayant téléchargé votre documentation au
> format .pdf, je voudrais vous demander la
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.
Arnaud.
> This raises up a good point. PEAR is starting to
> take shape and more and more ext
> 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...
I'm just one voice
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 n
Oh, I got it wrong then ;)
> Just to clarify just in case, I was referring to the
> move from phpdoc to peardoc and not peardoc/peardoc
> to peardoc/peardoc2.
--
PHP Documentation Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
> We talkes about this at our March Doc meeting. The problem is that the
> different doc systems mostly started out from the initial "phpdoc"
> repositories system, and developed on their own ways. Reuniting the build
> systems under one umbrella would be quite a hard task, and I don't know who
> c
