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: a07f3367d7,ec6f74e58e86b38b
X-Google-Attributes: gida07f3367d7,public,usenet
X-Google-NewGroupId: yes
X-Google-Language: ENGLISH,ASCII
Path: 
 g2news2.google.com!news4.google.com!feeder.news-service.com!news.mixmin.net!aioe.org!not-for-mail
From: =?iso-8859-15?Q?Yannick_Duch=EAne_=28Hibou57=29?=
 <yannick_duchene@yahoo.fr>
Newsgroups: comp.lang.ada
Subject: Re: Lost in translation (with SPARK user rules)
Date: Wed, 26 May 2010 21:28:58 +0200
Organization: Ada At Home
Message-ID: <op.vdbu2ksqxmjfy8@garhos>
References: <op.vda45rsfule2fv@garhos>
 <0466e131-cc80-4db4-b080-eec9aefcb1c7@z17g2000vbd.googlegroups.com>
 <op.vda7dlc2ule2fv@garhos> <4bfd2d05$0$27598$ba4acef3@reader.news.orange.fr>
 <siotu5lyiw08.u5c5kcrly3i2$.dlg@40tude.net>
NNTP-Posting-Host: VsdMw8HJ6uo7b6guDb/gnA.user.speranza.aioe.org
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-15; format=flowed; delsp=yes
Content-Transfer-Encoding: Quoted-Printable
X-Complaints-To: abuse@aioe.org
X-Notice: Filtered by postfilter v. 0.8.2
User-Agent: Opera Mail/10.53 (Win32)
Xref: g2news2.google.com comp.lang.ada:12045
Date: 2010-05-26T21:28:58+02:00
List-Id: <comp.lang.ada>

Le Wed, 26 May 2010 16:28:20 +0200, Dmitry A. Kazakov  =

<mailbox@dmitry-kazakov.de> a =E9crit:
> Yes. I think this could be a direction in which Ada should evolve. It
> should have a modular part equivalent to SPARK, which can be used with=

> certain compilation units. So that the programmer could choose the lev=
el  =

> of
> safety he is ready to invest into.

Please, tell more : you mean a kind of pragma or compiler option like th=
e  =

ones there is for runtime checks ?

By the way, that's an opportunity for two other ideas : why not integrat=
e  =

the SPARK language definition in the Ada standard ? We may have wordings=
  =

in the Ada reference or the annotated reference, stating that is and tha=
t  =

is allowed or disallowed with SPARK. And second thing, related to this  =

latter : why not an ACAT tests suit targeting SPARK/Ada compilation  =

capabilities beside of full Ada ? Actually, how can you test an compiler=
  =

compliance with SPARK ? I feel you can do it only for full Ada.

> It would be nice to be able to start the project at some middle level =
(a
> bit higher than of present Ada, but lower than SPARK), and then gradua=
lly
> adjust it, as the project evolves.
Like ensuring it is written in a valid SPARK syntax before we know if th=
is  =

part will really be semantically checked or not ?

> Another 2 cents.
Re-no, re-was re-valuable


-- =

There is even better than a pragma Assert: a SPARK --# check.