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=-0.3 required=5.0 tests=BAYES_00,
	REPLYTO_WITHOUT_TO_CC autolearn=no 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!news3.google.com!feeder1-2.proxad.net!proxad.net!feeder2-2.proxad.net!newsfeed.arcor.de!newsspool3.arcor-online.net!news.arcor.de.POSTED!not-for-mail
From: "Dmitry A. Kazakov" <mailbox@dmitry-kazakov.de>
Subject: Re: How do I write directly to a memory address?
Newsgroups: comp.lang.ada
User-Agent: 40tude_Dialog/2.0.15.1
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Reply-To: mailbox@dmitry-kazakov.de
Organization: cbb software GmbH
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>
Date: Tue, 1 Mar 2011 21:47:54 +0100
Message-ID: <16u9ka51wbukr$.1fj2sb73j9rv6.dlg@40tude.net>
NNTP-Posting-Date: 01 Mar 2011 21:47:51 CET
NNTP-Posting-Host: b6317277.newsspool2.arcor-online.net
X-Trace: 
 DXC=EBbOM0T:Tgh9kIfcjg:0fdA9EHlD;3Ycb4Fo<]lROoRa8kF<OcfhCOkd6k@k3`FIUg[6LHn;2LCVn[<mhadbfdUk5PLZ?d611Ifl572ljL>==g
X-Complaints-To: usenet-abuse@arcor.de
Xref: g2news2.google.com comp.lang.ada:18667
Date: 2011-03-01T21:47:51+01:00
List-Id: <comp.lang.ada>

On Tue, 01 Mar 2011 15:27:49 -0500, Hyman Rosen 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 against deploying damaging, unsafe and often
useless technologies like RDBMS. There should be no such thing (there
definitely exist better approaches to persistence) and no languages like
SQL.

Though this has nothing to do with Ada or C++, except that C is to blame
for horrific interfaces to the RDBMS, making them worse than SQL requires.

> 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".

No, Ada is immune exactly to this class of errors, which arise from
unnecessary type conversions. The only reason why conversion is there is
because of inability of C to describe even that pitiful set of datatypes
SQL is capable of. Kick the mess out, rewrite it in Ada, and there will be
no place for these errors. 

There cannot be safety if you communicate unsafe components.

-- 
Regards,
Dmitry A. Kazakov
http://www.dmitry-kazakov.de