Issue 6017 in pharo: Removing a trait is wrong?

Status: Accepted
Owner: marianopeck
CC: [hidden email]
Labels: Type-Bug Milestone-2.0

New issue 6017 by marianopeck: Removing a trait is wrong?
http://code.google.com/p/pharo/issues/detail?id=6017

After removing a trait, the users (classes that use that trait) now use a  
AnObsoleteXXXTrait. In addition, none of the methods that come from the  
trait were removed....

If you wanna see it in Pharo, just remove the trait  
FLTGlobalClassOrTraitSerializationTest and then browse  
FLGlobalClassSerializationTest and FLGlobalTraitSerializationTest.

I guess the correct behavario is to remove the trait from both compositons  
and the methods that come from the trait should be removed. Right?


_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker

Updates:
        Labels: Target-Trait

Comment #1 on issue 6017 by [hidden email]: Removing a trait is  
wrong?
http://code.google.com/p/pharo/issues/detail?id=6017

(No comment was entered for this change.)


_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker