On Friday 15 August 2003 17:44, you wrote: > > This works for procs, but what about the rest of the interp init code? >
The blueprint script can be modified to store plain proc definitions (Part1) apart from any other non-proc code (Part2) Then load the Part2 always and use unknown to fish out proc definitions from Part1. The defs can be retrieved from the master interp easily during runtime on the fly. Would require some internal changes to the Tcl init code and one or two new ns_ commands but it may work. On the first glance, I like the idea. One may also make use of nsv to avoid changing internals. Zoran -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]> with the body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: field of your email blank.
