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=-0.5 required=3.0 tests=BAYES_05 autolearn=ham
	autolearn_force=no version=3.4.5-pre1
Date: 25 Sep 92 22:58:00 GMT
From: netcomsv!iscnvx!news@decwrl.dec.com
Subject: Re: Using Global Variables
Message-ID: <92269.56792.LJ10891@LMSC5.IS.LMSC.LOCKHEED.COM>
List-Id: <comp.lang.ada>

------------------------- Original Article -------------------------
>    With the result that anybody who needs to access anything in shared
>memory now has full access to everything in shared memory.  Ah, informa-
>tion hiding, what has happened to you?
                                                          >             Charlie

   True, but the problem domain under discussion seemed centered around
large memory areas with common access requirements.  For a more discriminating,
less refined (yes, I do believe that parameter passing is more refined and
controllable), method one could open the pandora's box of:

package GLOBAL_1 is ...   -- regionals associated with some functionality
package GLOBAL_2 is ...   -- regionals associated with another functionality
..  -- etc.

   Synchronization is left as an exercise for the masochist.  :-)

   Trey Haddad (ghaddad@lmsc.lockheed.com)
These opinions were left on my doorstep, would you give them a good home?