Avi, what about 3.9's

ProtoObject #()
	Object #()

		Behavior #('superclass' 'methodDict' 'format')
			ClassDescription #('instanceVariables' 'organization')
				Class #('subclasses' 'name' 'classPool' 'sharedPools' 'environment'  
'category' 'traitComposition' 'localSelectors')
					[ ... all the Metaclasses ... ]
				Metaclass #('thisClass' 'traitComposition' 'localSelectors')

There it is, a particular non-trivial implementation, in form of open  
heart surgery ;-)

Okay the work on Collection (in the paper) doesn't count that much *but*  
the above is real-world.

/Klaus

On Fri, 01 Dec 2006 22:53:30 +0100, Av wrote:
> On 12/1/06, Klaus D. Witzel <klaus.witzel at cobss.com> wrote:
>> Hi Avi,
>>
>> I do not believe that you haven't used the trait concept for real-world
>> problems (no offense).
>
> Klaus,
>
> No offense, but I was asking for practice and you're giving me more
> theory.  My question wasn't about traits.  It was about Traits.
> There's a big difference between using a concept/pattern, and using a
> particular implementation, and I was asking about the latter.  Yes,
> given that we use traits all the time, Traits ought to be a big win,
> but I'd love to see some evidence to confirm that.
>
> Avi
>
>