Re: [Tcllib-devel] A proposed new package ... Asking for comments.

[Hemang L. <hl...@ci...>]

Andreas Kupries wrote:
> My work here could serve as that, with tighter integration and knowledge between
> the various parts.
> Create a comm channel and link it directly to an execution environment. Possibly
> auto-created. Any
> internally/auto created interp are deleted with the channel. Some restricted
> visibility outside to allow for command definition and aliases ...
>   
Yes: that sounds right.
>> What about callback hooks for comm channel? Are they executed in child
>> interpreter or the main one. I guess since the comm object is linked to
>> the child interpreter, everything will be evaluated in there.
>>     
>
> No. The only hook which goes to the execution environment is the 'eval' hook.
> I do not want the execution environment to do anything else than executing the
> incoming scripts. Authentication, lost connection, and all the other
> _management_
> tasks are not things which I want the slave interpreter to see, or even
> influence
> in any way, shape, or form.
>   
I am not sure that these are restricted to management tasks. For
example: I use 'eval' hook for debugging and lost connection hook to
perform clean up. If these are not executed in exe_interp context then I
would not have access to global variables, etc for debugging, right? The
internal management tasks related to comm/interp functionality can be
outside the execution environment but the user-registered hooks should
be executed in the exe_interp context.

Hemang.