Igor,<div><br></div><div> surely if you're writing primitives that do context manipulation these should be internal to Interpreter, just like the block value and process/semaphore primitives. IMO its a really really bad idea to expose contexts through InterpreterProxy.</div>
<div><br></div><div>(& redirecting to vm-dev)</div><div><br><br><div class="gmail_quote">On Sat, May 1, 2010 at 7:32 AM, Igor Stasenko <span dir="ltr"><<a href="mailto:siguctua@gmail.com">siguctua@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">Hello guys,<br>
<br>
i am looking for a way, how i can obtain an activeContext oop in my<br>
primitive function.<br>
An activeContext variable is directly accessible for interpreter code,<br>
but not for plugins.<br>
So, i need some indirect way to retrieve it, to avoid patching the<br>
Interpreter for exposing it.<br>
<br>
What i actually want is to switch an active context to a different<br>
one, but remember a previously active,<br>
so it can be restored later.<br>
<font color="#888888"><br>
--<br>
Best regards,<br>
Igor Stasenko AKA sig.<br>
<br>
</font></blockquote></div><br></div>