🚀 go-pugleaf

In a previous article, smith@ctron.com (Larry Smith) says:

[...]
>Even so, if it were possible to get the effect I have in mind
>_within_ the language, I'd agree with you, but you can't.  Even if you call
>a handler, it still going to return_to_the_function_that_detected_the_problem.
>It cannot abort processing and roll the stack back to a known state, as an
>exception can. 

In some languages an exception function need *not* return to the function 
that detected the problem, and *can* roll the stack back to a known state.  
(For example, Scheme can do this with call-with-current-continuation.)

>               If your file reader called a handler at EOF, that handler can
>set booleans, close the file, do whatever, but it must still return to a
>routine that _must_ return some sort of result.  

--
T.K. Bond