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,48e1a3c594fb62e8
X-Google-Attributes: gida07f3367d7,public,usenet
X-Google-NewGroupId: yes
X-Google-Language: ENGLISH,UTF8
Path: 
 g2news2.google.com!news4.google.com!proxad.net!feeder1-2.proxad.net!usenet-fr.net!gegeweb.org!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: SPARK
Date: Thu, 13 May 2010 05:06:23 +0200
Organization: Ada At Home
Message-ID: <op.vcmiwxowule2fv@garhos>
References: <op.vcl6900wule2fv@garhos>
NNTP-Posting-Host: FD8vExnEy5iRSNWAUP6U/Q.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:11577
Date: 2010-05-13T05:06:23+02:00
List-Id: <comp.lang.ada>

Some quick though to feed the talk and give interested parties an  =

opportunity to take part.

Although I can understand most of the restrictions SPARK applies (a big =
 =

amount of them did not ever requires to use SPARK to be meaningful and  =

beneficial and I do apply lot of them already), I still don't understand=
  =

one : the restriction of not using derived type (except tagged type, whi=
ch  =

are supported by SPARK). What was the rational for that ?

Functions may have legitimate side effects, like for memoisation.  =

Memoisation is a kind of optimization and optimizations should be  =

transparent to clients. SPARK would requires to split it into two parts:=
 a  =

kind of =E2=80=9Cprepare/compute=E2=80=9D procedure and a =E2=80=9Cget r=
esult=E2=80=9D function ; the  =

procedure being supposedly invoked prior to each function invokation. Di=
d  =

you ever face this ?

Block statements are not allowed in SPARK. Let say a procedure can do th=
e  =

same. Was this only to have one-matter-one-feature (avoid to have both  =

block-statement and procedure, and keep only one) for the sake of  =

simplicity or was there some other reasons properly dealing with  =

verifiability ?

-- =

pragma Asset ? Is that true ? Waaww... great