[Vm-dev] Having a specific class for temp vectors

Clément Bera bera.clement at gmail.com
Sat Nov 21 13:40:39 UTC 2015

There is one way using reflective APIs on Contexts.

(thisContext tempAt: 1) for example.

If you think it doesn't matter then I won't bother fixing these details. I
wonder if it matters.

2015-11-21 13:52 GMT+01:00 Levente Uzonyi <leves at elte.hu>:

> On Sat, 21 Nov 2015, Clément Bera wrote:
> This is the second time I have issues with temp vectors. They are
> internal to the runtime but are exposed to the programmer. The problem is
> that the runtime have expectations with the temp vectors that the
> programmer could break, crashing the VM.
> Is it possible to mangle the temp vectors unintentionally?
> The only scenario I can imagine right now is when someone accesses these
> Arrays via #allInstances and #allObjects.
> Unless there are other ways to access them, I wouldn't change them and
> wouldn't add VM checks either.
> There are so many practically unavoidable ways to make the VM crash by the
> programmer that I don't think it'd be worth patching this one.
> Levente
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.squeakfoundation.org/pipermail/vm-dev/attachments/20151121/0996b309/attachment.htm

More information about the Vm-dev mailing list