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.6 required=5.0 tests=BAYES_20,INVALID_MSGID autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,f188b1cd9c1f24dc X-Google-Attributes: gid103376,public From: glee@array.ca (Glenden Lee) Subject: Re: Parameter evaluation order Date: 1998/04/08 Message-ID: #1/1 X-Deja-AN: 342090842 References: <6g9d2o$tfg$1@nnrp1.dejanews.com> Organization: Array Systems Computing Inc., Toronto, Ontario, CANADA Newsgroups: comp.lang.ada Date: 1998-04-08T00:00:00+00:00 List-Id: Mark.Rutten@dsto.defence.gov.au wrote: : I'm using GNAT3.09 on WindowsNT (and also Solaris, but I didn't get : this problem). : I compiled a procedure call similar to the following : proc(func_one,func_two); : The program relies on func_one being called _before_ func_two. But : at run-time the code above did the opposite! Is this a bug (and if so, has it : been fixed in 3.10)? Or is there something written in the language definition : to justify this behaviour? Your compiler is probably optimizing it somehow. Why don't you just break it down into several lines? It'd be easier to maintain for the next person that looks at your code also. G. -- Glenden Lee Array Systems Computing 1120 Finch Avenue West North York, Ontario