Hi, Theoretically, I could do the same for inheritance as well. But, that would be too complex for most cases, so it is the implicit behavior. To me, the decision for trait handling is similar.
Cheers, Doru On Sun, Jun 30, 2013 at 2:54 PM, Camillo Bruni <camillobr...@gmail.com>wrote: > On 2013-06-30, at 11:16, Sebastian Tleye <stl...@gmail.com> wrote: > > I also like this uniform because it's easier to program, > > Up to now i haven't had the need to separate them. > > > > 2013/6/30 Tudor Girba <tu...@tudorgirba.com> > >> +1 > >> > >> Keeping things uniform is a plus in this case, even though we might lose > >> some flexibility. > >> > >> Doru > > > But you know that you can do this right now? > > Object subclass: #Foo > uses: TMyTrait classTrait > > and the same on the class-side :/ > > Foo class > uses: TMyOtherTrait > instanceVariableNames: 'a b c' > > so from that point of view the current system allows for a messy/flexible > combination > of instance-side and class-side traits. > > > -- www.tudorgirba.com "Every thing has its own flow"
