Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!ncar!gatech!udel!princeton!newross!hart.Princeton.EDU!nr
From: nr@hart.Princeton.EDU (Norman Ramsey)
Newsgroups: comp.lang.modula3
Subject: Re: help wanted with Thread.Alert
Message-ID: <1991Apr4.165038.18433@newross.Princeton.EDU>
Date: 4 Apr 91 16:50:38 GMT
References: <9104041502.AA04492@thor.uni-paderborn.de>
Sender: news@newross.Princeton.EDU (USENET News System)
Reply-To: nr@princeton.edu (Norman Ramsey)
Organization: Princeton University, Dept. of Computer Science
Lines: 19

In article <9104041502.AA04492@thor.uni-paderborn.de> modula-3@uni-paderborn.de (Thomas Roemke) writes:
> Thread.Alert(t) marks t as alerted, nothing else. No
> exception is raised, neither in the calling nor in the
> marked thread. 

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};
                                                           ^^^^^^^
-- 
Norman Ramsey
nr@princeton.edu