Xref: utzoo comp.os.msdos.programmer:5201 alt.msdos.programmer:2706
Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!usc!samsung!caen!uflorida!SORROW@MAPLE.CIRCA.UFL.EDU
From: sorrow@oak.circa.ufl.edu
Newsgroups: comp.os.msdos.programmer,alt.msdos.programmer
Subject: Re: Notes about Borland C++ interrupt keyword
Message-ID: <00948F17.9C3DE960@MAPLE.CIRCA.UFL.EDU>
Date: 21 May 91 21:13:32 GMT
References: <1991May20.171545.23591@amc.com> <1991May20.230908.7178@maytag.waterloo.edu> <00948EEF.C05FAA40@MAPLE.CIRCA.UFL.EDU>,<1991May21.195106.1530@watcgl.waterloo.edu>
Sender: news@uflorida.cis.ufl.EDU
Reply-To: sorrow@oak.circa.ufl.edu
Organization: University of Florida CIRCA VAX Cluster
Lines: 16

In article <1991May21.195106.1530@watcgl.waterloo.edu>, anicolao@watcgl.waterloo.edu (Alex Nicolaou) writes:
|>In article <00948EEF.C05FAA40@MAPLE.CIRCA.UFL.EDU> sorrow@oak.circa.ufl.edu writes:
|>>Actually, I found out that I must be doing something terribly wrong.  When
|>>I installed my own mouse interrupt handler, if the function was declared
|>>as "void far interrupt" it would die.  "void far" worked just fine.  
|>
|> ** Hmm. What do you mean you "installed my own mouse interrupt handler"? If
|>you mean via the services provided by the mouse driver (12h or 24h, I think)
|>which make the mouse driver call your function, then NO, you CANNOT use the
|>interrupt keyword; for a very simple reason: you aren't the interrupt handler,

Thanks for the info.  Right you are.  I did use the functions, and didn't think
to even think about the fact that INT0x33 was still in place and thus I wasn't
the interrupt handler.  Whoops. (:->

Brian