Thanks Gustaf.
Makes sense. I can see how that change keeps the explicit calls to namespace
eval ::tcl* out of the statescript.
But in this case it doesn't resolve the problem for us. The
clock::Initalization scripts still ends up being called after an ns_eval,
and ::tcl::clock::CachedSystemTimeZ
Hi David,
strange, the indicated modification did make the change for me
(first broken as described in your email, and now fine).
Can it be, that your installation is "manually" sourcing
some tcl init files (such as clock.tcl)?
Please try the following:
- use a default configuration of naviserv
Thanks again Gustaf,
Have done what you suggested (a little downlevel):
% info patchlevel
8.5.8
% ns_info patchlevel
4.99.5
And, yes, running on the main thread there is no problem
% clock_test
[05/Jul/2013:14:45:38][12827.7f1ea56ba700][-command-] Notice: 2013-07-05
14:45:38
true
% ns_eval expr
Dear David,
Now we exclude proc ::clock from the blueprint and this should solve
this issue.
By doing so, we are loosing some flexibility (namely to overload ::clock
with a tailored version), but i think we can live with this.
Please try again
-gustaf neumann
PS: Not sure, why ::clock is defi
