Path: utzoo!utgpu!watmath!watserv1!watdragon!abrodnik
From: abrodnik@watdragon.waterloo.edu (Andrej Brodnik (Andy))
Newsgroups: comp.realtime
Subject: Re: Language constructs for interrupt facility
Message-ID: <18742@watdragon.waterloo.edu>
Date: 28 Nov 89 02:23:34 GMT
References: <29160@shemp.CS.UCLA.EDU> <961@abvax.UUCP> <836@trlluna.trl.oz>
Reply-To: abrodnik@watdragon.waterloo.edu (Andrej Brodnik (Andy))
Organization: U. of Waterloo, Ontario
Lines: 19

In article <836@trlluna.trl.oz> aurie@rhea.trl.oz.au.trl.oz (Alistair Urie - Radio and Satellite Networks) writes:
>>In article <29160@shemp.CS.UCLA.EDU> cshen@maui.cs.ucla.edu
>>(Chien Chung Shen) writes:
>>>I am interested in language constructs for interrupt facility.
>>>Ada has "address clauses" and entry calls. Are there any other
>>>languages which support interrupt facility and how are they
>>>implemented? Any direction is appreciated.
>>>
>
>I rather liked the way HP does it in there development systems, a $INTERRUPT
>pre-complier command in the source sets the following routines as interupts
>(in effect the routines compile to an RTI rather than RTS return - in 68K )

Modula-2 has IOTRANSFER and the new BSI standard tries to specify it even more
preceisley. It (Modula-2) assumes that interrupt routine is nothing else but
another process. So interrupt handling is just a special case of general
concept of process handling.

Andrej


Brought to you by Super Global Mega Corp .com