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!g49g2000cwa.googlegroups.com!not-for-mail From: "Dmitriy Anisimkov" Newsgroups: comp.lang.ada Subject: Re: GCC 4.0 Ada.Containers Cursor danger. Date: 10 Jul 2005 19:24:29 -0700 Organization: http://groups.google.com Message-ID: <1121048669.574541.170320@g49g2000cwa.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> <1120707674.230510.280700@g47g2000cwa.googlegroups.com> <1120790099.587120.319610@g49g2000cwa.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 1121048675 14592 127.0.0.1 (11 Jul 2005 02:24:35 GMT) X-Complaints-To: groups-abuse@google.com NNTP-Posting-Date: Mon, 11 Jul 2005 02:24:35 +0000 (UTC) In-Reply-To: User-Agent: G2/0.2 Complaints-To: groups-abuse@google.com Injection-Info: g49g2000cwa.googlegroups.com; posting-host=80.89.131.48; posting-account=t4CEmgwAAAA8dL2naG2k3iz_rN__dZy3 Xref: g2news1.google.com comp.lang.ada:11990 Date: 2005-07-10T19:24:29-07:00 List-Id: << *You* can if you want to but *I* might say to myself, "This is a TCP-based stream, why should I double-check what the transport layer is doing anyway?" >> The transport layer is protected enought. I'm talking about protection of the reader side from errors on the writers side. So the errors (or malicious intent) on the sender would not cause broken memory on the reader side.