Slate and Agora; building the Slate VM

[Shaping]

----- Original Message ----- 
From: "Nicolas Pelletier" <nicolas.pelletier3 at free.fr>
To: "Slate project discussion" <slate at tunes.org>
Sent: Wednesday, December 29, 2004 09:07
Subject: Re: Slate and Agora; building the Slate VM


> "Shaping" <shaping1 at bellsouth.net> writes:
>
>> >
>> > In  fact, assignments  in  Slate  are message  sends  directed to  the
>> > current  execution context:  the current  object, the  context  of the
>> > method currently executed... The above could also be written:
>> >
>> > lobby addSlot: #x.
>>
>> Right; it seems clear either way.  You can have an explicit receiver,
>> and if there is none, then it must be the lobby.  Is that right?  Or
>> are there also inner scopes where that will also work.
>
> This is  the idea, but  there can be  nested scopes, each one  being a
> delegate  of its  parent scope.  These nested  scope originate  at the
> lobby.
>
> For example, a temporary variable declared in a method is semantically
> a slot  of the method's  execution context. If that  method references
> slots or  roles of  the receiving objects,  then it is  also necessary
> that the  method context delegates  to the receiving objects  to allow
> slots and roles resolution.

So the initial context is effectively extended to all additional contexts 
referenced by its slots?

Shaping