[Date Prev] [Date Next] [Thread Prev] [Thread Next] Date Index Thread Index Search archive:
Date:Mon Mar 5 13:27:33 2003 
Subject:Forwarded (Matthias Scheutz) Re: sockets 
From:A . Sloman 
Volume-ID:1030305.02 

Non-member submission from [Matthias Scheutz <mscheutz@cse.nd.edu>]
From: Matthias Scheutz <mscheutz@cse.nd.edu>
To: Aaron Sloman <A.Sloman@cs.bham.ac.uk>
cc: pop-forum@cs.bham.ac.uk
Subject: Re: sockets

Aaron,

> If prmishap exits normally then mishap aborts the current procedure,
> and interrupts. But that is prevented if prmishap uses chainto, or
> exitto, etc.

That one worked (I had to rewrite my code a bit so as to exit to a common
ancestor of the procedure I was calling, and I had to add mechanisms for
read errors as well, which I had not gotten in the past--this is why
setting the bit for ignoring write errors as I had in mind originally was
not going to work anyway).  Thank you very much for the hint

Best,
Matthias


Matthias Scheutz
---------------------------------------------------------------
Assistant Professor                http://www.nd.edu/~mscheutz/
Dept. of Computer Science and Engineering, 351 Fitzpatrick Hall
University of Notre Dame                   Notre Dame, IN 46556
USA                                    Phone: +1 (574) 631-0353