On 28.01.19 18:10, David Osborne wrote:
Thanks Gustaf,
That got me past the immediate problem - but I'm now seeing some
further issues which I can't fully explain.
1. Tcl8.5 only - After clock scan : invalid command name
"::tcl::clock::scan"
2. Tcl8.5 & Tcl8.6 After ::try .. on error : can't
On Tue, 29 Jan 2019 12:12:12 +0100
Gustaf Neumann wrote:
> So, i think, it is the best strategy for NaviServer to put the
> fingers away on stuff
> coming from Tcl.
... indeed, and not *only* Tcl.
I doubt we can be absolutely correct at that place, since
the task itself is far to complex to b
Thanks for looking at that Gustaf.
I can definitely relate to Zoran's comment:
> "In the moment all is pretty "spooky" and it is difficult to grasp..."
Your change doesn't seem to help the problems I'm looking at here
unfortunately.
The output you have pasted is the same as mine up to that point
On 29.01.19 13:13, David Osborne wrote:
The output you have pasted is the same as mine up to that point. I
wouldn't have seen an error by then either.
It's the *subsequent* calls to "clock scan" and "::try {} on error .."
which then fail.
I see, ... i can reproduce this, hopefully i can look i
On 29.01.19 13:49, Gustaf Neumann wrote:
I see, ... i can reproduce this, hopefully i can look into this today
evening or tomorrow.
just a quick thought, although it does not solve the not-for-me
reproducible issue of [2]
the change [1] seem to fix all known problems problems mentioned here.
On Tue, Jan 29, 2019 at 12:02:23AM +0100, Gustaf Neumann wrote:
> In case, the name is for unknown reason not initialized, the change [1]
> should help.
> https://bitbucket.org/naviserver/naviserver/commits/a1a07e7f1397e71809c74ca3a4bf93649affd8b2
That didn't make any difference.
> The function
