[Pharo-dev] Bug? AdditionalMethodState suddenly stores Associations

Max Leske maxleske at gmail.com
Wed Nov 6 02:53:24 EST 2013


Thanks Marcus. I’ll open a bug report.

On 06.11.2013, at 08:14, Marcus Denker <marcus.denker at inria.fr> wrote:

> 
> 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.
> 
> 	Marcus





More information about the Pharo-dev mailing list