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 autolearn=ham autolearn_force=no version=3.4.4 X-Google-Thread: 103376,23dabf88feae3dba X-Google-Attributes: gid103376,public X-Google-Language: ENGLISH,ASCII-7-bit Path: g2news2.google.com!news3.google.com!border1.nntp.dca.giganews.com!nntp.giganews.com!bcklog1.nntp.dca.giganews.com!nntp.megapath.net!news.megapath.net.POSTED!not-for-mail NNTP-Posting-Date: Thu, 22 Jun 2006 18:05:16 -0500 From: "Randy Brukardt" Newsgroups: comp.lang.ada References: <4fssh9F1ena5jU1@individual.net> <8KOdnYaLZJaLMATZnZ2dnUVZ_tydnZ2d@megapath.net> <87odwmcdku.fsf@willow.rfc1149.net> Subject: Re: Elaboration worries Date: Thu, 22 Jun 2006 18:06:02 -0500 X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 6.00.2800.1807 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1807 Message-ID: NNTP-Posting-Host: 64.32.209.38 X-Trace: sv3-Y97BVdLwdOix1pYfYq0/e+ZiOyRMIl9tw8heg1UHxf5FAgxcVmYoViCPnX3hA4FgGsb8EfMTw1up/Aa!KUe05aDZZfM4WsuaoWXLb7H/LabmeScASq3ZfMDSmJNoC2tqiR1IdmsatuB3VSbX7FEOvqv6mupJ!a0Mm6nIPlAENaQ== X-Complaints-To: abuse@megapath.net X-DMCA-Complaints-To: abuse@megapath.net X-Abuse-and-DMCA-Info: Please be sure to forward a copy of ALL headers X-Abuse-and-DMCA-Info: Otherwise we will be unable to process your complaint properly X-Postfilter: 1.3.32 Xref: g2news2.google.com comp.lang.ada:4910 Date: 2006-06-22T18:06:02-05:00 List-Id: "Samuel Tardieu" wrote in message news:87odwmcdku.fsf@willow.rfc1149.net... > >>>>> "Randy" == Randy Brukardt writes: > > Randy> try to avoid doing anything at elaboration time other than > Randy> use language-defined packages; > > There are cases where this is quite impractical; for example, when > using the Ravenscar profile, tasks cannot be created dynamically and > will be started at elaboration time. Using a "start" protected object > can be used as a workaround to limit their execution until after the > main program has been launched. Which is why I said "try to avoid", not just "avoid". It's hard to avoid library-level generic instantiations, for instance. OTOH, I was under the impression that most Ravenscar programs used what is now known as the "Concurrent" elaboration policy (see H.6 in the Ada 2005 RM). That prevents tasks from being started until elaboration of library units is finished. So the problem is less that you have to do things at elaboration time in Ravenscar, and more that Ravenscar is incompatible with the traditional Ada elaboration model. Randy.