2013/7/9 Igor Stasenko <siguctua@gmail.com>

To my thinking playing with pc is awfully evil, it should be
read-only, only to allow debugger
to map it to source code. Same goes for stack pointer.

For stack pointer I don't know�use cases�so I have to agree.

Now for pc in a smalltalk debugger you can select a place in code and execute 'run to here without executing code'. It is hidden in Pharo (right menu on stack) but it is a button in Visual works. So even if evil, it is required for some functionalities. I don't know if it could be deleted like that.

Setting receiver is less evil and it may work, if receiver belongs to
same inheritance chain
as compiled method's class. But it should not be set without checking this.

Setting receiver fails in Cog and no one complains so ..

And for method's temps, it is fine.

> Thanks for answering,

--
Best regards,
Igor Stasenko.