Okay, I think that I fixed everything mentioned previously. I've removed all the doc for classes written in PHP (sorry about that).
changes.tar contains files for five classes written in C: MongoId, MongoDate, MongoCode, MongoRegex and MongoBinData. The diff (changes.patch) corrects the MongoDB url in global.ent and updates some existing documentation. http://github.com/beaddy1238/phpdoc/blob/master/changes.tar http://github.com/beaddy1238/phpdoc/blob/master/changes.patch If someone could patch these into the exisiting documentation, I'd really appreciate it. Thanks! Kristina On Tue, Mar 10, 2009 at 3:42 PM, Hannes Magnusson < hannes.magnus...@gmail.com> wrote: > On Tue, Mar 10, 2009 at 18:10, Kristina Chodorow <krist...@10gen.com> > wrote: > > 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. > > That is _exactly_ the purpose of PEAR. > Abstract "annoying" tasks to packages. Be it a wrapper for C > extensions (there are *lot* of that kind of packages there) or logic. > > PECL is for C code. PEAR is for PHP code. > > -Hannes > > -- > PECL development discussion Mailing List (http://pecl.php.net/) > To unsubscribe, visit: http://www.php.net/unsub.php > >
