Re: Why can't objects be static in Ada?

[Simon Wright <simon@pushface.org>]

Mark Lorenzen <mark.lorenzen@gmail.com> writes:

> On Friday, April 12, 2019 at 12:49:07 AM UTC+2, Randy Brukardt wrote:
>> 
>> fix this. There's no good reason (outside of Annex E issues) for
>> declaring any package preelaborated, unless you like fighting errors
>> a lot. C.4 is a load of hooey, it's not actually implementable on the
>> margins, and there's no reason for any compiler to generate more code
>> than necessary. Ergo, you'll most likely get the same code whether or
>> not you declare something Preelaborated, so why bother with all of
>> the hassles?
>
> For certification purposes, I think there is a value in avoiding
> elaboration code.
>
> http://docs.adacore.com/live/wave/gnat_ugx/html/gnat_ugx/gnat_ugx/support_for_certified_systems.html#avoiding-elaboration-code

This is the GNAT-specific No_Elaboration_Code restriction (and pragma
No_Elaboration_Code_All[1]) which I had to apply to the units involved
in setting up the MCU and arranging to run the compiler-generated
elaboration sequence.

[1]: This is a program unit pragma (there is also an equivalent aspect
of the same name) that establishes the restriction No_Elaboration_Code
for the current unit and any extended main source units (body and
subunits). It also has the effect of enforcing a transitive application
of this aspect, so that if any unit is implicitly or explicitly with’ed
by the current unit, it must also have the No_Elaboration_Code_All
aspect set. It may be applied to package or subprogram specs or their
generic versions.