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,69c50fc0d29ced1b
X-Google-Attributes: gida07f3367d7,public,usenet
X-Google-NewGroupId: yes
X-Google-Language: ENGLISH,UTF8
Path: 
 g2news2.google.com!news4.google.com!feeder.news-service.com!news.mixmin.net!aioe.org!not-for-mail
From: =?utf-8?Q?Yannick_Duch=C3=AAne_=28Hibou57?=
 =?utf-8?Q?=29?=
 <yannick_duchene@yahoo.fr>
Newsgroups: comp.lang.ada
Subject: Re: Q: SPARK visibility rules and inherit annotations.
Date: Thu, 20 May 2010 03:47:53 +0200
Organization: Ada At Home
Message-ID: <op.vczdx3teule2fv@garhos>
References: <4bf3fce5$0$2399$4d3efbfe@news.sover.net>
 <568bb04d-6ad6-46da-9eb2-8d81c8c52b59@v18g2000vbc.googlegroups.com>
 <4bf45732$0$2407$4d3efbfe@news.sover.net>
NNTP-Posting-Host: Wj8XAjoNVRxqky9biWs8Mw.user.speranza.aioe.org
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8; 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:11784
Date: 2010-05-20T03:47:53+02:00
List-Id: <comp.lang.ada>

Le Wed, 19 May 2010 23:29:22 +0200, Peter C. Chapin <pcc482719@gmail.com=
>  =

a =C3=A9crit:
> One thing I like about Ada in general is how you can express a design =
in
> package specifications and then let the compiler check a few things  =

> about its
> consistency before embarking on the implementation. With SPARK that  =

> effect is
> even greater. For example in my Cryptographic_Services package the  =

> Examiner
> initially complained about how there was no way to initialize one of m=
y
> private types.
I've noticed the same, it requires some good practice to be applied,  =

someway comparable to what you could get with AdaControl and a good rule=
s  =

file (I mean AdaControl's rules). As an example, SPARK sees an error if =
 =

you forget the give the name of procedure at its end statement.

While sometime, I would like to better understand some choices, like the=
  =

one I've meet, which is that it does not accept nested package  =

specifications, or, more important, why it don't wants =E2=80=9Ctype ...=
 is new  =

...;=E2=80=9D. If I could understand the rational behind this latter res=
triction,  =

this could perhaps help me to redesign.