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.9 required=5.0 tests=BAYES_00 autolearn=ham autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,63360011f8addace X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 2002-07-18 10:38:13 PST Path: archiver1.google.com!news1.google.com!newsfeed.stanford.edu!news-spur1.maxwell.syr.edu!news.maxwell.syr.edu!newsfeed.cwix.com!news.binc.net!kilgallen From: Kilgallen@SpamCop.net (Larry Kilgallen) Newsgroups: comp.lang.ada Subject: Re: gnat: time-slicing Date: 18 Jul 2002 12:38:11 -0600 Organization: LJK Software Message-ID: References: <5ee5b646.0207161329.5c8e387b@posting.google.com> NNTP-Posting-Host: eisner.encompasserve.org X-Trace: grandcanyon.binc.net 1027013480 17476 192.135.80.34 (18 Jul 2002 17:31:20 GMT) X-Complaints-To: abuse@binc.net NNTP-Posting-Date: Thu, 18 Jul 2002 17:31:20 +0000 (UTC) Xref: archiver1.google.com comp.lang.ada:27234 Date: 2002-07-18T12:38:11-06:00 List-Id: In article , "Marin David Condic" writes: > if you are accessing the same variable from two tasks (which you do > implicitly with Put_Line, since the default is to use an object denoted by > the function Current_Output) this could be A Bad Thing. Accessing a shared > variable from two threads of control is going to result in unpredictable > behavior unless you do something to explicitly control the access. Or unless you have a guarantee from the Ada implementation or the operating system in that regard.