[e-lang] <import> with cycle breaking is not DeepFrozen

[Kevin Reid]

On May 31, 2006, at 13:07, Mark S. Miller wrote:
> Kevin Reid wrote:
>> Also, here's one consequence: if <import> is not DeepFrozen, then
>> safeScope is not, which means that anything which wants to evaluate E
>> code in the usual scope is not.
>
> A good point. Making <import> DeepFrozen impedes incremental  
> development, but not making it DeepFrozen seems to have worse costs.

I believe the appropriate answer for incremental development is to  
create a new mutually-referential <import> loader and scope with  
which the latest version is evaluated.

Making <import> controllably mutable would mean that any tool being  
used for such development has a channel to every un-DeepFrozen object  
in the E system.

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