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,f2690a5e963b61b6 X-Google-Attributes: gid103376,public X-Google-Language: ENGLISH,ASCII-7-bit Path: g2news1.google.com!postnews.google.com!g47g2000cwa.googlegroups.com!not-for-mail From: "Dmitriy Anisimkov" Newsgroups: comp.lang.ada Subject: Re: GCC 4.0 Ada.Containers Cursor danger. Date: 6 Jul 2005 20:41:14 -0700 Organization: http://groups.google.com Message-ID: <1120707674.230510.280700@g47g2000cwa.googlegroups.com> References: <1120474891.635131.216700@g44g2000cwa.googlegroups.com> <1120575076.876798.108220@g44g2000cwa.googlegroups.com> <1120583470.429264.325450@g43g2000cwa.googlegroups.com> <1120586558.930583.79880@g49g2000cwa.googlegroups.com> <1120590526.790939.236390@g49g2000cwa.googlegroups.com> <1120591595.158965.50780@g44g2000cwa.googlegroups.com> <1120592684.622723.174350@g44g2000cwa.googlegroups.com> <1120593983.215972.308010@g14g2000cwa.googlegroups.com> <1120615856.997416.158870@g14g2000cwa.googlegroups.com> NNTP-Posting-Host: 80.89.131.48 Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" X-Trace: posting.google.com 1120707679 29384 127.0.0.1 (7 Jul 2005 03:41:19 GMT) X-Complaints-To: groups-abuse@google.com NNTP-Posting-Date: Thu, 7 Jul 2005 03:41:19 +0000 (UTC) In-Reply-To: User-Agent: G2/0.2 Complaints-To: groups-abuse@google.com Injection-Info: g47g2000cwa.googlegroups.com; posting-host=80.89.131.48; posting-account=t4CEmgwAAAA8dL2naG2k3iz_rN__dZy3 Xref: g2news1.google.com comp.lang.ada:11922 Date: 2005-07-06T20:41:14-07:00 List-Id: <> The danger of this operations is undersood, at least for me. <> I do not know how the streams and IO could broke memory. Could you explain a bit more ? I think Ada.Containers cursors should not be in the same danger as Unchecked_*** operations.