Re: Comments on bugs marked bogus
| From: | Alexey Borzov | Date: | Tue, 26 Jul 2005 21:23:33 +0000 |
| Subject: | Re: Comments on bugs marked bogus | ||
| References: | 1 2 3 4 5 6 7 8 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-38945@lists.php.net to get a copy of this message | ||
Hi,
Justin Patrin wrote:
Alexey, stop nit-picking on stupid non-related issues. Explain why this bug will not be fixed from a technical perspective and we'll leave you alone. Saying that PHP is broken and/or this is a PHP bug is not sufficient. Saying that you don't like how the user is using the function is not sufficient. A small, non-intrusive change should not be causing this much crap.This bug report does not describe a bug in QuickForm package. It describes a error triggered in a third-party __autoload() function. This error does not even affect QuickForm's behaviour at all! At most this is a feature request, as the author of the last comment on the bug (smith at pooteeweet dot org) properly mentioned. "Please change this thing in QuickForm so that *my* function works properly". I also pointed out the obvious problem: QuickForm isn't the only package that will prevent such a function from working. If you'd like to make all packages brain-dead-__autoload()-compatible, then you should start by 1) Specifying how third-party __autoload() function works with PEAR packages 2) Writing down all requirements for packages' compatibility with this function 3) Making a list of packages that may be incompatible with such function Then you should consider whether "fixing" the packages found in (3) will break their backwards compatibility. Then you should write an RFC documenting changes to coding standards to support __autoload(). This is definitely less fun than harassing yours truly in pear-dev, but having __autoload()-compatibility in coding standards is the only way if you want to promote the report in question to actual "bug" status.
With the time you're spending writing all of these hurtful messages you could have comitted the fix and and probably fixed a few more bugs while you're at it.Of the two bugs opened now, one deals with Javascript on OS X browsers [1] and I cannot fix it 'cause I don't have access to any box running OS X and the other [2] deals with Flexy renderer which is unmaintained. I am not familiar enough with Flexy to properly fix it. If you would like to provide some help with these bugs... [1] http://pear.php.net/bugs/bug.php?id=3224 [2] http://pear.php.net/bugs/bug.php?id=2637