From: Yukihiro Matsumoto <matz@...>
Date: 2006-06-07T22:28:21+09:00
Subject: Re: [Bug?] set_trace_func: binding has wrong self value for return events

Hi,

In message "Re: [Bug?] set_trace_func: binding has wrong self value for return events"
    on Wed, 7 Jun 2006 19:36:43 +0900, Florian Gross <florgro@gmail.com> writes:

|Ah, hm. Any chance of having binding(n) where n=0 is the current binding 
|and n=1 is the caller's binding in standard Ruby then? Or do you feel it 
|is too much of a risk because it can be abused?

I want to make sure that this is a totally different story from
set_trace_func, OK?

Once I had discussed this issue of up-level binding with ko1 (the YARV
guy) and he said it is possible to implement it.  The only two reason
I didn't implement it are a) I didn't have good API idea, and b) it
might restrict the future implementation especially YARV.  Since he
said it didn't affect the performance, you will be able to have it in
the future - on Christmas, in some distant year ;-)

							matz.