Re: [TCLCORE] TIP #329 [try] updated

[Donal K. F. <don...@ma...>]

Twylite wrote:
> Two ways of handling this:
> (1) If errorcode is not a list, then trap handlers must determine that 
> there is no match, and let the error fall through to the next handlers 
> and be processed or propagated as normal.  I _think_ that's what Donal's 
> rewrite is saying, but I'm not certain?
> DKF - can you confirm this?

I can *deny* this. :-) Apart from everything else, it is significantly
more awkward to implement since you'd have to push a special catch
context just when doing the listRangeImm. And anyway...

> (2) Update the implementations of error & return so that a non-list 
> error code raises an appropriate error at that point, rather than 
> allowing arbitrary strings that can blow up the [try] later.

The errorcode is documented to be a list on the [return] manpage and has
been for many years, though according to DGP it is a bug that this is
not currently enforced. Probably because nobody tried to do it.

Donal.