2.8 Pragmas

1. A pragma is a compiler directive. There are language-defined pragmas that give instructions for optimization, listing control, etc. An implementation may support additional (implementation-defined) pragmas.
   Syntax
   

2. pragma ::=
      pragma identifier [(pragma_argument_association
         {, pragma_argument_association})];
   

3. pragma_argument_association ::=
        [pragma_argument_identifier =>] name
      | [pragma_argument_identifier =>] expression
   

   1. In a pragma, any pragma_argument_associations without a pragma_argument_identifier shall precede any associations with a pragma_argument_identifier.
   2. Pragmas are only allowed at the following places in a program:
      1. After a semicolon delimiter, but not within a formal_part or discriminant_part.
      2. At any place where the syntax rules allow a construct defined by a syntactic category whose name ends with "declaration", "statement", "clause", or "alternative", or one of the syntactic categories variant or exception_handler; but not in place of such a construct. Also at any place where a compilation_unit would be allowed.
   1. Additional syntax rules and placement restrictions exist for specific pragmas.

1. The name of a pragma is the identifier following the reserved word pragma. The name or expression of a pragma_argument_association is a pragma argument.
2. An identifier specific to a pragma is an identifier that is used in a pragma argument with special meaning for that pragma.
   Static Semantics
   
3. If an implementation does not recognize the name of a pragma, then it has no effect on the semantics of the program. Inside such a pragma, the only rules that apply are the Syntax Rules.
   Dynamic Semantics
   
4. Any pragma that appears at the place of an executable construct is executed. Unless otherwise specified for a particular pragma, this execution consists of the evaluation of each evaluable pragma argument in an arbitrary order.
   Implementation Requirements
   
5. The implementation shall give a warning message for an unrecognized pragma name.
   Implementation Permissions
   
6. An implementation may provide implementation-defined pragmas; the name of an implementation-defined pragma shall differ from those of the language-defined pragmas.
7. An implementation may ignore an unrecognized pragma even if it violates some of the Syntax Rules, if detecting the syntax error is too complex.
   Implementation Advice
   
8. Normally, implementation-defined pragmas should have no semantic effect for error-free programs; that is, if the implementation-defined pragmas are removed from a working program, the program should still be legal, and should still have the same semantics.
9. Normally, an implementation should not define pragmas that can make an illegal program legal, except as follows:
   1. A pragma used to complete a declaration, such as a pragma Import;
   2. A pragma used to configure the environment by adding, removing, or replacing library_items.

1. The forms of List, Page, and Optimize pragmas are as follows:
2. pragma List(identifier);
3. pragma Page;
4. pragma Optimize(identifier);
   1. Other pragmas are defined throughout this International Standard, and are summarized in Annex L.

1. A pragma List takes one of the identifiers On or Off as the single argument. This pragma is allowed anywhere a pragma is allowed. It specifies that listing of the compilation is to be continued or suspended until a List pragma with the opposite argument is given within the same compilation. The pragma itself is always listed if the compiler is producing a listing.
2. A pragma Page is allowed anywhere a pragma is allowed. It specifies that the program text which follows the pragma should start on a new page (if the compiler is currently producing a listing).
3. A pragma Optimize takes one of the identifiers Time, Space, or Off as the single argument. This pragma is allowed anywhere a pragma is allowed, and it applies until the end of the immediately enclosing declarative region, or for a pragma at the place of a compilation_unit, to the end of the compilation. It gives advice to the implementation as to whether time or space is the primary optimization criterion, or that optional optimizations should be turned off. It is implementation defined how this advice is followed.
   Examples
   
4. Examples of pragmas:

5. pragma List(Off);         -- turn off listing generation
   pragma Optimize(Off);     -- turn off optional optimizations
   pragma Inline(Set_Mask);  -- generate code for Set_Mask inline
   
   pragma Suppress(Range_Check, On => Index);
   -- turn off range checking on Index
   

Go to the first, previous, next, last section, table of contents.