From: Hemang L. <hl...@ci...> - 2006-08-12 20:22:13
|
Andreas Kupries wrote: > The new proposal basically provides communication channels with an > option to set an interpreter for execution. This is the link command > of the original proposal. The implementations of safeBasic and safe > commands of the original become so trivial in the new scheme that > providing special commands for them is not worthwhile. I.e. > > comm::comm new FOO -interp [interp create -safe] > or comm::comm new FOO -interp [safe::interpCreate] > Looks good. Just rename -ipevents option to -interp_events or -ievents. > The protocol command of the original proposal also reduces to 'create > an empty interpreter and set aliases into it'. For the case of linking > the aliases to a second interpreter 'interp alias' is still the best > way of doing it, reducing this further to 'create an empty interp'. We > can do a command for that, this is however quite general and unrelated > to comm. Anybody with an idea where to place such command ? (Maybe a > package "interp" ?) > Can you provide an example of how you intend to use this. As such, it could be just a sub-command "comm::comm link ..." but I can't say much without understanding how it is going to be used. > + > +This isecure setup can be changed by the user via the two options > Typo: isecure -> insecure. Hemang. |