Issue 4568 in pharo: Ring should define = for its definition

Status: Accepted
Owner: [hidden email]
Labels: Milestone-1.4

New issue 4568 by [hidden email]: Ring should define = for its  
definition
http://code.google.com/p/pharo/issues/detail?id=4568

else we will get problem in Set.
We should have a look at sameRevisionAs: and also we should not compare the  
source of MethodDefinition because this is one disc access
Of course we should write some tests.


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

Comment #1 on issue 4568 by [hidden email]: Ring should define = for  
its definition
http://code.google.com/p/pharo/issues/detail?id=4568

Introduced the = and hash methods in the core definitions (tests included).
Latest versions are in the Ring repository.

#sameRevisionAs: will be used for change comparison.  They need to be tested


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

Comment #2 on issue 4568 by [hidden email]: Ring should define = for  
its definition
http://code.google.com/p/pharo/issues/detail?id=4568

tx :)


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

Updates:
        Status: closed

Comment #3 on issue 4568 by [hidden email]: Ring should define = for  
its definition
http://code.google.com/p/pharo/issues/detail?id=4568

(No comment was entered for this change.)


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