as far I can see with my test its returns a RBlockNode and all the code of the node is contained inside as regular nodes. Sure its not exactly simple to do, you will have to refactor through the classes to see which class corresponds to which message but looks doable to me and not very hard to do.��

I would go through each node and find the ones that are messages then ask the class of the receiver and search for the selector and then iterate through super classes if I cannot find it. Same thing that Pharo already does with message passing.��

Do I miss something here ?��

On Thu, Aug 7, 2014 at 11:53 AM, Henrik Johansen <henrik.s.johansen@veloxit.no> wrote:

On 07 Aug 2014, at 10:41 , kilon alios <kilon.alios@gmail.com> wrote:

> cant you also use the ast to find out how exactly Pharo which object and which method it executes ?

No. Consider:

#do: aBlock
�� aBlock value

Finding the methods actually executed by this is a hard problem.
You��d at least need inferred types (to find the values of block that are actually sent to THIS #do: implementation) to even attempt to make a somewhat accurate prediction.

Cheers,
Henry