Bug? AdditionalMethodState suddenly stores Associations
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. Can someone please confirm that this is a bug? Cheers, Max
On 05 Nov 2013, at 19:48, Max Leske <maxleske@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
Thanks Marcus. Iâll open a bug report. On 06.11.2013, at 08:14, Marcus Denker <marcus.denker@inria.fr> wrote:
On 05 Nov 2013, at 19:48, Max Leske <maxleske@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
https://pharo.fogbugz.com/f/cases/12077/MNU-in-AdditionalMethodState-analogo... On 06.11.2013, at 08:53, Max Leske <maxleske@gmail.com> wrote:
Thanks Marcus. Iâll open a bug report.
On 06.11.2013, at 08:14, Marcus Denker <marcus.denker@inria.fr> wrote:
On 05 Nov 2013, at 19:48, Max Leske <maxleske@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
participants (2)
-
Marcus Denker -
Max Leske