|
From: Neil M. <ne...@Cs...> - 2008-02-09 14:10:17
|
On 9 Feb 2008, at 10:43, Alexandre Ferrieux wrote: > ... > > - adding another global is seamless. The slate being empty, and with > years of experience with ::errorInfo, we are in a better position to > get it right at once. > Moreover, the new global may work hand-in-hand with the old one, > giving only complementary info, and making it easy to scan both in > sync: to do that, ::errorStack could contain string positions in > ::errorInfo in addition to the requested [info level 0]'s. Adding a -errorstack option to the option dictionary seems like a much cleaner way of doing things. ::errorStack seems like a fairly common name to be actually used in existing code, so you'd at least want to make it ::tcl::errorStack. One argument for using a variable though is persistence: e.g., bgerror has no access to any error options dictionary, so it has to rely on global variables (or some command interface). -- Neil This message has been checked for viruses but the contents of an attachment may still contain software viruses, which could damage your computer system: you are advised to perform your own checks. Email communications with the University of Nottingham may be monitored as permitted by UK legislation. |