[Vm-dev] Re: [squeak-dev] Obtaining a current context in primitive
eliot.miranda at gmail.com
Mon May 3 00:56:41 UTC 2010
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.
(& redirecting to vm-dev)
On Sat, May 1, 2010 at 7:32 AM, Igor Stasenko <siguctua at gmail.com> wrote:
> Hello guys,
> i am looking for a way, how i can obtain an activeContext oop in my
> primitive function.
> An activeContext variable is directly accessible for interpreter code,
> but not for plugins.
> So, i need some indirect way to retrieve it, to avoid patching the
> Interpreter for exposing it.
> What i actually want is to switch an active context to a different
> one, but remember a previously active,
> so it can be restored later.
> Best regards,
> Igor Stasenko AKA sig.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Vm-dev