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.8 required=5.0 tests=BAYES_00,INVALID_DATE autolearn=no autolearn_force=no version=3.4.4 Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!linus!philabs!cmcl2!harvard!husc6!panda!genrad!decvax!ima!inmet!ada-uts!stt From: stt@ada-uts Newsgroups: net.lang.ada Subject: Re: Can CALENDAR.CLOCK be called during Message-ID: <4700028@ada-uts> Date: Wed, 14-May-86 11:18:00 EDT Article-I.D.: ada-uts.4700028 Posted: Wed May 14 11:18:00 1986 Date-Received: Fri, 16-May-86 04:18:40 EDT References: <247@anasazi.UUCP> Nf-ID: #R:anasazi.UUCP:247:ada-uts:4700028:000:745 Nf-From: ada-uts!stt May 14 11:18:00 1986 List-Id: You have run into the basic flaw with Pragma ELABORATE. Its usefulness is severely limited given its current semantics. It would be much more useful if a pragma ELABORATE of a unit implied a pragma ELABORATE of all of the units its body "with"s. Ada '88? Nevertheless, most compilers implement "friendly" elaboration order so you won't necessarily run into the problems. It turns out that the ACVC's made the same assumption, that pragma elaborating package Report was sufficient to avoid PROGRAM_ERROR. In fact, Report "with"s Text-IO, so it is quite possible that a call on Report during elaboration will die somewhere in Text-IO with PROGRAM_ERROR. The newest ACVC suite includes a pragma ELABORATE(Text_IO); on the report package body.