>> Zoran, just to make sure I got that right: xotcl does not work with the >> nstrace/lazyloader at all (true or false). That's the reason I'm using >> the modified init.tcl file from 4.99.1. > > I wonder if this is xotcl specific, or if xotcl just tickles the right > (wrong) bit of code. Xotcl seems to use a lot of deeply namespaced > commands, who's names are stored in variables...
Stephen, there is no need for deeply namespaced commands (that's just part of some code I wrote a couple of years back). > It would be really helpful if a minimal example of the error could be > isolated in standard Tcl and dropped into a file: > tests/testserver/modules/state.tcl > > Hard to write a test for it, but at least it will throw an error at > startup when the tests are run and someone will see it. If it really > is an xotcl-only error, I guess it can be package required in a catch > or something? The problem with lazyloader=false should be easier to overcome (i.e. serializing xotcl code + "ns_ictl trace allocate [list source module-file]"). The lazyloader=true case should be harder and IIRC Zoran already mentioned that it would require some changes on the xotcl-side to work. Still, getting lazyloader=false to work with xotcl is a first step. Best, Neophytos ------------------------------------------------------------------------- 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
