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.3 required=5.0 tests=BAYES_00,INVALID_MSGID
	autolearn=no autolearn_force=no version=3.4.4
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: fac41,2c6139ce13be9980
X-Google-Attributes: gidfac41,public
X-Google-Thread: 103376,3d3f20d31be1c33a
X-Google-Attributes: gid103376,public
From: dewar@merv.cs.nyu.edu (Robert Dewar)
Subject: Re: Precondition Checking For Ada 0X (Was: Separation of IF and Imp:
 process issue?)
Date: 1997/09/16
Message-ID: <dewar.874464817@merv>#1/1
X-Deja-AN: 273151230
References: <33E9ADE9.4709@flash.net>
 <mheaney-ya023680000409972313230001@news.ni.net>
 <5upe9k$7he@newshub.atmnet.net>
 <mheaney-ya023680000609971422530001@news.ni.net>
 <5utag9$o6s@newshub.atmnet.net> <3416ad14.0@news.uni-ulm.de>
 <3416D889.4A6C@pseserv3.fw.hac.com>
 <mheaney-ya023680001009971956580001@news.ni.net> <dewar.874090086@merv>
 <341D8B8D.7C9F@pseserv3.fw.hac.com>
Organization: New York University
Newsgroups: comp.lang.ada,comp.lang.eiffel
Date: 1997-09-16T00:00:00+00:00
List-Id: <comp.lang.ada>


WWG said

<<at the beginning of the body.  However, as with pragma Inline,
it would have to apply to all overloadings of "X", and if it is
allowed (as above) to reference X's parameters, there could be
a significant ambiguity in (for example) the following case:

         procedure x (a : calendar.time; b : task_ID);
         procedure x (a : integer; b : integer);
         pragma Precondition (x, a = b + 17);>>


No big deal. The conventional Ada answer is to use renamings to disambiguate,
or you could follow the lead of the DEC pragmas (as implemented in Ada,
see for example Import_Procedure), and give the corresponding profile in
the pragma.

This is no a difficult issue to resolve.