Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:7949
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
To: internals@lists.php.net, john@coggeshall.org (John Coggeshall)
Date: Wed, 18 Feb 2004 11:54:21 +0100
Message-ID: <20040218115421.434ac336@localhost.localdomain>
In-Reply-To: <1077090830.30573.1.camel@coogle.localdomain>
References: <1077090830.30573.1.camel@coogle.localdomain>
Organization: Freelancer
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Subject: Re: Static weirdness..
From: paj@pearfr.org (Pierre-Alain Joye)

On Wed, 18 Feb 2004 02:53:50 -0500
john@coggeshall.org (John Coggeshall) wrote:

> http://bugs.php.net/bug.php?id=27304
> 
> Marcus says he's brought this up before, and i think it really needs
> to be addressed before PHP 5 so I'm bringing it up again. I am told
> that currently we are allowing static methods to be called from an
> object context because of a performance hit if we check every call,
> but currently because $this is undefined regardless of context there
> is no way even for the developer to check if the method was called
> properly. 

imho, this is the expected behavior. At least a notice should be raised.
I do not see a reason to define $this if a method is explicitly defined
as static (means it should not be called dynamically). Declare the
same funciton as public|private|protected and everything works fine.

pierre