Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!usc!cs.utexas.edu!uunet!math.fu-berlin.de!opal!unido!pbinfo!modula-3
From: modula-3@uni-paderborn.de (Thomas Roemke)
Newsgroups: comp.lang.modula3
Subject: Re: help wanted with Thread.Alert
Message-ID: <1991Apr5.073344.13809@uni-paderborn.de>
Date: 5 Apr 91 07:33:44 GMT
References: <9104041502.AA04492@thor.uni-paderborn.de> <1991Apr4.165038.18433@newross.Princeton.EDU>
Organization: Uni-GH Paderborn
Lines: 24

nr@hart.Princeton.EDU (Norman Ramsey) writes:

>Well, no, that's not the way it's supposed to work.  From the Rd
>interface:

>(*
>Many operations on a reader can wait indefinitely.  For example,
>GetChar can wait if the user is not typing. In general these waits are
>alertable, so each procedure that might wait includes Thread.Alerted
>in its RAISES clause. *)

>PROCEDURE GetLine(rd: T): TEXT RAISES {EndOfFile, Failure, Alerted, Error};
>                                                           ^^^^^^^

Oops. Sorry Norman. My answer was a result of misunderstanding your question.
I answered to 'Why isn't t (automatically) raising Thread.Alerted ?' and your 
question actually was 'Why isn't Rd.GetLine raising it ?'.

Thomas


(*	Thomas Roemke, University of Paderborn, Germany 
	modula-3@uni-paderborn.de
	..!uunet!mcsun!unido!pbinfo!modula-3	*)