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,c9d5fc258548b22a
X-Google-NewGroupId: yes
X-Google-Attributes: gida07f3367d7,domainid0,public,usenet
X-Google-Language: ENGLISH,ASCII-7-bit
Path: 
 g2news2.google.com!news1.google.com!border1.nntp.dca.giganews.com!nntp.giganews.com!news-xxxfer.readnews.com!news-out.readnews.com!postnews3.readnews.com!not-for-mail
Date: Tue, 01 Mar 2011 17:08:32 -0500
From: Hyman Rosen <hyrosen@mail.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
 rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7
MIME-Version: 1.0
Newsgroups: comp.lang.ada
Subject: Re: How do I write directly to a memory address?
References: 
 <67063a5b-f588-45ea-bf22-ca4ba0196ee6@l11g2000yqb.googlegroups.com>
 <31c357bd-c8dc-4583-a454-86d9c579e5f4@m13g2000yqb.googlegroups.com>
 <05a3673e-fb97-449c-94ed-1139eb085c32@x1g2000yqb.googlegroups.com>
 <4d4c232a$0$28967$882e7ee2@usenet-news.net> <4D4D6506.50909@obry.net>
 <4d50095f$0$22393$882e7ee2@usenet-news.net>
 <wcck4hb95jz.fsf@shell01.TheWorld.com>
 <4d6d56c4$0$11509$882e7ee2@usenet-news.net> <4D6D6A90.2090108@obry.net>
In-Reply-To: <4D6D6A90.2090108@obry.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Message-ID: <4d6d6e60$0$11509$882e7ee2@usenet-news.net>
NNTP-Posting-Host: aa943177.usenet-news.net
X-Trace: 
 DXC=7aBJ=M45B099AmIGXU7hU3^oXGM_6\KV0mX0AG3X_jU?bO=B]JiG>>=VjKk:Lk^BN1cR12TN^Bg7>O6DZ1OMjcH;E2TC\hF^UY7
X-Complaints-To: abuse@usenet-news.net
Xref: g2news2.google.com comp.lang.ada:18674
Date: 2011-03-01T17:08:32-05:00
List-Id: <comp.lang.ada>

On 3/1/2011 4:52 PM, Pascal Obry wrote:
>> It's somewhat ironic given this discussion that we've recently
>> seen the GNATColl error which caused incorrect string values to
>> be inserted into the database! It should serve as a caution to
>> those who seamlessly transition from "Ada is immune to entire
>> classes of errors prevalent in C++" to "Ada is immune to errors".
>
> Right, but note that this is an *interface* problem which does not
 > involve Ada only. I've also seen many problems to have proper
> implementation for filenames with spaces and pathnames with slashes
 > or backslash. Quoting the spaces, escaping for the backslashes
> when passing to OS process... Again is that really Ada fault, I would
 > say not but I may be biased.

What does that mean? Every program ultimately interfaces with its
environment and must do so in the correct way. When a program gets
this wrong then it has an error, and that is true even when the
program is written in Ada. This example proves that Ada programmers,
even ostensibly good ones who work for the company that makes the
compiler, can make "stupid" mistakes like putting in extra quotes
where they don't belong. That's a given, of course, because no one
is immune to this sort of error, but as I said, in these language
wars people erroneously progress from "my language is immune to a
certain class of errors" to "my language is immune to errors".