Re: Comments on bugs marked bogus

Alexey Borzov wrote:

Hi, Justin Patrin wrote:

Also, a developer should not write the example you provided. They should be using PEAR::isError().

This approach was actually promoted on this mailing list and there are several prominent packages using it. So unless you are willing to open a *really huge* can of worms I suggest you shut up now.

And I have promoted the use of PEAR::isError() on this list as well and I am willing to open this can of worms.

I agree.

Me too! OK, HTML_Template_Flexy uses is_a($foo, 'PEAR_Error') to check for errors. Lukas' own MDB uses is_a($whatever, 'mdb_common') with the "wrong" case. So the question is: is it easier to invest a *considerable* amount of time into "fixing" the packages to make them usable for stupid one-liner __autoload() or just add a note to the manual stating not to touch PEAR classes in __autoload() at all? Its not a whole lot of time if all we do if fix bugs that users find, once someone has done the checking its not really anymore work to put the one line fix in, then it is to ignore the bug and start a big argument.

Plus by acting this way we give a black eye to the PEAR community, makes us looks like a bunch of developers who are rude, and use an old coding style that will never work right in php5. -josh