Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:8350
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Message-ID: <03a601c40143$49f9a2b0$f7dea8c0@cyberware.local>
To: "Greg Beaver" <greg@chiaraquartet.net>
Cc: <internals@lists.php.net>
References: <014501c400be$2190f1f0$f7dea8c0@cyberware.local> <4045553C.3080309@chiaraquartet.net> <018301c4010f$65ffd9e0$f7dea8c0@cyberware.local> <4045DE9D.3050107@chiaraquartet.net>
Date: Wed, 3 Mar 2004 12:16:38 -0500
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] Re: more static method fun
From: rrichards@ctindustries.net ("Rob Richards")

> 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 method from a parent as valid, but from an unrelated
class I see it as a bug.
When calling a non-static method, it is allowed which it shouldnt be and
when calling a method which can be either, it should be called as a true
static method and not as a method of this unrelated object.

The crashes can be fixed, but imo it should be fixed on the engine level
rather than writing around the engine in the extensions as this behavior is
just wrong.

Rob