This raises up a good point. PEAR is starting to take shape and more and more extensions are moving into PEAR/PECL. What do we do? PECL extensions are documented in the PEAR manual, not here.
Since most of these extension moves are so recent, (4.3.0), we should probably continue to document them until they are moved into the PEAR manual. I think you should do PECL ones as well as it will really help the peardoc team and provide a good framework. Soon after they are moved into the PEAR manual then dummy/filler pages can simply refer to them. In fact, how about creating filler pages for all PECL extensions? Moved extensions are mentioned in NEWS: http://www.php.net/php4news One thing to keep in mind is the PEAR manual uses our old method of one xml file per extension as opposed to reference.xml, config.xml, etc. but the peardoc team can merge them or ideally have them split up too. Regards, Philip p.s. Once many of these are moved out, maybe we can create (full) pdf's again! :) On Thu, 28 Nov 2002, Friedhelm Betz wrote: > Hi, > > maybe noticed I am working on incorporating configure-options in the > Reference-Part of the manual. To avoid wasting my time, I want to > exclude those modules/extensions no longer available. > > Any pointer to an overview, or should I search php-dev? > > Thanks > > Friedhelm > > > -- > PHP Documentation Mailing List (http://www.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
