Re: HTTP_Upload_Error extends PEAR

Cipriano Groenendal wrote:

HTTP_Upload_Error extends PEAR Any reasons for that? If no, 0.9.0 looks like a good reason to remove it :)

And thus breaking the already stable earlier releases? HTTP_Upload_Error::isError() for example wouldn't work anymore. Alas,

but

some people might be depending upon the inheritance of the PEAR-class,

so

there's no way to remove it now, unless a new major version was to be released..

function isError(&$err) { return PEAR::isError($err); }

One down, 20+ functions to go. Fact remains, you can't simply pull away an object's parent without breaking BC at some point.Granted, it probably gives hardly any problems, but there's hardly a need to remove it, besides the `It doesn't need to be like that`-argument. Cipri The huge bloat that is added by extending the Pear class is generally a good reason, of course its not quite so bad now that the destructor bug has been fixed.

-josh