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-Thread: 103376,7eef1e530c6ffb21 X-Google-NewGroupId: yes X-Google-Attributes: gida07f3367d7,domainid0,public,usenet X-Google-Language: ENGLISH,ASCII-7-bit Path: g2news2.google.com!news1.google.com!goblin2!goblin.stu.neva.ru!aioe.org!.POSTED!not-for-mail From: tmoran@acm.org Newsgroups: comp.lang.ada Subject: Re: procedure Make_File_Gone (Name : in String); Date: Sat, 23 Jul 2011 19:05:02 +0000 (UTC) Organization: Aioe.org NNTP Server Message-ID: References: NNTP-Posting-Host: Lf0Nl3CcQzx+ocHx9cmuGg.user.speranza.aioe.org X-Complaints-To: abuse@aioe.org X-Notice: Filtered by postfilter v. 0.8.2 X-Newsreader: Tom's custom newsreader Xref: g2news2.google.com comp.lang.ada:21299 Date: 2011-07-23T19:05:02+00:00 List-Id: > The postcondition of the two is the same -- the file isn't there. I understand a postcondition to be true just after execution of something. The postcondition for an execution of Ada_Directories.Delete_File is "(the file isn't there and a Name_Error may or may not have been raised), or a Use_Error has been raised" I want a routine where the postcondition is "the file isn't there, or a Use_Error has been raised" (In my programming a Use_Error is exceptional, but trying to ensure that a certain file no longer exists is not all that unusual.) I'm looking for a good name for such a routine, where "good" means short and clear to a maintenance programmer scanning the code. Perhaps English doesn't have a nice way of making such an imperative->declarative phrase.