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!feeder.news-service.com!newsfeed.straub-nv.de!uucp.gnuu.de!newsfeed.arcor.de!newsspool1.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>
 <4d4ff70e$0$6886$9b4e6d93@newsspool2.arcor-online.net>
 <737a6396-72bd-4a1e-8895-7d50f287960e@d28g2000yqc.googlegroups.com>
 <4d5008a5$0$6879$9b4e6d93@newsspool2.arcor-online.net>
 <eda00084-fcc3-416c-bd3e-8b9e9c1a4b40@o13g2000yql.googlegroups.com>
 <4d5031fe$0$6765$9b4e6d93@newsspool3.arcor-online.net>
 <1f229967-d3cf-42b6-8087-c97ee08652f3@i40g2000yqh.googlegroups.com>
 <4d5110ea$0$7669$9b4e6d93@newsspool1.arcor-online.net>
 <1fb3ce45-ffcc-4c1c-8f76-d151975c8425@x1g2000yqb.googlegroups.com>
 <4d511500$0$7665$9b4e6d93@newsspool1.arcor-online.net>
 <ea9f26e9-c741-4732-824a-ca4a3cf2a353@m16g2000prc.googlegroups.com>
 <4d518a90$0$7651$9b4e6d93@newsspool1.arcor-online.net>
 <op.vqlqqzxllzeukk@jellix.jlfencey.com>
 <4d51b471$0$6772$9b4e6d93@newsspool3.arcor-online.net>
 <op.vqls7lellzeukk@jellix.jlfencey.com>
 <1lajq4dvy7368.41bre951qpy3$.dlg@40tude.net>
 <op.vqnesepflzeukk@jellix.jlfencey.com>
Date: Wed, 9 Feb 2011 21:03:37 +0100
Message-ID: <6r07nah77nc1$.uwqkyjfg484k$.dlg@40tude.net>
NNTP-Posting-Date: 09 Feb 2011 21:03:35 CET
NNTP-Posting-Host: f016a274.newsspool2.arcor-online.net
X-Trace: 
 DXC=X3b;`Fa5^2n016@cHD@m;jA9EHlD;3Ycb4Fo<]lROoRa8kF<OcfhCOkd6k@k3`FIUg[6LHn;2LCVn[<mhadbfdUkm5dQF0[hebn^5m0o`UVB4l
X-Complaints-To: usenet-abuse@arcor.de
Xref: g2news2.google.com comp.lang.ada:18114
Date: 2011-02-09T21:03:35+01:00
List-Id: <comp.lang.ada>

On Wed, 09 Feb 2011 19:25:16 +0100, Vinzent Hoefler wrote:

> Dmitry A. Kazakov wrote:
> 
>> Unfortunately not. The problem is that the C language was not designed in
>> order to be used at this level of scrutiny. It becomes extremely annoying
>> because many warnings are false negatives. It is a structural problem of C:
>> the number of false negatives cannot be reduced without increasing the
>> number of false positives. And this is not the compiler's problem only.
>> When you read C program you have to set your alarm level much lower than
>> for Ada. Because otherwise, you won't be able to understand the program at
>> all.
> 
> So tell me what I did wrong. In the eight months I spent in the auto-motive
> sector [so I literally moved up ;)] I did MISRA-C, both compilers were tuned
> to their maximum warning level and PC-Lint was run with a quite restrictive
> set of rules. The goal was zero warnings from those tools. I think, I had
> two which could not be circumvented and thus could count as false-positives.

You circumvented false alarm rather than fixed actual problems. Did it make
the program more readable?

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