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,e9498cf5655316a X-Google-Attributes: gid103376,public From: robert_dewar@my-dejanews.com Subject: Re: Ada83 and Ada95 interrupt handling Date: 1999/02/24 Message-ID: <7b0l9k$aqm$1@nnrp1.dejanews.com>#1/1 X-Deja-AN: 447832347 References: <36D303B8.B1AB9A49@swol.de> X-Http-Proxy: 1.0 x2.dejanews.com:80 (Squid/1.1.22) for client 205.232.38.14 Organization: Deja News - The Leader in Internet Discussion X-Article-Creation-Date: Wed Feb 24 10:46:12 1999 GMT Newsgroups: comp.lang.ada X-Http-User-Agent: Mozilla/4.04 [en] (OS/2; I) Date: 1999-02-24T00:00:00+00:00 List-Id: In article , Matthew Heaney wrote: > You're code should continue to work in Ada95. Interrupt > entries of a task are obsolescent, but not entirely gone. > > The "preferred" method now is to use an interrupt handler > associated with a protected object. I haven't done this > yet, so I cannot give you more advice than to say, read > the interrupt handler stuff in the RM. This is probably unhelpful advice in this case. Interrupt stuff (by either method) is highly implementation dependent. What interrupts your implementation supports, what they are called, and whether they are available by one or other or both of the methods is entirely up to the implementation. So the better advice is to consult your vendor and/or the vendor documentation on this issue. -----------== Posted via Deja News, The Discussion Network ==---------- http://www.dejanews.com/ Search, Read, Discuss, or Start Your Own