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,99ab4bb580fc34cd
X-Google-Attributes: gid103376,public
From: dewar@cs.nyu.edu (Robert Dewar)
Subject: Re: Q: access to subprogram
Date: 1996/07/15
Message-ID: <dewar.837476413@schonberg>#1/1
X-Deja-AN: 169116031
references: <dewar.836964092@schonberg>> <JSA.96Jul10213633@organon.com>
 <dewar.837095740@schonberg> <4sehmr$p7f@wdl1.wdl.lmco.com>
organization: Courant Institute of Mathematical Sciences
newsgroups: comp.lang.ada
Date: 1996-07-15T00:00:00+00:00
List-Id: <comp.lang.ada>


Mark says

"Does tasking mess the static link vs display trade off in any way.  I.E.
a procedure nested in a task nested in a procedure and you want to pass
the inner most procedure as a parameter."

The only effect is that if you are using a single global display, you need
to switch displays when you switch tasks, which means that the display
has to be per-task data. A common implementation approach is to put the
display in the TCB, and then have a register pointing to the TCB.