Re: Comments on bugs marked bogus
| From: | Alan Knowles | Date: | Tue, 26 Jul 2005 23:49:22 +0000 |
| Subject: | Re: Comments on bugs marked bogus | ||
| References: | 1 2 3 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-38951@lists.php.net to get a copy of this message | ||
I think autoload will be fixed to allow failure - It's a known bug of
the autoload implementation ....
Saying that though, using Case sensitive names in is_a(), is a rather
trivial change..
Regards
Alan
On Tue, 2005-07-26 at 22:39 +0400, Alexey Borzov wrote:
> Hi,
>
> Justin Patrin wrote:
> >>If a comment is made on a bug flagged bogus, do the developers get a
> >>message? I added a comment to bug
> >>http://pear.php.net/bugs/bug.php?id=3197 but I am not
> >>sure if anyone
> >>will see it. Do I need to re-open the bug first?
> >
> > Yes, they should see the message even if the bug us set bogus. It
> > simply sounds like the maintainer doesn't want to make the change
> > although he gives no real reasons for it. I've added a comment fo my
> > own as well.
>
> The maintainer has his reasons. __autoload() from his point of view is bad
> voodoo very much like the infamous "magic quotes". It also shouldn't be probably
>
> triggered by using is_a() function which is deprecated (!) in PHP5. So if
> someone is bent on using __autoload() Black Magick he should take necessary
> precautions. Like only __autoload() his own classes and not touch PEAR's *at
> all* (none of them requires __autoload()!). If someone is too lazy to properly
> code his functions and understand the consequences, I have *no* sympathy for them.
>