[prev in list] [next in list] [prev in thread] [next in thread] 

List:       haskell
Subject:    Re: Asynchronous Exceptions
From:       "Steinitz, Dominic J" <Dominic.J.Steinitz () BritishAirways ! com>
Date:       2001-11-27 10:03:18
Message-ID: "044DB3C0364E6005*/c=GB/admd=ATTMAIL/prmd=BA/o=British Airways PLC/ou=CORPLN1/s=Steinitz/g=Dominic/i=J/" () MHS
[Download RAW message or body]

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




Hannah,

 

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 doing this?

 

Dominic. 

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

To: haskell@haskell.org@INTERNET
cc: 
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.britishairways.com/registration


[prev in list] [next in list] [prev in thread] [next in thread]