Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uunet!amgraf!heitis1!news
From: news@heitis1.uucp (News Administrator)
Newsgroups: comp.lang.c
Subject: Re: Turbo C Interrupt Question
Message-ID: <1990Oct16.175004.17523@heitis1.uucp>
Date: 16 Oct 90 17:50:04 GMT
References: <32905@nigel.ee.udel.edu>
Organization: Harmon Electronics, Inc
Lines: 14

In article <32905@nigel.ee.udel.edu> shearer@cis.udel.edu (Rob Shearer) writes:
>of the REAL Clock no matter what...).  Can you Gurus inform me how to
>detect if the interrupt was hardware or software driven??  It is all

I had to work around this same problem once upon a time.  My solution was to
actually use 2 routines.  I called a non-interrupt specific routine from the
actual interrupt routine.  This way, all interrupt specific tricks could be
handled for me.  And if I decided to call the routine manually, I simply
called the non-interrupt machine from elsewhere in my code.  The only problem
with this method is if you are in a very timing critical portion of the code,
in which case I would suggest having parallel routines for the same function,
its not elegant, but it will work.

	brian