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=0.7 required=5.0 tests=BAYES_00,INVALID_DATE,
	MSGID_SHORT,REPLYTO_WITHOUT_TO_CC autolearn=no autolearn_force=no
	version=3.4.4
Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.1 6/24/83; site qucis.UUCP
Path: utzoo!utcsri!qucis!dalamb
From: dalamb@qucis.UUCP (David Lamb)
Newsgroups: net.lang.ada
Subject: Re: ForTran-Ada + flamette + question
Message-ID: <136@qucis.UUCP>
Date: Wed, 28-May-86 15:30:28 EDT
Article-I.D.: qucis.136
Posted: Wed May 28 15:30:28 1986
Date-Received: Thu, 29-May-86 06:04:23 EDT
References: <8605210805.AA20308@ucbvax.Berkeley.EDU>
Reply-To: dalamb@qucis.UUCP (David Lamb)
Organization: Queen's University, Kingston, Ontario
Summary: 
List-Id: <comp.lang.ada>

Someone recently asked if there was any way to pass procedures as
parameters in Ada, or place them in records;  I think the problem in
question was doing key-to-procedure bindings in an editor.  Ada has
neither of these directly;  you can sometimes simulate them in ugly
ways.  You can simulate procedure parameters via generics: pass the
procedures or functions as generic parameters, and hope your compiler
is smart enough to pass them as procedures at runtime.  You can get
procedure variables (or record fields) with the tasking mechanism
(yech!) as shown in "Simulating Procedure Variables with Ada Tasks",
D.A. Lamb and P. Hilfinger, IEEE Trans. Soft. Eng.  v9#1 (Jan 83).