On 8/6/07, Zoran Vasiljevic <[EMAIL PROTECTED]> wrote: > > As of today, what we have is: > > a. > introspective script based on the "old" way as 4.0 AS > did it (init the interp by loading all Tcl files then > run a script to pull-out namespaces, variables etc
"variables etc." -- do we support variables? We have a pretty explicit (and simple) end-user programming model: the Tcl code that runs for each connection begins in a known environment, which includes all the procs/commands you need, plus a clean slate as far as global variables go. Connections are independent. # # ns_cleanupvars -- # # Destroy global variables. Namespaced variables # are left and could introduce unwanted state. # IIRC namespaced variables aren't touched because it would be too expensive. Do they get cloned at startup though? This test: test init-1.4 {namespace variables do not get cloned} -body { ns_job wait $qid [ns_job queue $qid { info exists testnamespace::testvariable2 }] } -result 0 ..fails when lazyloader=false, but passes when lazyloader=true. What's going on here? ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ naviserver-devel mailing list naviserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/naviserver-devel