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,26f80afcbbd1b278
X-Google-Attributes: gid103376,public
From: Robert Dewar <robert_dewar@my-deja.com>
Subject: Re: Interrupt Handler Problems
Date: 1999/07/08
Message-ID: <7m1782$9i$1@nnrp1.deja.com>#1/1
X-Deja-AN: 498417424
References: <1999Jul7.160434.10447@nosc.mil>
X-Http-User-Agent: Mozilla/4.04 [en] (OS/2; I)
X-Http-Proxy: 1.0 x33.deja.com:80 (Squid/1.1.22) for client 205.232.38.14
Organization: Deja.com - Share what you know. Learn what you don't.
X-Article-Creation-Date: Thu Jul 08 03:51:34 1999 GMT
Newsgroups: comp.lang.ada
Date: 1999-07-08T00:00:00+00:00
List-Id: <comp.lang.ada>

In article <1999Jul7.160434.10447@nosc.mil>,
  claveman@cod.nosc.mil (Charles H. Sampson) wrote:
>      We're having a terrible time getting our code running in
the new
> environment.  The killer problem of the moment is interrupt
handlers.
> (We have a lot of them.)  Our handlers have been modified into
protected
> procedures, as required by Green Hills


Why not use a technology that provides compatible handling
of interrupts, avoiding the need for these modifications?


Sent via Deja.com http://www.deja.com/
Share what you know. Learn what you don't.