From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=-1.3 required=5.0 tests=BAYES_00,INVALID_MSGID autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,fe5641bca012dada X-Google-Attributes: gid103376,public From: Markus Kuhn Subject: Re: help about handling interrupts Date: 1998/04/07 Message-ID: <352A68E9.38B5BBAA@cl.cam.ac.uk>#1/1 X-Deja-AN: 341770303 Content-Transfer-Encoding: 7bit References: <3528B9E0.6F0F@bipa162.bi.ehu.es> <3529047A.44EE08B8@cl.cam.ac.uk> Content-Type: text/plain; charset=us-ascii Organization: Cambridge University, Computer Laboratory Mime-Version: 1.0 Newsgroups: comp.lang.ada Date: 1998-04-07T00:00:00+00:00 List-Id: Samuel Tardieu wrote: > I'm afraid you are talking about different things; it looks like Igor > means "signal" when he writes "interrupt", while you mean "hardware > interrupt". It seems to be a common problem that programming beginners mix up terminology and get therefore confusing answers here, such as "signal" versus "hardware interrupt" under Unix or "memory access" versus "i/o port access". "Interrupt" can under Unix indeed also refer to one special type of signal, the SIGINT that a process receives when you press Ctrl-C on its controlling shell. Handling Unix signals is described in POSIX.1 if you want to use the C API or in POSIX.5 if you want to use a native Ada API. See the FLORIST package on . A note about the pain with standards: I'd love to comment on the POSIX.5 way of handling signals, but the copy of POSIX.5 which I ordered from IEEE many weeks ago still has not arrived. Standards that are only available on paper from low-quality-of-service publishers like IEEE and ISO are a VERY BAD THING, not at all helpful for the spread of the technology. If you are the editor of any standard, *please* make sure that the documents are available freely online as well as from a big book publisher such as Springer or Addison Wesley, and not only from buerocrats like ISO/IEEE. The AdaRM has proofed that this is easily possible (I got my AdaRM from Springer delivered within 3 days, at the price of a normal university textbook), so why not also for POSIX? Markus -- Markus G. Kuhn, Security Group, Computer Lab, Cambridge University, UK email: mkuhn at acm.org, home page: