I've published a fix to the inbox. Since the bug was related to some implementation details of the ClassBuilder and hence non-trivial, I'd appreciate if somebody could try it out and verify that traits still work as expected. I've added tests that document the bug and they run green now (with the other 80 traits tests). For details see http://code.google.com/p/pharo/issues/detail?id=443 Adrian
On Jan 17, 2009, at 15:29 , Adrian Lienhard wrote: > Well, if you just want to make your numbers be right, that's easy: > > Smalltalk allTraits do: [ :each | each instVarNamed: 'users' put: > IdentitySet new ]. > Smalltalk allClassesAndTraits do: [ :each | > each hasTraitComposition ifTrue: [ each setTraitComposition: each > traitComposition ] ]. > > This recreates all users sets. > > Adrian > > On Jan 15, 2009, at 18:20 , Damien Cassou wrote: > >> On Thu, Jan 15, 2009 at 6:18 PM, Adrian Lienhard <[email protected]> >> wrote: >>> BTW, why is this so pressing now? This bug has existed for four >>> years. >> >> We are writing an article and we have lots of metrics automatically >> calculated (and the LaTeX tables are also automatically generated). >> Since the article and the metrics are about trait users... >> >> -- >> Damien Cassou >> http://damiencassou.seasidehosting.st >> >> _______________________________________________ >> Pharo-project mailing list >> [email protected] >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > _______________________________________________ > Pharo-project mailing list > [email protected] > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project _______________________________________________ Pharo-project mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
