Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:35713
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain lorenso.com from 67.18.161.90 cause and error)
Message-ID: <47BE0A09.6060702@lorenso.com>
Date: Thu, 21 Feb 2008 17:32:25 -0600
User-Agent: Thunderbird 2.0.0.9 (Windows/20071031)
MIME-Version: 1.0
To: Internals Mailing List <internals@lists.php.net>
CC: php@stefan-marr.de
References: <001c01c87264$3c01b4e0$b4051ea0$@de> <698DE66518E7CA45812BD18E807866CE014A8D9D@us-ex1.zend.net> <47BE0664.8060304@stefan-marr.de>
In-Reply-To: <47BE0664.8060304@stefan-marr.de>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: Traits for PHP ... Why can't every Class be a Trait?
From: dante@lorenso.com ("D. Dante Lorenso")

All,

I can imagine a case where you would want to box common functionality 
into a trait and be able to use that trait as a class also.  Will we end 
up with a lot of classes like this?:

class SomeClass {
   use SomeTrait;
}

What's wrong with making all 'Class'es be 'Trait's and the only thing 
which makes a Trait a Trait is when you use it as such?

class MyClass {
   trait SomeClass;
}

In other words, why mustn't a trait be instantiable?  Why can't every 
Class be a Trait?

-- Dante