For instance, if you've got a procedure which is two-third error
handling code, for example parsing a complicated user input field, you
don't want to have to write a page of code just to format the error
message correctly. But you also don't want to dig through an overly
cryptic error message when something goes wrong.
From what I've seen, the really ugly error reporting is mostly confined
to control structures, but I've got a few [foreach] style bits and
pieces (things like [dict for] and [dict with]), and even worse still
are callbacks (which I also use rather a lot), and writing their error
reporting (more so than error handling per-se) is a right royal pain in
the a***, especially when you don't really have a 100% clear idea of
how errors are really supposed to be reported to begin with.
I'm still using TCL 8.4.12, personally, so documentation for the
pre-funky-[return] would be handy. ;)
Fredderic