Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!uunet!cis.ohio-state.edu!sei.cmu.edu!fs7.ece.cmu.edu!o.gp.cs.cmu.edu!pt.cs.cmu.edu!ralf
From: Ralf.Brown@B.GP.CS.CMU.EDU
Newsgroups: comp.os.msdos.programmer
Subject: Re: Handling interrupts in C
Message-ID: <28451d88@ralf>
Date: 30 May 91 15:43:04 GMT
Organization: Carnegie Mellon University School of Computer Science
Lines: 15
In-Reply-To: <1991May29.044612.8057@bnr.ca>
Originator: ralf@B.GP.CS.CMU.EDU

In article <1991May29.044612.8057@bnr.ca>, seanna@bnr.ca (Seanna Watson) wrote:
}A quick note while on the topic: I discovered tody (after some effort) that
}in TC++, interrupt handlers take arguments (...) not (void), as in TC.
}It's NOT documented.

Sure it is.  See page 388 of the TC2 User's Guide.  Interrupt functions have
never had void arguments, although you might have been fooled by the lack
of argument declarations in the prototype for getvect() and setvect().	But
foo() is *not* the same as foo(void).

-- 
{backbone}!cs.cmu.edu!ralf  ARPA: RALF@CS.CMU.EDU   FIDO: Ralf Brown 1:129/53
BITnet: RALF%CS.CMU.EDU@CARNEGIE   AT&Tnet: (412)268-3053 (school)   FAX: ask
DISCLAIMER?  Did  | It isn't what we don't know that gives us trouble, it's
I claim something?| what we know that ain't so.  --Will Rogers