Asynchronous Exceptions

[Steinitz, Dominic J]

---------------------- Forwarded by Dominic Steinitz/HEATHROW/BRITISH AIRWA=
YS/GB on 27/11/2001 09:59 ---------------------------
From:=09Dominic Steinitz on 27/11/2001 08:16
To:=09uk1o
cc:=09haskell
bcc:=09
Subject:=09Re: Asynchronous Exceptions =20




Hannah,

=20

I was thinking of where you really want to write something to a transaction=
 log so that you know an action really did complete. Is there a way of doin=
g this?

=20

Dominic.=20

uk1o@rz.uni-karlsruhe.de
26/11/2001 23:53

To: haskell@haskell.org@INTERNET
cc:=20
bcc: Dominic Steinitz/HEATHROW/BRITISH AIRWAYS/GB
Subject: Re: Asynchronous Exceptions


Hello!

On Fri, Nov 23, 2001 at 09:38:35AM -0000, Simon Marlow wrote:

> [...]

> However, I agree that sometimes you really want to be able to do this,
> so perhaps we need another form of 'block' which doesn't allow *any*
> exceptions to be delivered, for those times when you know that the time
> spent waiting in an interruptible operation is going to be bounded.

But even things like putStr can block for an unbounded amount of
time. E.g. stdout is a pipe and the reader just doesn't read it for
n hours (n unknown), etc.

Kind regards,

Hannah.

_______________________________________________
Haskell mailing list
Haskell@haskell.org
http://www.haskell.org/mailman/listinfo/haskell




---------------------------------------------------------------------------=
----------------------
To receive our special fares directly by email, register at http://www.brit=
ishairways.com/registration