[e-lang] A trivial naming problem: too many Scopes?

[Kevin Reid]

On Jul 10, 2005, at 13:18, Mark Miller wrote:

> Kevin Reid wrote:
>> In E-on-CL's compiler, there is a third thing. Unlike the above two, 
>> it is not public. It is the compile-time equivalent of a Scope, 
>> containing information about the internal names (or known constant 
>> values) of variables, the FQN prefix, the innnermost enclosing object 
>> expression for meta.getState(), etc. [...]
>> I need a name for this thing. [...]
>
> Does this correspond to E-on-Java's "ScopeLayout"?

It does, almost exactly.

Reading the documentation, differences: my EvalContexts are implicit in 
the cl:eval operation, and my Scopes are not built out of ScopeLayouts 
(they are specialized but simple maps).

Do you think this name might be confusing? In E-on-Java, it refers to 
an object which is publicly available as part of a Scope, whereas 
E-on-CL's scope layouts are entirely private (or rather, not exposed as 
they are useless outside of the compiler and subject to change).

Can E-on-Java's Scope#getScopeLayout be considered an implementation 
detail?

-- 
Kevin Reid                            <http://homepage.mac.com/kpreid/>