Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:35883
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain proposaltech.com from 66.51.199.86 cause and error)
To: internals@lists.php.net
In-Reply-To: <1476108437.20080301203629@marcus-boerger.de>
References: <234b196e0803011115t31dd004iba76f5d7ac9125b8@mail.gmail.com>
	 <1476108437.20080301203629@marcus-boerger.de>
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
Date: Sat, 01 Mar 2008 16:24:44 -0800
Message-ID: <1204417484.6084.25.camel@inspiron.local>
Mime-Version: 1.0
Subject: Re: [PHP-DEV] 5.2.5 and static calls
From: truth@proposaltech.com (Todd Ruth)


> > I compiled 5.2.5 last night and noticed that it effectively breaks all
> > static calls which have no static keyword assigned in the function's
> > definition (sorry, a bit clumsy here).       ....

How about waiting to break people's :: calls to non-static functions
until some number of releases or amount of time after traits are
introduced?  For years, making :: calls to non-static functions has
been the php way to write traits.  (OK, this lacks a lot of the
features of full traits, but it's better than nothing.)  Isn't it 
fair to provide an alternative and some time to switch to the 
alternative before making the old way fatal?

In case it isn't clear how you could write a trait, here's a
silly example:  (A full example would have more interesting code
that would be re-used by a variety of objects, but this example
demonstrates the key abilities of php without the distractions
of doing something useful.)

<?php
class Trait {
   function e() {
      print $this->g()."\n";
   }
   function f() {
      Trait::e();
   }
}

class Obj {
   function g() {
      return 5;
   }
   function h() {
      Trait::f();
   }
}

$o = new Obj;
$o->h();
?>