[Pharo-dev] Bug? AdditionalMethodState suddenly stores Associations

Marcus Denker marcus.denker at inria.fr
Wed Nov 6 02:14:11 EST 2013

On 05 Nov 2013, at 19:48, Max Leske <maxleske at gmail.com> wrote:

> I discovered that AdditionalMethodState now (sometimes) stores Associations, not only Pragmas and Messages. That seems to work fine so fare but leads to an exception if #analogousCodeTo: is sent to a state which stores an Association.
I think this is the case when the method stored general properties (non-source visible). 

see propertyValueAt:put:

> Can someone please confirm that this is a bug?

I guess the bug is that analogousCodeTo: should handle the properties correctly. I think just ignoring them would be fine, as they
are not part of code, but meta.


More information about the Pharo-dev mailing list