not sure that it does not introduce side effect but Association>>isLiteral ^ self key isLiteral and: [self value isLiteral] Fix the problem. stef On Mar 22, 2010, at 10:25 PM, Stéphane Ducasse wrote:
eliot
Your changes fixed some of the problems. Now I tried to fix the test testAnalogousCodeTo in MethodPropertiesTest and the expression returns false.
(#zork->'hello') analogousCodeTo: (#zork->'hello') -> false
(#zork->'hello') = (#zork->'hello') -> true
Stef
On Mar 22, 2010, at 6:20 PM, Eliot Miranda wrote:
Oops. Find attached.
2010/3/22 Cyrille Delaunay <cy.delaunay@gmail.com> try in a Pharo-1.0-10515-rc3 image :
|set| set := Set new. Collection withAllSubclasses do: [:aClass | set addAll: aClass methods ].
It will raise an exception telling: "MessageNotUnderstood: ByteSymbol>>analogousCodeTo:". Indeed, in the code of CompiledMethod >> = , the message 'analogousCodeTo:' is send to a symbol.
I opened an Issue: http://code.google.com/p/pharo/issues/detail?id=2185
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
<Object-analogousCodeTo.st>_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project