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.9 required=5.0 tests=BAYES_00 autolearn=ham
	autolearn_force=no version=3.4.4
X-Google-Thread: a07f3367d7,4a79d3a6d273074a
X-Google-Attributes: gida07f3367d7,public,usenet
X-Google-NewGroupId: yes
X-Google-Language: ENGLISH,ASCII-7-bit
Received: by 10.216.233.196 with SMTP id p46mr296741weq.0.1348233638449;
        Fri, 21 Sep 2012 06:20:38 -0700 (PDT)
Path: 
 q11ni9092558wiw.1!nntp.google.com!feeder2.cambriumusenet.nl!feeder1.cambriumusenet.nl!feed.tweaknews.nl!216.40.29.245.MISMATCH!novia!border4.nntp.dca.giganews.com!border2.nntp.dca.giganews.com!nntp.giganews.com!newsfeed.news.ucla.edu!nntp.club.cc.cmu.edu!feeder.erje.net!news2.arglkargh.de!news.mixmin.net!eternal-september.org!feeder.eternal-september.org!mx04.eternal-september.org!.POSTED!not-for-mail
From: Simon Wright <simon@pushface.org>
Newsgroups: comp.lang.ada
Subject: Re: Ganssle plugs Ada
Date: Fri, 14 Sep 2012 22:48:10 +0100
Organization: A noiseless patient Spider
Message-ID: <m24nn0mg2t.fsf@pushface.org>
References: <12caf09a-13b4-4d19-be4a-9d2d9b3f1f10@googlegroups.com>
	<ad67561e-9c9c-4608-9df9-d05fdf74ba60@googlegroups.com>
Mime-Version: 1.0
Injection-Info: mx04.eternal-september.org;
 posting-host="a9272c9c584810f74e3f95ce46cbeceb";
	logging-data="32422"; mail-complaints-to="abuse@eternal-september.org";
	posting-account="U2FsdGVkX1/SVYRCmP89q89awLUKds6XIJhNbimAgMg="
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.2 (darwin)
Cancel-Lock: sha1:SIl3Kh8/ZDb0jK0wdILCQS4LK0E=
	sha1:43Q5Drs5Ov66hEtn5ys3TTM3GnA=
Content-Type: text/plain
Date: 2012-09-14T22:48:10+01:00
List-Id: <comp.lang.ada>

Shark8 <onewingedshark@gmail.com> writes:

>> 5. Incorrect hardware handling. For example using edge triggered
>> instead of level triggered interrupts resulting in peripherals going
>> to sleep and product failure.
>
> -- I've not done a lot of low-level work... but I'm under the
> impression that Ada's interrupt handlers work perfectly fine.

As noted, the edge/level interrupt triggering is a hardware issue
(normally; could be configuration done by software), so no software
features are going to prevent the wrong choice.