My hunch on this problem, avoiding lazy code leaking exceptions through handlers, is that Haskell needs to build sufficiently general covers that the points where the handlers are located can be computed in advance: So the implementation of all objects that may contain a handler should be strengthened in order to ensure this. Or the programmer must accept the fact that exceptions may be caught by different handlers depending on the circumstances (i.e. depending on the laziness that the compiler determines to use). Hans Aberg * Email: Hans Aberg <mailto:[EMAIL PROTECTED]> * Home Page: <http://www.matematik.su.se/~haberg/> * AMS member listing: <http://www.ams.org/cml/>
- Re: FW: Exceptions are too return values! Amr A Sabry
- Re: Exceptions are too return values! Fergus Henderson
- Re: FW: Exceptions are too return values! Fergus Henderson
- Re: Exceptions are too return values! Hans Aberg
- Re: FW: Exceptions are too return values! Alastair Reid
- Re: FW: Exceptions are too return values! Fergus Henderson
- Re: FW: Exceptions are too return values! Alastair Reid
- Re: FW: Exceptions are too return values! Carl R. Witty
- Re: Exceptions are too return values! Scott Turner
- Re: FW: Exceptions are too return values! Hans Aberg
- Re: Exceptions are too return values! Hans Aberg
- Re: Exceptions are too return values! Hans Aberg
- Re: Exceptions are too return values! Fergus Henderson
- Re: Exceptions are too return values! Fergus Henderson
- Re: FW: Exceptions are too return values! Fergus Henderson
- Re: Exceptions are too return values! Dave Tweed
- Re: Exceptions are too return values! Alastair Reid
- Re: Exceptions are too return values! Fergus Henderson
- Re: Exceptions are too return values! Fergus Henderson
- Re: FW: Exceptions are too return values! Simon L Peyton Jones
- RE: FW: Exceptions are too return values! Erik Zuurbier