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=unavailable autolearn_force=no version=3.4.4 X-Received: by 2002:a24:2f05:: with SMTP id j5-v6mr1901818itj.37.1527832648359; Thu, 31 May 2018 22:57:28 -0700 (PDT) X-Received: by 2002:aca:eb85:: with SMTP id j127-v6mr248555oih.13.1527832648290; Thu, 31 May 2018 22:57:28 -0700 (PDT) Path: eternal-september.org!reader01.eternal-september.org!reader02.eternal-september.org!feeder.eternal-september.org!border1.nntp.ams1.giganews.com!nntp.giganews.com!feeds.phibee-telecom.net!newsfeed.xs4all.nl!newsfeed7.news.xs4all.nl!85.12.16.69.MISMATCH!peer02.ams1!peer.ams1.xlned.com!news.xlned.com!peer02.am4!peer.am4.highwinds-media.com!peer01.iad!feed-me.highwinds-media.com!news.highwinds-media.com!v8-v6no1651627itc.0!news-out.google.com!f20-v6ni982itd.0!nntp.google.com!u74-v6no1665105itb.0!postnews.google.com!glegroupsg2000goo.googlegroups.com!not-for-mail Newsgroups: comp.lang.ada Date: Thu, 31 May 2018 22:57:28 -0700 (PDT) In-Reply-To: Complaints-To: groups-abuse@google.com Injection-Info: glegroupsg2000goo.googlegroups.com; posting-host=2a04:ae04:9408:b600:ec28:b853:ecb6:d478; posting-account=-SMKVgoAAAA8u8UnmI_NwOPA-LGqXugp NNTP-Posting-Host: 2a04:ae04:9408:b600:ec28:b853:ecb6:d478 References: <13ec49fb-8c1a-42a4-b1a2-3984d0e159f7@googlegroups.com> User-Agent: G2/1.0 MIME-Version: 1.0 Message-ID: Subject: Re: Memory pools From: gorgelo@hotmail.com Injection-Date: Fri, 01 Jun 2018 05:57:28 +0000 Content-Type: text/plain; charset="UTF-8" X-Received-Bytes: 2338 X-Received-Body-CRC: 1761426709 Xref: reader02.eternal-september.org comp.lang.ada:52833 Date: 2018-05-31T22:57:28-07:00 List-Id: Den fredag 1 juni 2018 kl. 00:57:10 UTC+2 skrev Randy Brukardt: > ... > > pragma Suppress (Tampering_Check); > > -- Tampering checks are only for multi-task applications. > > -- Since this application is single task we can safely > > -- suppress tampering checks of the standard containers. > > This is a completely false statement. Tampering checks are designed to > prevent problems with iterators and element access, no tasks need to be > involved (indeed, they don't do anything in a tasking environment - such > code is usually erroneous). For instance, without tampering checks, an > iterator might run forever or otherwise malfunction. Similarly, for > Update_Element and other sorts of element access. > > Randy. > Simon wrote: > Not true! Try forward looping over a Vector to find particuler members > and deleting them in the loop. Thanks for the correction Simon and Randy! /Joakim