comp.lang.ada
 help / color / mirror / Atom feed
From: robert_dewar@my-dejanews.com
Subject: Re: Connecting To Interrupts Using Protected Procedures
Date: 1999/02/18
Date: 1999-02-18T00:00:00+00:00	[thread overview]
Message-ID: <7ag0p8$ae3$1@nnrp1.dejanews.com> (raw)
In-Reply-To: 36CB42FA.FDD195CF@pwfl.com

In article <36CB42FA.FDD195CF@pwfl.com>,
  diespammer@pwfl.com wrote:

> Now Ada95 allows this as per ARM J.7.1 etc. but given
> that it is considered obsolete, I'd like to do it by the
> preferred method.

Please, obsolescent, not obsolete. The rules in Annex J
are just as normative as anything else in the RM. They
simply represent the design team's opinion of features
they would have preferred not to support, if they had
had a choice.

I think the likelyhood of ANY of the annex J features ever
being removed fr om the language is zero. Why on earth
cause
significant back compatibility problems for no good reason?

In this particular case, I actually prefer the Ada 83 style
of interrupts. I think it is a much cleaner interface from
a conceptual point of view, and it allows the program
counter to be used to encode the state of the interrupt
handler process.

As far as hardware goes, machine interrupt structure exists
that reflects both models. All ia32 (x86) machines for
example support a hardware model of interrupts essentially
identical to the J.7.1 method.

-----------== Posted via Deja News, The Discussion Network ==----------
http://www.dejanews.com/       Search, Read, Discuss, or Start Your Own    




  parent reply	other threads:[~1999-02-18  0:00 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-02-17  0:00 Connecting To Interrupts Using Protected Procedures Marin David Condic
1999-02-17  0:00 ` Pat Rogers
1999-02-18  0:00   ` Pat Rogers
1999-02-18  0:00     ` Marin David Condic
1999-02-18  0:00 ` robert_dewar [this message]
1999-02-18  0:00   ` Marin David Condic
1999-02-18  0:00     ` robert_dewar
1999-02-18  0:00 ` Matthew Heaney
replies disabled

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox