Re: Issue 1642 in pharo: Class >> #obsolete should be renamed to Class >> #becomeObsolete

Updates:
        Status: WontFix

Comment #4 on issue 1642 by [hidden email]: Class >> #obsolete  
should be renamed to Class >> #becomeObsolete
http://code.google.com/p/pharo/issues/detail?id=1642

becomeObsolete sounds as it would be a version of #become:... and #obsolete  
is not related to become.

So I would vote for keeping the old name for now.


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