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=-0.8 required=5.0 tests=BAYES_00,INVALID_DATE autolearn=no autolearn_force=no version=3.4.4 Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!tut.cis.ohio-state.edu!purdue!bu.edu!inmet!stt From: stt@inmet.inmet.com Newsgroups: comp.lang.ada Subject: Re: LRM question - access types and con Message-ID: <20600054@inmet> Date: 27 Jun 90 15:53:00 GMT References: <1394@software.software.org> Nf-ID: #R:software.software.org:1394:inmet:20600054:000:421 Nf-From: inmet.inmet.com!stt Jun 27 11:53:00 1990 List-Id: Re: Allocators and tasking. The programmer need only worry about declared variables which are shared between tasks. An access collection is not considered an explicitly declared variable in this sense. The implementation must worry about all "hidden" shared data. Therefore, an implementation must protect its run-time data structures from simultaneous access. S. Tucker Taft Intermetrics, Inc. Cambridge, MA 02138