Am 08.07.13 21:12, schrieb Jeff Rogers:
> Sheer luck is definitely a possibility,
what i called "luck" was the random order of entries as returned from the
hash tables during serialization.
> but also naviserver is missing
> the ensemble serialization that aolserver has, so things defined (or
> red
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
Am 08.07.13 15:21, schrieb David Osborne:
> That certainly does the trick. Thanks.
>
> What's your opinion. Could this be considered a bug in Tcl?
> Would seem a lot cleaner if ::clock::Initialize just ran
> ::tcl::clock::ClearCaches before initialising the TZData array which
> would allow ::tcl:
That certainly does the trick. Thanks.
What's your opinion. Could this be considered a bug in Tcl?
Would seem a lot cleaner if ::clock::Initialize just ran
::tcl::clock::ClearCaches before initialising the TZData array which would
allow ::tcl::clock::Initalize to run multiple times.
I notice the
