Path: utzoo!attcan!uunet!lll-winken!lll-tis!ames!ll-xn!mit-eddie!killer!pollux!dalsqnt!rpp386!jfh
From: jfh@rpp386.UUCP (John F. Haugh II)
Newsgroups: comp.lang.c
Subject: Re: Turbo C
Message-ID: <4244@rpp386.UUCP>
Date: 22 Jul 88 00:37:57 GMT
References: <16577@brl-adm.ARPA>
Reply-To: jfh@rpp386.UUCP (The Beach Bum)
Organization: Big "D" Home for Wayward Hackers
Lines: 16

In article <16577@brl-adm.ARPA> C08922DB%WUVMD.BITNET@cunyvm.cuny.edu writes:
>I am interested in understanding the structure of the function type
>"interrupt" in Turbo C. Basically, what is special about this function
>definition, and what approaches can be used in other compilers to simulate
>this feature? Optimum-C is what I'm using.

it declares the function as being called at interrupt time.  this means
that the function can have no stray side effects, such as not restoring
a modified register, and that the function must be ended with a return
from exception rather than a short or long return from subroutine call.

- john.
-- 
John F. Haugh II                 +--------- Cute Chocolate Quote ---------
HASA, "S" Division               | "USENET should not be confused with
UUCP:   killer!rpp386!jfh        |  something that matters, like CHOCOLATE"
DOMAIN: jfh@rpp386.uucp          |             -- with my apologizes