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.3 required=5.0 tests=BAYES_00,FREEMAIL_FROM,
	INVALID_MSGID autolearn=no autolearn_force=no version=3.4.4
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 103376,74b55538385b7366
X-Google-Attributes: gid103376,public
From: "Vladimir Olensky" <vladimir_olensky@yahoo.com>
Subject: Re: Ada safety road Was: Which is right ...
Date: 1999/06/13
Message-ID: <929222561.966.57@news.remarQ.com>#1/1
X-Deja-AN: 488892789
References: <928083159.436.79@news.remarQ.com>
 <m33e0el4vr.fsf@deneb.cygnus.stuttgart.netsurf.de>
 <928174549.336.98@news.remarQ.com> <7iuqkc$ln6$1@nnrp1.deja.com>
 <928529202.956.79@news.remarQ.com> <928569312.951.42@news.remarQ.com>
 <7jb1l9$694$1@nnrp1.deja.com> <928703068.617.98@news.remarQ.com>
 <375F6F0B.AD735B5B@praxis-cs.co.uk> <7jo1d2$kno$1@pegasus.csx.cam.ac.uk>
 <929128919.557.95@news.remarQ.com> <7jsdkf$v3p$1@nnrp1.deja.com>
 <489533776wnr@diphi.demon.co.uk>
X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3
X-Complaints-To: newsabuse@remarQ.com
X-Trace: 929222561.966.57 K3TLTKYJOA5C9C7F8C qube-02.us-ca.remarq.com
Organization: Posted via RemarQ Communities, Inc.
NNTP-Posting-Date: Sat, 12 Jun 1999 21:22:41 GMT
Newsgroups: comp.lang.ada
Date: 1999-06-13T00:00:00+00:00
List-Id: <comp.lang.ada>


JP Thornley wrote in message <489533776wnr@diphi.demon.co.uk>...
>In article: <7jsdkf$v3p$1@nnrp1.deja.com>  Robert Dewar
><robert_dewar@my-deja.com> writes:
>
>(with reference to the HRG Guidance)
>
>> it is VERY specifically aimed at safety critical programming
>> in Ada
>
>Definitely not so - and if this becomes the accepted idea then a number
>of programmers are likely to ignore a very useful document.
>(Particularly if they take Robert's other comments to mean that
>safety-critical programming is an arcane art with little connection to
>the 'real-world').
>
>The Guide is _aimed at_ producers of high integrity software, where the
>software supplier is (usually) required to demonstrate the integrity of
>the software to a third party (who may be a certification authority or,
>perhaps, a knowledgeable customer).
>
>It is _useful to_ anyone who wants to make consistent use of one or more
>of the verification methods referenced in the Guide as it helps them to
>avoid language features that are difficult to verify by the chosen
>techniques. (All of the usual techniques are included in the Guide.)


Suport all said above.

>
>In another message, "Vladimir Olensky" <vladimir_olensky@yahoo.com>
>wrote:
>> What is interesting it was published only 30 days ago (99-05-11).
>
>Yes, but that is simply the latest in a long line of minor revisions.
>The document has been largely unchanged for over a year - an earlier
>draft was published in Ada Letters last year (may have been around
>April/May) and there are some detailed changes from that version, but
>nothing major.


I've seen N350 also.
To my point of view one of the  problems with it was that it  was not widely
advertised.
The other thing is an erroneous idea that writing reliable software  is VERY
specialized area.

Regards,

Vladimir Olensky