Re: [Fwd: Re: PEAR framework changes for PHP5]

Quoting Daniel Convissor <danielc@analysisandsolutions.com>:

Easy, yes. But it adds a lot of unnecessary if statements. Either you use PEAR or you don't. If you like some PEAR features and want to use them in your own special customizations, great, just go ahead and copy the files to the location you want and make the modifications you desire and you're good to go.

A lot? No, one. Unnecessary? Only if you don't want your package to be able to be extended by custom drivers - which may not make sense as part of the general package sometimes. I think the way the Log packages implements things is a perfectly reasonable way to allow this, and that having it is more than worth the single if. The all-or-nothing attitude is not going to make PEAR more useful as a framework. If you want all-or-nothing, use a whole app suite (like Horde <g> - but even Horde lets you add custom drivers easily, or glue a non-Horde application into the system with a few lines of code). Also, checking class_exists() after doing the @include_once is simply good practice, since it lets you avoid errors if there's a parse error or some other reason that the class didn't actually get defined. -chuck -- Charles Hagenbuch, <chuck@horde.org> "Here, I brought some cole slaw. It's made from peeeooople! Just kidding."