🚀 go-pugleaf

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,
you are being called by it, and you are supposed to be a routine. If you use
an interrupt function, the BC++ compiler will put an iret instruction in 
for you, and that will terminate the interrupt handling prematurely - your
Microsoft compatible driver will not have finished its work and your computer
will dissappear into limbo. Incidentally, if you are doing this and then 
accessing data, you'd better be sure that you're restoring DS yourself, since
the MS mouse driver won't do it for you - if you compile in Medium or Large
models this is an absolute must, in smaller models you ought to do it for 
painless changes later.

>I just
>don't USE the interrupt keyword.  The documentation is too skimpy on it
>for me to be able to use it decently.

 ** Interrupts are a pain, but that is not a function of the documentation.
Yes, I am another borland fan :-)

alex