On 2/6/06, Zoran Vasiljevic <[EMAIL PROTECTED]> wrote:
> Hi!
>
> I have included the ttrace module which allows for
> alternative Tcl interp initializations.
Nice!
> To enable, edit the sample-config.tcl and set
>
> ns_section ns/server/$servername/ttrace
> ns_param enabletraces true
Can this be changed to:
ns_section ns/server/$servername/tcl
ns_param betternamehere true
It's clearly part of the Tcl configuration. As for the name, 'trace'
just seems too generic, which is why it clashes with existing usage
(ns_register_trace).
Anyway, tracing is just the mechanism, not the purpose. What about
lazyloader, or tclondemand, or ...?
> This way all "things" loaded into an interp during startup
> will just be recorded in ttrace database. At new thread
> creation, a short bootstrap script will be installed
> instead of a full-blown (potentially very large) init
> script. This one overrides the Tcl unknown method and loads
> required "things" definitions on-demand.
Why is this off by default? This is robust, right?
How about some debug log statements, so that we can see that it's
working correctly.
Looks like some cut 'n paste cleanup is needed: The blurb at the top
of ttrace.tcl mentions licence.terms. You'll need to include the
license directly at the top of the file. nsv_*, ns_mutex etc. will
always be available as this is now embedded in NaviServer -- can you
remove the indirect calls ( ${store}set etc. ) ?
