From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.5-pre1 (2020-06-20) on
	ip-172-31-74-118.ec2.internal
X-Spam-Level: 
X-Spam-Status: No, score=-0.0 required=3.0 tests=BAYES_20 autolearn=ham
	autolearn_force=no version=3.4.5-pre1
Date: 18 Feb 93 15:07:11 GMT
From: cis.ohio-state.edu!pacific.mps.ohio-state.edu!linac!uwm.edu!ux1.cso.uiuc.
edu!news.cso.uiuc.edu!ehsn4.cen.uiuc.edu!dl10696@ucbvax.Berkeley.EDU  (Dat Trie
u Le)
Subject: Interrupts
Message-ID: <C2nGo0.8oB@news.cso.uiuc.edu>
List-Id: <comp.lang.ada>

Hi everyone,

I'm working on an ada application requiring the use of interrupts.
I understand you can use tasks to trap interrupts, but haven't
tested it.

task service is
  entry ISR;
  for ISR use at 16#xxx#;
end service;

My question is: instead of using the overhead of tasks, is it
possible to tie the interrupt directly to a procedure?

procedure ISR is
end ISR;
for ISR use at 16#xxx#;

Any advice or comments is appreciated. Thanks in advance.