Xref: utzoo alt.msdos.programmer:2707 comp.os.msdos.programmer:5209
Path: utzoo!utgpu!cs.utexas.edu!sdd.hp.com!caen!hellgate.utah.edu!cai.utah.edu!b-davis
From: b-davis%cai.utah.edu@cs.utah.edu (Brad Davis)
Newsgroups: alt.msdos.programmer,comp.os.msdos.programmer
Subject: Re: Notes about Borland C++ interrupt keyword
Message-ID: <1991May21.191802.23534@hellgate.utah.edu>
Date: 22 May 91 01:18:02 GMT
References: <1991May20.230908.7178@maytag.waterloo.edu> <00948EEF.C05FAA40@MAPLE.CIRCA.UFL.EDU> <1991May21.195106.1530@watcgl.waterloo.edu>
Organization: University of Utah CAI Group
Lines: 17

In article <1991May21.195106.1530@watcgl.waterloo.edu> anicolao@watcgl.waterloo.edu (Alex Nicolaou) writes:
> ** Interrupts are a pain, but that is not a function of the documentation.

As Alex said interrupts are a pain (any form of multi-tasking is) but
you can always have the compiler generate assembler to read and check.
If you can't read 8086 code and/or don't know what the hardware does you
shouldn't be trying to write interrupt handlers.

>Yes, I am another borland fan :-)

Me too (and so is my fully interrupt driven, buffered, handshaking,
with up calls to other routines serial port driver, all written in
Wizard/Turbo/Borland C).
-- 
Brad Davis	..!uunet.uu.net!cs.utah.edu!cai.utah.edu!b-davis
		b-davis@cs.utah.edu, b-davis@cai.utah.edu
One drunk driver can ruin your whole day.