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: 103376,16e3a8dd4f3ab3f3 X-Google-Attributes: gid103376,public From: dewar@cs.nyu.edu (Robert Dewar) Subject: Re: Elaboration order Date: 1996/03/18 Message-ID: #1/1 X-Deja-AN: 143066911 references: <314701A1.469D@lfwc.lockheed.com> <31494143.3825@lfwc.lockheed.com> organization: Courant Institute of Mathematical Sciences newsgroups: comp.lang.ada Date: 1996-03-18T00:00:00+00:00 List-Id: " More important, it is possible to write a legal (Ada 83 and 95) program which reads input from a file, command line, or even a terminal, before the main program is called. If you work at it (exercise left to the reader) it is possible to write the program so that there are two different interesting and legal elaboration orders, and inputs that cause Program_Error with one elaboration order excute successfully with the other. Of course, for toy examples, there is an equivalent program which doesn't raise Program_Error. But for embedded applications, it can be the case that various peripherals have to be brought on line in sequence and with fairly tight timing requirements." This sounds VERY bogus, I would NEVER do this kind of initialization at elaboration time -- this is NOT what elaboratoin is intended for, but rather, in my book, a gross misuse of the concept!