Guys,
This isn't going to change in the near future. Far too much code out there
relies on this mis-feature :)
Andi
At 08:33 AM 3/3/2004 -0500, Greg Beaver wrote:
Hi Rob,
Rob Richards wrote:
From: Greg Beaver
The PEAR base class also has this design flaw in several methods. It
has caused
> To quote Microsoft, "this is a feature, not a bug." :) Of course, if
> someone tries to call a non-static method from another completely
> unrelated class, that's just stupid. But there are cases where you
> might want to call a method from a parent class 2 levels up.
I can see calling the me
Hi Rob,
Rob Richards wrote:
From: Greg Beaver
The PEAR base class also has this design flaw in several methods. It
has caused nothing but annoying and unfixable bugs. The only good
solution is to redesign by splitting the methods into two methods, one
static, one not. It's best to do this
From: Greg Beaver
> The PEAR base class also has this design flaw in several methods. It
> has caused nothing but annoying and unfixable bugs. The only good
> solution is to redesign by splitting the methods into two methods, one
> static, one not. It's best to do this before the stable label i
Hi,
Rob Richards wrote:
Within the dom extension there are a few methods which can be called both statically and off an instantiated object.
The PEAR base class also has this design flaw in several methods. It
has caused nothing but annoying and unfixable bugs. The only good
solution is to red
