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.1 required=5.0 tests=BAYES_20,INVALID_DATE
	autolearn=no autolearn_force=no version=3.4.4
Path: utzoo!attcan!uunet!wuarchive!usc!orion.oac.uci.edu!ucivax!gateway
From: jduarte@ternes.ICS.UCI.EDU (J o s e D u a r t e ! ! !)
Newsgroups: comp.lang.ada
Subject: procedural variables
Message-ID: <9102110959.aa23851@PARIS.ICS.UCI.EDU>
Date: 11 Feb 91 18:04:29 GMT
List-Id: <comp.lang.ada>



	Since Ada does not provide for procedural variables, how
do you/your associates handle the need for having a procedure or
a task perform different duties depending on run-time circumstances?

	One scenario would be to pass an enumeration value to the
procedure and then to use "if-then-else-end if" or "case" statements to
determine which procedure should be run. This approach will work;
however, it seems inelegant.


	Does anyone one out there have a "nifty" solution or idea
that they would be willing to share?

Thanks,

JOSE D.