Re: Mongo Extension Doc Patch

I'm using and updating the C code. The C code just has basic functions, like "connect to the database" or "query the database." Since I find writing in PHP a bit quicker than writing in C, I wrote more complex functions in PHP, but they still call the C functions to actually interact with the database. I haven't created a PEAR package because PEAR requires the extension to be written in just PHP, and the PHP I wrote isn't standalone, it requires the C code to work. Should I create two projects (one PECL, one PEAR)? That doesn't seem to make sense, though, as the PHP needs the C to run and the C is annoying to use without the PHP. On Tue, Mar 10, 2009 at 11:55 AM, Philip Olson <philip@roshambo.org> wrote: > But, I'm a little confused... is this documentation for code written in > PHP? If so that seems wrong... we only document APIs and not optional PHP > libraries. Please explain the situation and why the OOP API isn't written in > the extension itself. > > > This documentation is (almost all) for PHP code. I didn't intend for > people to use the C functions directly, instead I expect them to include the > mongo.php file and use the nicer API that provides. I understand if that > isn't something PECL documentation covers, though, and I can resubmit just > the changes to the functions section. Sorry about that. > > > It looks like you've created two different projects, one PECL extension and > one PEAR package. If the PECL API won't be updated then consider creating a > mongo PEAR package and documenting said code there. > > Regards, > Philip > > >