Gustaf Neumann wrote: > also the definition of proc "clock", which redefines itself in terms of > an ensemble. This makes it sensitive to the definition order.
>> I notice the same test case doesn't raise an error in Aolserver. Seems >> after a ns_eval the ::tcl::clock:: vars left not populated so >> ::tcl::clock::Initialize runs cleanly. Couldn't ascertain from my >> limited understanding of the internals why it should be different. > aolserver does essentially the same thing as naviserver. my guess is > that this is sheer luck in the order of definitions. Furthermore, a > single call to lock "at the right time" can heal everything or lead to > the error, since clock is kind of a "self modifying" code... Sheer luck is definitely a possibility, but also naviserver is missing the ensemble serialization that aolserver has, so things defined (or redefined) as ensembles would get lost. I've copied this code over from aolserver. I don't know if it will help the clock problem, although it is possible clock was the motivating issue for that code in the first place. In aolserver the code is wrapped to prevent it from executing on pre-8.5 tcl. Is that still needed, or is 8.4 dead enough to have 8.5 as a default requirement? -J ------------------------------------------------------------------------------ This SF.net email is sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev _______________________________________________ naviserver-devel mailing list naviserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/naviserver-devel
