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=-1.9 required=3.0 tests=BAYES_00 autolearn=ham
	autolearn_force=no version=3.4.5-pre1
Date: 23 Sep 92 02:44:37 GMT
From: holmes@MIMSY.CS.UMD.EDU  (Holmes S. Liao)
Subject: Re: Using Global Variables
Message-ID: <60545@mimsy.umd.edu>
List-Id: <comp.lang.ada>

In article <1992Sep21.040837.10149@sei.cmu.edu> lph@sei.cmu.edu (Larry Howard) 
writes:
>We have been involved in the design of several large, real-time Ada
>applications (flight simulators) which have used shared memory extensively.

As far as I know, FAA's endeavor to implement the next generation 
distributed, fault-tolerant, real-time air traffic control system also 
uses shared memory extensively. Each workstation reserves an area to
store runtime-adaptable processor Id, facility Id, rank info., and so on.
The area is shared among all local operating units. Some of the info
in shared memory is required for message passing (header). Some others
can be modified by a global monitor on certain occasions (such as
system failure and re-configuration).

I don't see any problem with the design.

//holmes liao