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: 103376,3f4112f9d4cec374 X-Google-NewGroupId: yes X-Google-Attributes: gida07f3367d7,domainid0,public,usenet X-Google-Language: ENGLISH,UTF8 Path: g2news1.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?= Newsgroups: comp.lang.ada Subject: Re: SPARK POGS: List the rules used by the Simplifier Date: Fri, 13 Aug 2010 21:41:32 +0200 Organization: Ada At Home Message-ID: References: <0885ddcf-4d87-4cb5-a7ff-53d4397e0c8a@j8g2000yqd.googlegroups.com> <25335b0c-f1d6-4816-be30-a2c8c71018e9@i31g2000yqm.googlegroups.com> NNTP-Posting-Host: M2yP1Cx/h9YxW/Ct5b534Q.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.60 (Win32) Xref: g2news1.google.com comp.lang.ada:13237 Date: 2010-08-13T21:41:32+02:00 List-Id: Le Fri, 13 Aug 2010 21:04:00 +0200, Phil Thornley = a =C3=A9crit: > No - *.rls files are produced by the Examiner, so it doesn't really > matter which of the rules in these files are used (in fact most of > them are not used). > > These summaries are of the user rules - in *.rlu files - which are > hand coded and so have to be reviewed and maintained as the code > develops. It's useful to be able to keep these rules to a minimum to > keep the maintenance load down. Oops, so this can be seen as an extraction of some of the reports which = = belongs to *.slg files ? (the ones where steps of proof are exposed, lik= e = =E2=80=9CApplied substitution rule multiply_rules(3)=E2=80=9D and etc). = Please, don't kick = if I'm still wrong. > (And, for example, one of the changes with SPARK 2010 will remove the > need for user rules for function return annotations, so these > summaries will help to identify which those rules are.) Will see (I am not aware of these change so far). > In fact this information is already in the POGS summary - but it is > given for each operation, ahead of the table showing each VC in the > operation, and the way that it is presented makes it tedious to > identify which rules have/have not been used - particularly for > 'package' rule files that might be used by a number of different > operations. OK (I don't use POGS so much, I mostly read *.siv files... and I am not = = using SPARK every day) By the way, if you want to join, I am to open a new thread about =E2=80=9C= SPARK = understand me very well... me neither=E2=80=9D :D -- = There is even better than a pragma Assert: a SPARK --# check. --# check C and WhoKnowWhat and YouKnowWho; --# assert Ada; -- i.e. forget about previous premises which leads to conclusion -- and start with new conclusion as premise.