Hi,

I don't think that it makes sens to try copying the implementation  
from Squeak. It is too much depending on the details of the  
implementation of the classes kernel. What is independent from that  
is the small part which models trait compositions, and of course the  
tests, which will certainly be helpful.

The kernel part is quite straight forward to implement: the main  
thing is to keep track of changed or deleted methods and to  
appropriately update the method dictionaries of affected classes and  
traits. In our implementation, traits are behaviors like classes,  
with the main difference beeing that they cannot be instantiated. To  
get an idea of how this works, have a look at the Squeak  
implementation. You can also find information here [1].

Of course, the real work then comes when you want to integrate traits  
seamlessly into the environment (code browsers, SCM, changesets,  
etc.), and to have an automated bootstrapping.

Please feel free to ask questions... For papers about traits see [2].

  Cheers,
Adrian

[1] http://www.adrian-lienhard.ch/files/master.pdf
[2] http://www.iam.unibe.ch/~scg/Research/Traits/index.html

___________________
Adrian Lienhard
www.adrian-lienhard.ch


On Sep 23, 2006, at 21:18 , Diego Tubello wrote:

> Hi,
>
>
>
> We are trying to migrate Traits into Visual Age, and thought about  
> three alternatives:
>
> -          Try to copy squeak implementation into Visualk Age as it  
> is and make the tests pass.
>
> -          Copy only the tests and make an implementation of Traits  
> to make tests pass.
>
> -          Implement Traits from the ground in Visual Age.
>
>
>
> Any idea of which is the best way to do this?, or if there is a  
> better approach?
>
>
>
> Thanks,
>
> DiegoTubello
>
> Luciana Garcia Richter
>
>