Dear David, My suspicion that one should not rely on the universal existence of ::errorInfo and ::errorCode is backed by the newer definitions of init.tcl in tcl 8.5 and 8.6. In these releases, the code checks for the existence of these variables before reading its content. I've commit a patch, that is quite similar to this.
https://bitbucket.org/naviserver/naviserver/commits/d118a87689afe116ee3e618809a4b34f66a75379 all the best -gustaf neumann Am 03.08.13 12:07, schrieb Gustaf Neumann: > Am 01.08.13 15:00, schrieb David Osborne: >> Hi, >> >> We intermittently encounter the above error when we call a ns_eval >> from our naviserver codebase (with Tcl 8.5.11 ). > The code is in "proc getentry" in nstrace. > > Actually, one should only access the value ::errorInfo and friends > immediately after an error occured, that is typically within a catch > clause. "proc getentry" seems to try to preserve the previous > ::errorInfo and ::errorCode settings (not sure why). I think the access > to ::errorInfo should be guarded by an "info exists". > > Will try this later and do some testing. > Greetings from dubai. > -g > ------------------------------------------------------------------------------ Get your SQL database under version control now! Version control is standard for application code, but databases havent caught up. So what steps can you take to put your SQL databases under version control? Why should you start doing it? Read more to find out. http://pubads.g.doubleclick.net/gampad/clk?id=49501711&iu=/4140/ostg.clktrk _______________________________________________ naviserver-devel mailing list naviserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/naviserver-devel
