On Nov 20, 2009, at 9:57 PM, stephane ducasse wrote:

Begin forwarded message:

...

From: pharo@googlecode.com Date: November 20, 2009 8:08:46 PM GMT+01:00 To: stephane.ducasse@gmail.com Subject: Re: Issue 1424 in pharo: Comparing a MethodProperties analogousCodeTo: an AdditionalMethodState is broken

Comment #10 on issue 1424 by nicolas.cellier.aka.nice: Comparing a MethodProperties analogousCodeTo: an AdditionalMethodState is broken http://code.google.com/p/pharo/issues/detail?id=1424

I mean you should - correct ScriptLoader>>#cleanUpMethods - then execute (ScriptLoader new cleanUpMethods) in an update stream to get rid of these old MethodProperties

Ok, so the #cleanUpMethods is broken right now. And there is a problem with some Service thing holding on a method. (we need reset Services in cleanUpMethods, too).

...

Then remove or deprecate MethodProperties (classify in backward compatibility or something...). Don't know if you can simply remove it, or if some binary file outs of CompiledMethod require it. Ask Marcus.

No, properties where used just internally for Pragmas. And those work. The other use of properties was in Persephone/Reflectivity (http://scg.unibe.ch/research/reflectivity) and in Bytesurgeon (http://scg.unibe.ch/research/bytesurgeon). Both of which will need some change (fort the better!) to work on Pharo anyway. So no problem. We should remove MethodProperty. I will add report to the tracker for this. Marcus -- Marcus Denker -- http://www.marcusdenker.de