Re: Merging PHPLIB into PEAR

> Log::factory()), and it all still works. You change _no_ code in any of your > application. Just the configuration file. I agree. A simple, single place to change these kinds of parameters is definitely the way to go. It makes maintenance _so_ much easier. > With the phplib model, if I want to switch from using syslog to using sql > logging, I need to write at least one (and probably two) new subclasses, I > need > to make sure that the various subclasses are included by prepend.inc, and I > have to know enough about php classes to edit things without breaking them. Really? I did not know that. And it doesn't sound good. :( > From the point of view of someone who builds applications that other people > use, the first scenario is far easier. You keep everything in one config file, > and you keep it much simpler for people. yeppers. -a > -chuck > > -- > Charles Hagenbuch, <chuck@horde.org> > Entropy. It's what's for dinner. > > -- > PHP Extension and Add-on Repository (PEAR) mailing list. > Documentation can be found at http://pear.php.net/doc/pear.html > To unsubscribe, e-mail: php-pear-unsubscribe@lists.php.net from the > mail address you subscribed with. >