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,FREEMAIL_FROM autolearn=ham autolearn_force=no version=3.4.4 X-Google-Thread: 103376,470860aa3e635a7 X-Google-Attributes: gid103376,public,usenet X-Google-Language: ENGLISH,ASCII-7-bit Path: g2news2.google.com!news3.google.com!out03a.usenetserver.com!news.usenetserver.com!in01.usenetserver.com!news.usenetserver.com!news.tele.dk!news.tele.dk!small.news.tele.dk!lnewsinpeer00.lnd.ops.eu.uu.net!emea.uu.net!peer-uk.news.demon.net!kibo.news.demon.net!mutlu.news.demon.net!news.demon.co.uk!demon!not-for-mail From: Simon Wright Newsgroups: comp.lang.ada Subject: Re: GNAT for MS Visual Studio Date: Fri, 05 Oct 2007 21:15:25 +0100 Organization: Pushface Message-ID: References: <13duou81kg3sd1c@corp.supernews.com> <13f3e0vbb05s47c@corp.supernews.com> <13f6eg0te46m2a3@corp.supernews.com> <4xsl4zw3bp.fsf@hod.lan.m-e-leypold.de> <1191357491.860178.230380@22g2000hsm.googlegroups.com> <4702ADCC.7080209@obry.net> <1191439439.120567.172630@g4g2000hsf.googlegroups.com> <4703F02D.3030207@obry.net> <1191442124.099242.282130@57g2000hsv.googlegroups.com> NNTP-Posting-Host: pogner.demon.co.uk Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: news.demon.co.uk 1191615325 24047 62.49.19.209 (5 Oct 2007 20:15:25 GMT) X-Complaints-To: abuse@demon.net NNTP-Posting-Date: Fri, 5 Oct 2007 20:15:25 +0000 (UTC) Cancel-Lock: sha1:LSwOyoVzAGqRPx3yrIEypimFw0s= User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.1 (darwin) Xref: g2news2.google.com comp.lang.ada:2322 Date: 2007-10-05T21:15:25+01:00 List-Id: Maciej Sobczak writes: > On 3 Pa , 21:40, Pascal Obry wrote: > >> The container won't change, so this can't be a problem. > > The visible state of the container might not change, but the > container is free to do some accounting, for example with cursors, > to ensure the ability to catch any misuse. If the library is not protected internally against concurrent access then it would be a clever implementation that could guarantee even to detect misuse. I suppose it could do something involving pragma Atomic and a use count. I had thought that the Booch Components would be readably shared, but not so -- the Unbounded and Unmanaged forms maintain a simple internal cache which isn't atomic and could be trashed by concurrent access. > There is one thing that might help here - the documentation of the > given library implementation. The only info you can rely on is that in the standard, of course.