From: Jason Roelofs <jameskilton@...>
Date: 2009-06-07T00:57:24+09:00
Subject: [ruby-core:23732] Fwd: ruby_frame in 1.8 is what in 1.9?

--0003255757de80cb9c046bb0109c
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

So I have some C++ extension code that nicely uses ruby_frame->orig_func and
ruby_frame->self to figure out the current status of the VM at a given
method call. Trying to port this to 1.9 is running into some issues, mainly
that I can't find a replacement for ruby_frame->self. I've found
rb_frame_callee() to replace ruby_frame->orig_func but cannot find out how
to get access to the current Ruby "self" object for the call.

Jason

--0003255757de80cb9c046bb0109c
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div class=3D"gmail_quote">So I have some C++ extension code that nicely us=
es ruby_frame-&gt;orig_func and ruby_frame-&gt;self to figure out the curre=
nt status of the VM at a given method call. Trying to port this to 1.9 is r=
unning into some issues, mainly that I can&#39;t find a replacement for rub=
y_frame-&gt;self. I&#39;ve found rb_frame_callee() to replace ruby_frame-&g=
t;orig_func but cannot find out how to get access to the current Ruby &quot=
;self&quot; object for the call.</div>
<div class=3D"gmail_quote"><font color=3D"#888888">
<br>Jason<br>
</font></div><br>

--0003255757de80cb9c046bb0109c--