I think you're making the component argument I alluded to toward the end of 
my message. I was a bit worried that my example might we a bit too 
simplistic in this regard. However, my main point was that Herink's module 
definition appears to require the use of a particular implementation of 
Transcript provided by a particular module.  I don't see where in his 
proposal the mechanism exists for rebinding TranscriptModule.

Allen

At 02:55 PM 8/22/2001 -0700, Dan Ingalls wrote:

>I will admit to little experience with these issues.  However, I did give 
>this aspect some thought in the Environments design.  This approach 
>compiles the statement
>
>         Transcript show: "my message";cr;
>as
>         TranscriptModule Transcript show: "my message";cr;
>
>where #Transcript is a message sent to whatever module is bound to the 
>(real) global, TranscriptModule.  The idea is that several Transcript 
>packages can be resident at the same time.
>
>Then, just as you can now rebind a global, as in
>
>         Changes := ChangeSet new
>
>you could similarly rebind a module, as in
>
>         TranscriptModule := ScreenTranscriptModule
>or
>         TranscriptModule := RemoteTranscriptModule
>
>This can happen in the twinkling of an eye, and it can be undone by 
>various error handlers during experimentation, because the original 
>foreign reference just sends a message.
>
>So I think there is an answer to this need in the simple approach.  It may 
>not do everything Team/V does, but it seems to handle this particular need.
>
>         - Dan
>
>--