From: Alexandre F. <ale...@gm...> - 2009-10-09 07:35:25
|
On 10/9/09, Daniel A. Steffen <da...@us...> wrote: > On Thu, Oct 8, 2009 at 14:55, Joe English <jen...@fl...> wrote: > > > >> This is a Call For Votes on TIP #348. > >> > >> TIP #348: Substituted 'errorStack' / 'traceback' > >> > >> Contrary to the information in the headers of the TIP (Tcl 8.7) it is my > >> understanding that Alexandre is asking for inclusion of this feature into > >> > >> Tcl 8.6 > > > > TIP#348: SEND IT BACK. > > > > The basic idea behind this TIP is good, but there is > > an IMO fatal flaw as currently specified: it introduces > > two new magic globals, $::tcl::errorStack and $::tcl::useErrorStack. > > > > Tcl already has too many of these (errorInfo, errorCode, > > tcl_precision, env, ...); this is recognized by now as > > having been a bad idea in all cases. > > > > I'd also suggest targeting this for 8.7. 8.6 is supposed to > > be in feature-freeze mode, so that it can be released. > > Every last-minute addition delays the release. > > > > If "SEND IT BACK" is (still) not a valid vote, then I'm > > sadly forced to say: > > > > TIP#348: NO. > > > +1 on all counts, i.e. NO for 8.6, sounds good for 8.7 if amended to > not introduce yet more magic variable names, e.g. use [info > errorstack] or something instead. Of course I have no objection regarding the API. It is trivial to expose it through the [info] or [interp] ensembles rather than variables. I'm just surprised to see this as a strong showstopper, because I seem to recall some of you saying that the ::tcl namespace was okay for the job. Now to proceed is: info errorstack --> gives the list info errorstack <boolean> --> enables/disables the feature palatable ? Minor variations: - "interp" ensemble instead of "info" - boolean replaced or extended by "enable/disable" -Alex |