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=0.4 required=5.0 tests=BAYES_00,FORGED_MUA_MOZILLA
	autolearn=no autolearn_force=no version=3.4.4
X-Google-Thread: 103376,8fd9e333acefd8a3,start
X-Google-NewGroupId: yes
X-Google-Attributes: gida07f3367d7,domainid0,public,usenet
X-Google-Language: ENGLISH,ASCII-7-bit
Received: by 10.68.202.37 with SMTP id kf5mr4837208pbc.7.1333922882356;
        Sun, 08 Apr 2012 15:08:02 -0700 (PDT)
Path: 
 r9ni34232pbh.0!nntp.google.com!news1.google.com!news2.google.com!Xl.tags.giganews.com!border1.nntp.dca.giganews.com!nntp.giganews.com!local2.nntp.dca.giganews.com!news.giganews.com.POSTED!not-for-mail
NNTP-Posting-Date: Sun, 08 Apr 2012 17:07:59 -0500
Date: Sun, 08 Apr 2012 18:07:48 -0400
From: "Peter C. Chapin" <PChapin@vtc.vsc.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64;
 rv:11.0) Gecko/20120327 Thunderbird/11.0.1
MIME-Version: 1.0
Newsgroups: comp.lang.ada
Subject: Question about Spark_IO
Message-ID: <Cf2dnRYegbnckR_S4p2dnAA@giganews.com>
X-Usenet-Provider: http://www.giganews.com
X-Trace: 
 sv3-P8Do7Ndyryxdi0xZ0TyKWuAJz/ZBa3pNN/VYPZQ+VGKi4LMQj+znz1nA3LtJ5YBKXpKMrLIZlswxSdy!vwjKwSupONk0FyGUnUo5ah+u56Cpft5qEQVIvaOQi1gaX/0n/dWpaJkaKunIqSY=
X-Complaints-To: abuse@giganews.com
X-DMCA-Notifications: http://www.giganews.com/info/dmca.html
X-Abuse-and-DMCA-Info: Please be sure to forward a copy of ALL headers
X-Abuse-and-DMCA-Info: Otherwise we will be unable to process your complaint
 properly
X-Postfilter: 1.3.40
X-Original-Bytes: 1813
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Date: 2012-04-08T18:07:48-04:00
List-Id: <comp.lang.ada>

I'm doing something like this to close a file using Spark_IO

    Spark_IO.Close(Input, Input_Status);
    if Input_Status /= Spark_IO.Ok then ...

The Examiner says there is a flow error with the first line because the 
assignment to Input is "ineffective." This is because it is an 'in out' 
parameter and nothing is being done with the returned value.

My understanding is that Close puts the file handle it has been given 
into an invalid state so that any further use of it will result in an 
error. Thus it is not correct to do anything with that value after Close 
returns.

Is this a case where it is appropriate to suppress the flow error with 
an '--# accept flow_message...' annotation or is there some better way 
to handle this situation?

Thanks!

Peter