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 autolearn=ham
	autolearn_force=no version=3.4.4
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 103376,d0fb3b725598ca25
X-Google-Attributes: gid103376,public
X-Google-ArrivalTime: 2003-03-25 02:17:42 PST
Path: 
 archiver1.google.com!news1.google.com!newsfeed.stanford.edu!news-spur1.maxwell.syr.edu!news.maxwell.syr.edu!newsfeed.icl.net!newsfeed.fjserv.net!colt.net!peernews3.colt.net!newsfeed.stueberl.de!news.m-online.net!news-FFM2.ecrc.net!news.iks-jena.de!not-for-mail
From: Lutz Donnerhacke <lutz@iks-jena.de>
Newsgroups: comp.lang.ada
Subject: Re: [Spark] How to terminate information flow?
Date: Tue, 25 Mar 2003 10:17:41 +0000 (UTC)
Organization: IKS GmbH Jena
Message-ID: <slrnb80b64.nt.lutz@taranis.iks-jena.de>
References: <slrnb7ucqt.o1.lutz@taranis.iks-jena.de>
 <3E801412.1030605@praxis-cs.co.uk>
NNTP-Posting-Host: taranis.iks-jena.de
X-Trace: branwen.iks-jena.de 1048587461 6738 217.17.192.37 (25 Mar 2003
 10:17:41 GMT)
X-Complaints-To: usenet@iks-jena.de
NNTP-Posting-Date: Tue, 25 Mar 2003 10:17:41 +0000 (UTC)
User-Agent: slrn/0.9.7.4 (Linux)
Xref: archiver1.google.com comp.lang.ada:35674
Date: 2003-03-25T10:17:41+00:00
List-Id: <comp.lang.ada>

* Peter Amey wrote:
> The short answer is that you can't make those messages go away because
> they are true!  We do not recommend slavishly trying to eliminate all
> flow errors as long as the reason for them is understood.  The Examiner
> is telling you what is _really_ happening - you have to interpret that
> information.

Ok, understood.

> What we do in these cases is:
>
> (1) Choose a good naem for the unused parameters.  e.g. UnusedRes and
>     UnusedOk.  You then get a flow error "assignment to unused is
>     ineffective" which is self-documenting.

Done.

> (2) Add a comment to line 29 saying "expect ineffective .... because ...".
>     Which maintain a justifation along with the code.

I add a comment type (--! regex) which can be parsed automatically, in order
to suppress the examiner output on this cases by a wrapper script. This
wrapper script is even necessary here to provide a editor friendly output.
I'll put the wrapper script at
  ftp://ftp.iks-jena.de/pub/mitarb/lutz/ada/spark/spark.pl
in a few hours.

> I do have a tentative plan for a a "justify" annotation which can be
> placed at the point where any flow error is produced and which will
> suppress it at that point but add it to a summary file of justified
> errors.

That would be fine, but hat very low priority. A practial workaround exists.