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
Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!seismo!rochester!cornell!uw-beaver!mit-eddie!husc6!cca!mirror!ishmael!ada-uts!stt
From: stt@ada-uts
Newsgroups: comp.lang.ada
Subject: Re: passing a task type as a generic pa
Message-ID: <57900033@ada-uts>
Date: Thu, 9-Jul-87 14:36:00 EDT
Article-I.D.: ada-uts.57900033
Posted: Thu Jul  9 14:36:00 1987
Date-Received: Sat, 18-Jul-87 06:57:30 EDT
References: <11262@ucbvax.Berkeley.EDU>
Nf-ID: #R:ucbvax.Berkeley.EDU:-1126200:ada-uts:57900033:000:479
Nf-From: ada-uts!stt    Jul  9 14:36:00 1987
List-Id: <comp.lang.ada>


In general, there is not much you can do with a limited private
generic formal type (whether or not it is a task type),
unless you provide operations along with the type.

Therefore your generic should have generic formal
subprograms along with the type.  The generic actual subprograms
will probably have to be simple procedures which take the
task as a parameter and call the desired entry, rather
than the entries themselves.

Tucker Taft
c/o Intermetrics, Inc.
Cambridge, MA