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-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,a00006d3c4735d70 X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 2004-03-01 23:08:54 PST Path: archiver1.google.com!news2.google.com!news.maxwell.syr.edu!border1.nntp.ash.giganews.com!border2.nntp.ash.giganews.com!nntp.giganews.com!elnk-atl-nf1!newsfeed.earthlink.net!bigfeed2.bellsouth.net!news.bellsouth.net!cycny01.gnilink.net!cyclone1.gnilink.net!spamkiller2.gnilink.net!nwrdny02.gnilink.net.POSTED!0e8a908a!not-for-mail From: Hyman Rosen User-Agent: Mozilla Thunderbird 0.5 (Windows/20040207) X-Accept-Language: en-us, en MIME-Version: 1.0 Newsgroups: comp.lang.ada Subject: Re: In-Out Parameters for functions References: <4020C947.81A6D703@0.0> <1075907239.138068@master.nyc.kbcfp.com> <402232E9.3EE15B4B@0.0> <1075987360.225622@master.nyc.kbcfp.com> <40236C0B.E988E003@0.0> <1077634311.254581@master.nyc.kbcfp.com> <1077718871.47635@master.nyc.kbcfp.com> <54cp3095jmv8s17h63d4bjdus0tec7l7pt@jellix.jlfencey.com> <1077721343.481619@master.nyc.kbcfp.com> <1077727853.904323@master.nyc.kbcfp.com> <1077810250.28474@master.nyc.kbcfp.com> <1078162736.111267@master.nyc.kbcfp.com> In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Message-ID: <8qW0c.24142$TF2.22229@nwrdny02.gnilink.net> Date: Tue, 02 Mar 2004 07:08:52 GMT NNTP-Posting-Host: 162.84.141.199 X-Complaints-To: abuse@verizon.net X-Trace: nwrdny02.gnilink.net 1078211332 162.84.141.199 (Tue, 02 Mar 2004 02:08:52 EST) NNTP-Posting-Date: Tue, 02 Mar 2004 02:08:52 EST Xref: archiver1.google.com comp.lang.ada:6002 Date: 2004-03-02T07:08:52+00:00 List-Id: Robert I. Eachus wrote: > So although whether the compiler does follow the advice of a pragma > Inline, it has semantic effects. The same section says "The permissions granted by this clause can have an effect on the semantics of a program only if the program fails a language-defined check." So unless you're coding in a way where you expect to cause and catch l-d checks, it won't matter. Also, if I read that section correctly, in a sequence of code like this a := 0; b := c + d; e := f + g; h := i + j; a := 1 / a; it is possible that only the assignment to a will have occurred when the exception handler from the division by zero is executed, is that correct? Doesn't that make catching failures of language-defined checks useless? You will know that something bad happened, but you won't know which objects in your program are abnormal.