Re: documenting and releasing a PHP extension

On Sat, 23 Jun 2001, Dan Libby wrote: > I'm preparing to release another PHP C extension. I would like to do > it as correctly as possible, but i have some questions. > > 1) Is there a better place to ask these questions? ie, is there a > list or forum for discussing 3rd party extensions? > > 2) Is there any standard place for putting (or listing) 3rd party C > extensions to php? My first thought is to place it on sourceforge, > but how do I let people know it is available? > > 3) Is PEAR setup to handle C extensions? Or only php code? The > documentation I've seen is unclear on this point, but as I see only > php code in /pear, I assume the latter. Can someone say definitively? > > 4) Is there a standard process for creating documentation for > extension API's? I've seen mention of the "proto" keyword and some > vague references to a "doc/genfuncsummary script" in the > CODING_STANDARDS document distributed with php. However, that script > does not appear to be distributed with the source. Can I get access > to this, or must I roll my own system? What do others do? > > Thanks for any help. Please send replies to dan@libby.com and cc the > list if u like. PEAR can deal with C extensions. You need a package.xml file with the right tags and the recent (4.0.7 I guess) "pearize" script, take a look at pear/PEAR for an example. - Stig