Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:52012
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.160.42 as permitted sender)
DomainKey-Status: bad
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=date:from:to:cc:message-id:in-reply-to:references:subject:x-mailer
         :mime-version:content-type:content-transfer-encoding;
        b=j1X83mu0bJcl53loCE0nEP0IRQG7EOse2MeOyWO4jCaLPkDl9qQqeXipYc0c/de9qx
         Y3jvqqnlkgPGPChTqEgIoNFYlskKKsxqnhxJolTrz/vvXOcrFUTXyuTvBXDZzz8VYS/j
         St9/wRStCerCtDdbuhX3EXjvb+Yf5iWrM8fUw=
Date: Tue, 26 Apr 2011 11:30:57 +0800
To: David Muir <davidkmuir@gmail.com>
Cc: internals@lists.php.net
Message-ID: <26521B79ADC84D1F85EC8F6BA5F5B0EC@gmail.com>
In-Reply-To: <4DB62E7D.2010508@gmail.com>
References: <5870D50E38AE4374833F83A59ABFB59E@gmail.com>
 <4DB4847B.3080004@gmail.com> <20110424202353.GC21102@crousti>
 <BANLkTi=kG_6KiEzNwmdAFtQqLnS=jCkoKw@mail.gmail.com>
 <BANLkTi=wUHSHZoT8sv_MXSp0KjCXVe1MvA@mail.gmail.com>
 <4DB613C0.4060905@yahoo.com.au> <4DB62E7D.2010508@gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="4db63c71_519b500d_fb"
Content-Transfer-Encoding: 8bit
Subject: Re: [PHP-DEV] Call non-static method staticly raise E_STRICT,
 but why call a static method instancely won't
From: reeze.xia@gmail.com (reeze)

--4db63c71_519b500d_fb
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
Content-Disposition: inline

On 2011年4月26日星期二 at 上午10:31, David Muir wrote:
On 26/04/11 09:37, Ben Schmidt wrote:
> > > Back in PHP4 it was the only way to "simulate" an static call, but
> > > nowadays it really don't make sense at all.
> > > 
> > > class Foo {
> > >  static function toString(Bar $bar) {
> > >  return 'Foo::toString($bar)';
> > >  }
> > >  function toString() {
> > >  return '$this->toString()';
> > >  }
> > > }
> > > 
> > > $foo = new Foo();
> > > echo $foo->toString(); // instance
> > > echo Foo::toString(); // class
> > > 
> > > PHP will complain about the 2nd method (can't redefine function) but
> > > for me
> > > are 2 completely different methods.
> > > I belive the current Object Model could be improved. isn't?
> > 
> > I agree. Backward compatibility is the only reason to keep this. It's a
> > pretty compelling reason, though. It's hard to know how to phase it out
> > "non-invasively", too.
> > 
> > Ben.
> 
> Why not just deprecate it, and throw a E_STRICT warning? That's how
> we're dealing with all other future BC breaks.
+1 just like call non-static method statically did
> 
> 
> David
> 
> -- 
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
> 

--4db63c71_519b500d_fb--