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,8eff44ec1bcf8433 X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 2001-10-16 10:52:34 PST Newsgroups: comp.lang.ada Path: archiver1.google.com!news1.google.com!sn-xit-02!supernews.com!newsfeed.direct.ca!look.ca!news.maxwell.syr.edu!newspeer.radix.net!uunet!ash.uu.net!xyzzy!nntp From: Jeffrey Carter Subject: Re: Container reqs X-Nntp-Posting-Host: e246420.msc.az.boeing.com Content-Type: text/plain; charset=us-ascii Message-ID: <3BCC6CB7.20BAA30D@boeing.com> Sender: nntp@news.boeing.com (Boeing NNTP News Access) Content-Transfer-Encoding: 7bit Organization: The Boeing Company X-Accept-Language: en References: <9qctpn$lil$1@news.huji.ac.il> <3BCC01B1.18C18C98@free.fr> Mime-Version: 1.0 Date: Tue, 16 Oct 2001 17:21:59 GMT X-Mailer: Mozilla 4.73 [en]C-CCK-MCD Boeing Kit (WinNT; U) Xref: archiver1.google.com comp.lang.ada:14716 Date: 2001-10-16T17:21:59+00:00 List-Id: Jean-Marc Bourguet wrote: > > I'm not for making a container "threadsafe" to the point where > several tasks may modify the container without providing their > synchronisation. > In my experience > * most containers are accessed only by one task > * for those who are not, an explicit synchronisation is needed for > other > purpose as the container is not the only part member of the > datastructure > which has to be modified atomically. This is an interesting assertion, considering that a protected queue is a useful and common form of intertask communication. -- Jeffrey Carter