> Is it a bad idea, maybe before use on the production system, to let AOLserver > create the file, byte compile the procs, adding "load libtbcload..." and > sourcing this file instead of running through the process every time?
procomp/tbcload is designed for obfuscation, not speed. It will not speed anything up, unless you have procs that take a very long time to compile. We (ActiveState) actually just did some work recently on a Tcl_CloneInterp implementation, which could possibly benefit something like AOLServer. Getting it into the core will be touchy though, because it breaks the existing bytecode structures, which would mean all existing tbcload'able code. > Would that help speed up things? No, the aspect of obfuscation prevents any speed gain. > Would it "hide" all procs from the info vars/procs/body... command to make it > (more) difficult to inspect vars, procs and environment at runtime? Very much so, that is the exact purpose. Users would still be able to see the global variables and procs with 'info', but 'info body' would not return anything. Jeff Hobbs The Tcl Guy Senior Developer http://www.ActiveState.com/
