>>>
>>> I am working now on making the #after work so that one can get with #value
>>> the return of the method…
>>>
>>> I now have a version where it works for Message Sends correctly *and* were
>>> #after on Method works better (the compilation errors should be fixed).
>>>
>>> But #value f
--- Begin Message ---
> On 23 Nov 2018, at 15:19, Marcus Denker wrote:
>
>
>
>> On 23 Nov 2018, at 14:59, Marcus Denker wrote:
>>
>>
>>
>>> On 23 Nov 2018, at 13:40, Manuel Leuenberger
>>> wrote:
>>>
>>> Hi,
>>>
>>> I stumbled upon another MetaLink scenario that I am unsure how to
>>
> On 23 Nov 2018, at 14:59, Marcus Denker wrote:
>
>
>
>> On 23 Nov 2018, at 13:40, Manuel Leuenberger
>> wrote:
>>
>> Hi,
>>
>> I stumbled upon another MetaLink scenario that I am unsure how to implement.
>> I want to track method invocations, with receiver, arguments, selector, and
>
Awesome! I am looking forward to it.
Cheers,
Manuel
> On 23 Nov 2018, at 14:59, Marcus Denker wrote:
>
>
>
>> On 23 Nov 2018, at 13:40, Manuel Leuenberger
>> wrote:
>>
>> Hi,
>>
>> I stumbled upon another MetaLink scenario that I am unsure how to implement.
>> I want to track method invo
> On 23 Nov 2018, at 13:40, Manuel Leuenberger wrote:
>
> Hi,
>
> I stumbled upon another MetaLink scenario that I am unsure how to implement.
> I want to track method invocations, with receiver, arguments, selector, and
> return value (maybe even signaled exception). I can track the method
Hi,
I stumbled upon another MetaLink scenario that I am unsure how to implement. I
want to track method invocations, with receiver, arguments, selector, and
return value (maybe even signaled exception). I can track the method input with
a MetaLink installed on an RBMethodNode like this:
MetaLi
