On 31/10/2007, Jason Johnson <jason.johnson.081 at gmail.com> wrote:
> On 10/31/07, Rob Withers <reefedjib at yahoo.com> wrote:
> >
> > I am trying to ensure that objects in one Vat don't get directly manipulated
> > by objects in other Processes.
>
> I don't see this part as too difficult, since you can't modify what
> you can't get a reference to.  But the issue is mutable globals.  The
> most obvious example here are class side variables: if multiple vats
> can see the same class and that class has class side variables that it
> mutates, then that's an issue.
>

This is not the only case. Its just a special case when two or more
processing units having access to same mutable object.
There are other problems related with reflective nature of smalltalk.
A killer example is passing reference to context (thisContext) or
stack to other vat/thread/processing units.

-- 
Best regards,
Igor Stasenko AKA sig.