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-Thread: 103376,f2690a5e963b61b6
X-Google-Attributes: gid103376,public
X-Google-Language: ENGLISH,ASCII-7-bit
Path: 
 g2news1.google.com!news4.google.com!news.glorb.com!news-in.ntli.net!newsrout1-win.ntli.net!ntli.net!xara.net!gxn.net!194.159.246.34.MISMATCH!peer-uk.news.demon.net!kibo.news.demon.net!news.demon.co.uk!demon!not-for-mail
From: Simon Wright <simon@pushface.org>
Newsgroups: comp.lang.ada
Subject: Re: GCC 4.0 Ada.Containers Cursor danger.
Date: Sat, 09 Jul 2005 07:17:05 +0100
Organization: Pushface
Message-ID: <m2pstsy04e.fsf@grendel.local>
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>
 <qMednb705_KZw1HfRVn-3w@megapath.net>
 <1120707674.230510.280700@g47g2000cwa.googlegroups.com>
 <CIadnbEyqbna4lDfRVn-tA@megapath.net>
 <1120790099.587120.319610@g49g2000cwa.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 1120889818 2278 62.49.19.209 (9 Jul 2005 06:16:58
 GMT)
X-Complaints-To: abuse@demon.net
NNTP-Posting-Date: Sat, 9 Jul 2005 06:16:58 +0000 (UTC)
Cancel-Lock: sha1:8R3L7wyJteT6/NCCa9qdIW0PC+s=
User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.0.50 (darwin)
Xref: g2news1.google.com comp.lang.ada:11970
Date: 2005-07-09T07:17:05+01:00
List-Id: <comp.lang.ada>

"Dmitriy Anisimkov" <anisimkov@yahoo.com> writes:

> I think we could have a check for about 99.9% errors in stream reading
> if we put some checking bytes into input data format.

*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?"

If on the other hand my system is built up of many parts, not all of
which are under my control, and some of which are built in C, I might
want checks built in if only to make sure I can integrate the
thing. But then I doubt I'll be able to use Ada.Streams all that
easily.