Re: something I noticed re:licenses.

On Fri, 19 Jan 2001, Chuck Hagenbuch wrote: > Quoting Kristian Koehntopp <kris@koehntopp.de>: > > > Not code, only the API. I have obligations to an installed base, > > but these cover only the API, not the actual code that is being > > run behind that API. This is an essential difference. > > Okay, that's a valid distinction. But I am still of the opinion that PEAR will > not be best served by conforming to PHPLIB's API. Ummm... Seeing that I'm not terribly experienced in such matters, I feel like this is a little too simple for me to see (I've gotta be extremely wrong about this :-) ... Why not work the internals and all valuable things in PHPLib into PEAR. Take those things which are needed. Then, release the newer version of PHPLib (8.0?) as a wrapper to PEAR functions for compatibility sake. Is this totally off the mark? I Use PHPLib for almost every site I've programmed. Infact, I have a class which I've written which I've used in almost anything I've done having to do with databases. I'd really like to contribute it to PEAR, but it's based heavily on PHPLib's DB class. Plus I don't quite understand all this ERROR foolishness or the :: notation (I'm used to just extending classes). I would really like to see some (if not all) of PHPLib's functionality in PEAR. -peace --- BEGIN GEEK CODE BLOCK ----------+---------- GAT d- s:+ !a C++$ UL/S/I/B++++$ P+ | "In the ongoing battle between objects L++ E- W+(+++) N K- w(---) O-- M@ | made of aluminum going hundreds of V(--) PS+++ PE Y+ PGP@ t++ 5 X+ R- | miles per hour and the ground going tv+ b- DI++++ D+(+++) G e>++ h--- | zero, the ground has yet to lose." r++ z+>+++ - END GEEK CODE BLOCK ---+