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,c9d5fc258548b22a
X-Google-NewGroupId: yes
X-Google-Attributes: gida07f3367d7,domainid0,public,usenet
X-Google-Language: ENGLISH,ASCII-7-bit
Path: 
 g2news1.google.com!news4.google.com!feeder3.cambriumusenet.nl!feed.tweaknews.nl!138.195.8.3.MISMATCH!news.ecp.fr!news.jacob-sparre.dk!pnx.dk!.POSTED!not-for-mail
From: "Randy Brukardt" <randy@rrsoftware.com>
Newsgroups: comp.lang.ada
Subject: Re: How do I write directly to a memory address?
Date: Tue, 1 Mar 2011 18:41:22 -0600
Organization: Jacob Sparre Andersen Research & Innovation
Message-ID: <ikk3nl$6fr$1@munin.nbi.dk>
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>
 <4d6d6e60$0$11509$882e7ee2@usenet-news.net>
NNTP-Posting-Host: static-69-95-181-76.mad.choiceone.net
X-Trace: munin.nbi.dk 1299026485 6651 69.95.181.76 (2 Mar 2011 00:41:25 GMT)
X-Complaints-To: news@jacob-sparre.dk
NNTP-Posting-Date: Wed, 2 Mar 2011 00:41:25 +0000 (UTC)
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2900.5931
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5931
X-RFC2646: Format=Flowed; Response
Xref: g2news1.google.com comp.lang.ada:17710
Date: 2011-03-01T18:41:22-06:00
List-Id: <comp.lang.ada>

"Hyman Rosen" <hyrosen@mail.com> wrote in message 
news:4d6d6e60$0$11509$882e7ee2@usenet-news.net...
> On 3/1/2011 4:52 PM, Pascal Obry wrote:
...
>> 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.

If "the environment" had a strongly typed Ada interface, then the error 
could not occur there. I suppose eventually you'll get to hardware that is 
untyped and have a source of errors at that point, but that interface can be 
minimized far more than it is. Indeed, even hardware can be typed (consider 
the Rational R1000, which was an Ada computer even in the hardware).

It is clear that many errors occur in interfacing (far more than occur in 
Ada itself); the solution is to minimize the interfacing as much as 
possible.

(Anyone that thinks that *all* errors are avoidable is an idiot. But a lot 
of errors are avoidable, far more than we actually avoid in practice.)

                        Randy.