Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:52002
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 74.125.82.170 as permitted sender)
DomainKey-Status: bad
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:user-agent:mime-version:to:cc:subject
         :references:in-reply-to:content-type:content-transfer-encoding;
        b=Q1fRZxn9MrdFb3aGzvkOJkVMe2/Y9SNpR13nxPTwa8c//TlkOzfycfsGanX7YzvpFr
         z/5bL/JGqrjm5vjq/AnC2DLyU8HtjaENxuAd/onQJ3O8NHWnRciUy93HykEkSwex4qS2
         krc/VkR7SnYQu1FGh6B4mjKMxKfiEvtnhjxQk=
Message-ID: <4DB4847B.3080004@gmail.com>
Date: Sun, 24 Apr 2011 22:13:47 +0200
User-Agent: Thunderbird
MIME-Version: 1.0
To: reeze <reeze.xia@gmail.com>
CC: PHP internals list <internals@lists.php.net>
References: <5870D50E38AE4374833F83A59ABFB59E@gmail.com>
In-Reply-To: <5870D50E38AE4374833F83A59ABFB59E@gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] Call non-static method staticly raise E_STRICT, but
 why call a static method instancely won't
From: keisial@gmail.com ("=?UTF-8?B?w4FuZ2VsIEdvbnrDoWxleg==?=")

reeze wrote:
> Hi, 
> I am not sure it's the right place to discuss this. someday I found I call a static method _instancely_.
> the method is just a helper method when reviewing my code. I know I do the wrong thing, but PHP doesn't
> complain about it. then I do some tests like below:

A few corrections to your test case so it actually works.
> <?php
> error_reporting(E_ALL ^ E_STRICT);
I think you want E_ALL | E_STRICT

> class A {
> public function static staticFunc() {
This is a parse error. static should be placed before function.

> echo "static";
> }
> public function instanceFunc() {
> echo "instace";
> }
> }
>
> A::instanceFunct(); // Strict Standards: Non-static method A::instanceFunc() ...
And this should be A::instanceFunc();

> $a = new A();
> $a->staticFunc(); // Just static no E_STRICT error raised
>
> I know it's the wrong way to do like these, maybe there are some historical reasons to allow these.
> I just wonder why previous method call raise E_STRICT but later not. 
>
> Yes, something could be done doesn't means we should, but we could stop things like happened.

I think it may be related to inheritance.