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.4 required=5.0 tests=AC_FROM_MANY_DOTS,BAYES_00 autolearn=no 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 05:19:50 PST Path: archiver1.google.com!news1.google.com!newsfeed.stanford.edu!news-spur1.maxwell.syr.edu!news.maxwell.syr.edu!newsfeed1.cidera.com!Cidera!cyclone1.gnilink.net!spamfinder.gnilink.net!nwrddc01.gnilink.net.POSTED!53ab2750!not-for-mail From: "Frank J. Lhota" Newsgroups: comp.lang.ada References: <5ee5b646.0207161329.5c8e387b@posting.google.com> Subject: Re: gnat: time-slicing X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 5.50.4807.1700 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700 Message-ID: Date: Thu, 18 Jul 2002 12:02:51 GMT NNTP-Posting-Host: 141.157.176.41 X-Complaints-To: abuse@verizon.net X-Trace: nwrddc01.gnilink.net 1026993771 141.157.176.41 (Thu, 18 Jul 2002 08:02:51 EDT) NNTP-Posting-Date: Thu, 18 Jul 2002 08:02:51 EDT Xref: archiver1.google.com comp.lang.ada:27218 Date: 2002-07-18T12:02:51+00:00 List-Id: "Jan Prazak" wrote in message news:pan.2002.07.17.18.15.32.366460.1723@gmx.net... > There is no output to a file. And I think it's an interesting example (if > it works as explained in the tutorial), because it shows that tasking can > be dangerous in some way. The fact that "tasking can be dangerous in some way" is common knowledge. Moreover, most programmers who have done tasking / multithreading should spot the error in this example right away - two tasks are using the same resource (current output) with no guards against concurrent access.