Fwd: Re: [PEAR-DEV] Net_Socket -> 1.0.3 ?

----- Forwarded message from l.alberton@quipo.it ----- Date: Fri, 7 May 2004 20:58:03 +0200 From: Lorenzo Alberton <l.alberton@quipo.it> Reply-To: Lorenzo Alberton <l.alberton@quipo.it> Subject: Re: [PEAR-DEV] Net_Socket -> 1.0.3 ? To: Chuck Hagenbuch <chuck@horde.org> On Fri, 7 May 2004 14:26:22 -0400, Chuck Hagenbuch wrote: > It's still a potential BC break if they were using $socket- > >isError() or some such. I haven't looked at the code at all, and I don't even know what bug is causing these problems, but if the only worry of BC break is caused by those method extended by PEAR, wouldn't be enough adding those methods in your class and conditionally include PEAR in them and proxy the call to the PEAR class? Are there so many methods to implement? class Net_Socket { function isError($err) { require_once 'PEAR.php'; return PEAR::isError($err); } } Just an idea... Regards, -- Lorenzo Alberton http://pear.php.net/user/quipo ----- End forwarded message ----- -chuck -- "Regard my poor demoralized mule!" - Juan Valdez