Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:35641
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.162.182 as permitted sender)
DomainKey-Status: bad
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth;
        b=xTKFhNsw047/eYTUhtF3JHBIsKOUbkPJIlNtoc9GSYkV+Qg3ShvD76CDak5Pw4KSKUff8eJzXVxSdpSKmnAvTMaF7lxcR06qm6FxUka/r9Xvb3+yDtoDJ8FRJkP1fDaP++Bs89ycypkQbjd4IOoVHDQr7bQZV9BAAlGKa6YfDJs=
Message-ID: <1e12984d0802200028k1c53071cj750b1b539295e2c3@mail.gmail.com>
Date: Wed, 20 Feb 2008 09:28:37 +0100
Sender: stefan.marr.de@gmail.com
To: "Lars Strojny" <lars@strojny.net>
Cc: internals@lists.php.net, "=?ISO-8859-1?Q?Marcus_B=F6rger?=" <helly@php.net>, 
	"=?ISO-8859-1?Q?Johannes_Schl=FCter?=" <johannes@php.net>, 
	"Sebastian Bergmann" <sb@sebastian-bergmann.de>, 
	"Alexandre Bergel" <alexandre@bergel.eu>, 
	"Falko Menge" <falko.menge@hpi.uni-potsdam.de>, 
	"Sara Golemon" <pollita@php.net>, derick@php.net
In-Reply-To: <1203470933.3529.33.camel@localhost>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <001c01c87264$3c01b4e0$b4051ea0$@de>
	 <1203470933.3529.33.camel@localhost>
Subject: Re: [PHP-DEV] RFC: Traits for PHP
From: php@stefan-marr.de ("Stefan Marr")

Hi Lars,

> What about abstract methods in traits? I think this could be handy to
> enforce the user class implement a data getter.
>
> trait Foo {
>    public function doSomething()
>    {
>        return str_replace("foo", "bar", $this->_getString());
>    }
>    abstract protected _getString();
> }
>
> class Consumer
> {
>    use Foo;
>    protected function _getString()
>    {
>         return "foo";
>    }
> }
>
> What do you think?
I am sorry :) This part has been missing in the RFC.
But is already implemented in the patch and supposed to work exactly
like you has described it.

Kind Regards
Stefan