Re: why don't most classes extend PEAR?

Martin Jansen wrote: > > On Thu, 06 Sep 2001 15:28:56 -0700, greg keraunen wrote: > > >In my case, I'm avoiding extending PEAR for now because I don't have > >control over php installion on my hosted site and can't run pearize or > >dl(PEAR.so). > > To use PEAR.php as the base class for your projects you don't need > to have the ability to use dl() or pearize. Simply use > > <?php > require_once "PEAR.php"; > > class MyClass extends PEAR > { > > } > ?>. The problem is that I downloaded the current cvs tree and put it in my include_path. The current PEAR.php calls dl(PEAR.so) which is not on my system. I have the old PEAR.php in /usr/local/lib/php from my PHP 4.0.5 install. But I have removed that from include_path in order to avoid ambiguities about which PEAR classes will load. I don't understand what is going on with the PEAR.php file and why it has been changed to require PEAR.so. Is this a permanent feature or have I bypassed an install procedure that would recreate a normal looking PEAR.php after using pearize, etc.? - greg