On Fri, 22 Feb 2008 17:39:14 +0100, Igor Stasenko wrote:

> On 22/02/2008, Andreas Raab wrote:
>> Igor Stasenko wrote:
>>  > In this respect, i think, best would be to incorporate Spoon  
>> features to VM.
>>  > As i understand (Craig, correct me if i'm wrong), a Spoon VM changes
>>  > are incremental and not breaking any compatibility.
>>
>> I'm not sure which changes you mean. If it's about imprinting, I'm no
>>  fan of that. I don't want methods automatically transferred between
>>  images - I want tools that I can use in a remote image to load and edit
>>  code just like I do in the "main" image. With the end result being a
>>  well-defined set of packages that are designed to work together.
>>
>
> I'm about marking oops while code running, to get a part of image
> which required to run your code and scrap the rest.

You know about the difference between, this my code has been executed at  
least once v.s. this my code will be executed? It is as easy to  
mechanically remove a method like #(cannotReturn: mustBeBoolean) as is  
removing any other as-yet-not-exexcuted method ...

Good luck :)

>
>