VMS Help
ADA, Positional Qualifiers

 *Conan The Librarian

1 - /ANALYSIS_DATA

    /ANALYSIS_DATA[=file-spec]
    /NOANALYSIS_DATA (D)

    Controls whether a data analysis file containing source code
    cross-reference and static analysis information is created. The
    data analysis file is supported only for use with Digital layered
    products, such as the DEC Source Code Analyzer.

    One data analysis file is created for each source file that is
    compiled. The default directory for data analysis files is the
    current default directory. The default file name is the name of
    the source file being compiled. The default file type is .ANA. No
    wildcard characters are allowed in the file specification.

    By default, no data analysis file is created.

2 - /ARCHITECTURE

    Controls the use of new Alpha instructions.
    The syntax for this switch is as follows:

    /ARCHITECTURE = { GENERIC | HOST | EV4 | EV5 | EV56 }

    Setting the /ARCH switch causes a corresponding setting in the /TUNE
    switch.  (See the Release Notes for more information.)

3 - /CHECK

    /CHECK
    /NOCHECK

    Controls whether all run-time checks are suppressed. The /NOCHECK
    qualifier is equivalent to having all possible SUPPRESS pragmas
    in the source code.

    Explicit use of the /CHECK qualifier overrides any occurrences of
    the pragmas SUPPRESS and SUPPRESS_ALL in the source code, without
    the need to edit the source code.

    By default, run-time checks are suppressed only in cases where a
    pragma SUPPRESS or SUPPRESS_ALL appears in the source code.

    See the DEC Ada Language Reference Manual for more information on
    the pragmas SUPPRESS and SUPPRESS_ALL.

4 - /COPY_SOURCE

    /COPY_SOURCE (D)
    /NOCOPY_SOURCE

    Controls whether a copied source file is created in the current
    program library when a compilation unit is compiled without
    error. The ACS RECOMPILE command requires that a copied source
    file exist in the current program library; the ACS COMPILE
    command uses the copied source file if it cannot find an external
    source file when it is recompiling an obsolete unit or completing
    an incomplete generic instantiation (see Developing Ada Programs
    on OpenVMS Systems). Copied source files may also be used by
    the OpenVMS Debugger (see the Developing Ada Programs on OpenVMS
    Systems for more information on debugging tasks; and the OpenVMS
    Debugger Manual for more information on the debugger).

    By default, a copied source file is created in the current
    program library when a unit is compiled without error.

5 - /DEBUG

    /DEBUG[=(option[,...])] (D)
    /NODEBUG

    Controls which compiler debugging options are provided. You
    can debug Compaq Ada programs with the OpenVMS Debugger (see the
    Developing Ada Programs on OpenVMS Systems for more information
    on debugging Ada tasks; and the OpenVMS Debugger Manual for more
    information on the OpenVMS debugger.

    You can request the following options:

    ALL            Provides both SYMBOLS and TRACEBACK.
    NONE           Provides neither SYMBOLS nor TRACEBACK.
    [NO]SYMBOLS    Controls whether debugger symbol records are
                   included in the object file.
    [NO]TRACEBACK  Controls whether traceback information (a subset
                   of the debugger symbol information) is included in
                   the object file.

    By default, both debugger symbol records and traceback
    information are included in the object file (/DEBUG=ALL, or
    equivalently: /DEBUG).

6 - /DESIGN

    /DESIGN[=option]
    /NODESIGN (D)

    Allows you to process Ada source files as a detailed program
    design. For each unit that is design checked without error, the
    program library is updated with information about that unit.
    Design-checked units are considered to be obsolete in operations
    that require full compilation and must be recompiled.

    You can request the following options:

    [NO]COMMENTS       Determines whether comments are processed for
                       program design information. For the COMMENTS
                       option to have effect, you must specify
                       the /ANALYSIS_DATA qualifier. See Guide to
                       Source Code Analyzer for VMS Systems for more
                       information on using the Source Code Analyzer
                       (SCA).

                       If you specify NOCOMMENTS, comments are
                       ignored.

    [NO]PLACEHOLDERS   Determines whether design checking is
                       performed. If you specify PLACEHOLDERS,
                       compilation units are design checked-LSE
                       placeholders are allowed and some of the
                       Ada language rules are relaxed so that you
                       can omit some implementation details. If you
                       specify NOPLACEHOLDERS, full compilation is
                       done-the compiler is invoked, LSE placeholders
                       are not allowed, and Ada language rules are
                       not relaxed.

                       Note that when you specify this option with
                       the /SYNTAX_ONLY qualifier, it determines only
                       whether LSE placeholders are allowed. If you
                       specify NOPLACEHOLDERS, then only valid Ada
                       syntax is allowed.

    If you specify the /DESIGN qualifier without supplying any
    options, the effect is the same as the following default:

    /DESIGN=(COMMENTS,PLACEHOLDERS)

    If you specify only one of the options with the /DESIGN
    qualifier, the default value for the other option is
    used. For example, /DESIGN=NOCOMMENTS is equivalent to
    /DESIGN=(NOCOMMENTS,PLACEHOLDERS). In this case, both qualifiers
    specify that the unit is design-checked, but comment information
    is not collected. Similarly, /DESIGN=NOPLACEHOLDERS is equivalent
    to /DESIGN=(COMMENTS,NOPLACEHOLDERS). In this case, both
    qualifiers specify that comment information is collected, but
    the unit is not design-checked (that is, in the absence of the
    /SYNTAX_ONLY qualifier, units are fully compiled).

7 - /DIAGNOSTICS

    /DIAGNOSTICS[=file-spec]
    /NODIAGNOSTICS (D)

    Controls whether a diagnostics file containing compiler messages
    and diagnostic information is created. The diagnostics file is
    supported only for use with Digital layered products, such as the
    DEC Language-Sensitive Editor.

    One diagnostics file is created for each source file that is
    compiled. The default directory for diagnostics files is the
    current default directory. The default file name is the name of
    the source file being compiled. The default file type is .DIA. No
    wildcard characters are allowed in the file specification.

    By default, no diagnostics file is created.

8 - /ERROR_LIMIT

    /ERROR_LIMIT[=n] (D)
    /NOERROR_LIMIT

    Controls whether execution of the ADA command for a given
    compilation unit is terminated upon the occurrence of the nth
    E-level error within that unit.

    Error counts are not accumulated across a sequence of compilation
    units. If the /ERROR_LIMIT=n option is specified, each
    compilation unit may have up to n - 1 errors without terminating
    the compilation. When the error limit is reached within a
    compilation unit, compilation of that unit is terminated, but
    compilation of subsequent units continues.

    The /ERROR_LIMIT=0 option is equivalent to ERROR_LIMIT=1.

    By default, execution of the ADA command is terminated for a
    given compilation unit upon the occurrence of the 30th E-level
    error within that unit (equivalent to /ERROR_LIMIT=30).

9 - /EXPORT_INTERFACE

    /EXPORT_INTERFACE=ADA  (D)
    /EXPORT_INTERFACE=FORTRAN
    /EXPORT_INTERFACE=DEFAULT

    This qualifier sets the passing mechanism chosen for string parameters
    for exported subprograms unless an export pragma specifically specifies
    the passing mechanism.

    The default is ADA, which uses dope vectors for the passing mechanism.

    FORTRAN or DEFAULT will use VAX descriptors for the passing mechanism.

    For more information, please see the Compaq Ada release notes.

10 - /LIST

    /LIST[=file-spec]
    /NOLIST (D)

    Controls whether a listing file is created. One listing file is
    created for each source file compiled. The default directory for
    listing files is the current default directory. The default file
    name is the name of the source file being compiled. The default
    file type is .LIS. No wildcard characters are allowed in the file
    specification.

    By default, the ADA command does not create a listing file.

11 - /LOAD

    /LOAD[= option] (D)
    /NOLOAD

    Controls whether the current program library is updated with the
    successfully processed units contained in the specified source
    files. Depending on other qualifiers specified (or not specified)
    with the ADA command, processing can involve full compilation,
    syntax checking only, and so on. The /NOLOAD qualifier causes the
    units in the specified source files to be processed, but prevents
    the current program library from being updated. For example, this
    effect allows you to obtain a machine code listing for a unit
    that has already been compiled into the program library without
    affecting the library.

    You can specify the following option:

    [NO]REPLACE   Controls whether a unit added to the current
                  program library replaces an existing unit with the
                  same name. If you specify the NOREPLACE option, the
                  unit will be added to the current program library
                  only if no existing unit has the same name, except
                  if the new unit is the missing body of an existing
                  specification, or vice versa.

    By default, the current program library is updated with the
    successfully processed units, and a unit added to the current
    program library will replace an existing unit with the same name
    (/LOAD=REPLACE).

12 - /MACHINE_CODE

    /MACHINE_CODE
    /NOMACHINE_CODE (D)

    Controls whether generated machine code (approximating assembler
    notation) is included in the listing file.

    By default, generated machine code is not included in the listing
    file.

13 - /NOTE_SOURCE

    /NOTE_SOURCE (D)
    /NONOTE_SOURCE

    Controls whether the file specification of the source file is
    noted in the program library when a unit is compiled without
    error. The ACS COMPILE command uses this information to locate
    revised source files.

    By default, the file specification of the source file is noted in
    the program library when a unit is compiled without error.

14 - /OPTIMIZE

    /OPTIMIZE[=(option,...])]
    /NOOPTIMIZE

    Controls the level of optimization that is applied in producing
    the compiled code. You can specify one of the following primary
    options:

    TIME          Provides full optimization with time as the primary
                  optimization criterion. Overrides any occurrences
                  of the pragma OPTIMIZE(SPACE) in the source code.
    SPACE         Provides full optimization with space as the
                  primary optimization criterion. Overrides any
                  occurrences of the pragma OPTIMIZE(TIME) in the
                  source code.
    DEVELOPMENT   Suggested when active development of a program
                  is in progress. Provides some optimization, but
                  development considerations and ease of debugging
                  take preference over optimization. This option
                  overrides pragmas that establish a dependence on
                  a subprogram or generic body (the pragmas INLINE
                  and INLINE_GENERIC), and therefore reduces the need for
                  recompilations when such bodies are modified. This
                  option also disables generic code sharing.
    NONE          Provides no optimization. Suppresses inline
                  expansions of subprograms and generics, including
                  those specified by the pragmas INLINE and INLINE_
                  GENERIC. Suppresses occurrences of the pragma
                  SHARE_GENERIC and disables generic code sharing.

    The /NOOPTIMIZE qualifier is equivalent to /OPTIMIZE=NONE.

    By default, the ADA command applies full optimization with time
    as the primary optimization criterion (like /OPTIMIZE=TIME, but
    observing uses of the pragma OPTIMIZE).

    The /OPTIMIZE qualifier also has a set of secondary options that
    you can use separately or together with the primary options to
    override the default behavior for inline expansion (generic and
    subprogram) and generic code sharing.

    The INLINE secondary option can have the following values (see
    the DEC Ada Run-Time Reference Manual for OpenVMS Systems for
    more information about inline expansion):

    NONE             Disables subprogram and generic inline
                     expansion. This option overrides any occurrences
                     of the pragmas INLINE or INLINE_GENERIC in the
                     source code, without your having to edit the
                     source file. It also disables implicit inline
                     expansion of subprograms. (Implicit inline
                     expansion means that the compiler assumes a
                     pragma INLINE for certain subprograms as an
                     optimization.) A call to a subprogram or an
                     instance of a generic in another unit is not
                     expanded inline, regardless of the /OPTIMIZE
                     options in effect when that unit was compiled.
    NORMAL           Provides normal subprogram and generic inline
                     expansion.

                     Subprograms to which an explicit pragma INLINE
                     applies are expanded inline under certain
                     conditions. In addition, some subprograms are
                     implicitly expanded inline. The compiler assumes
                     a pragma INLINE for calls to some small local
                     subprograms (subprograms that are declared in
                     the same unit as the unit in which the call
                     occurs).

                     Instances are compiled separately from the unit
                     in which the instantiation occurred unless a
                     pragma INLINE_GENERIC applies to the instance.
                     If a pragma INLINE_GENERIC applies and the
                     generic body has been compiled, the generic is
                     expanded inline at the point of instantiation.
    SUBPROGRAMS      Provides maximal subprogram inline expansion and
                     normal generic inline expansion.

                     In addition to the normal subprogram inline
                     expansion that occurs when INLINE:NORMAL is
                     specified, this option results in implicit
                     inline expansion of some small subprograms
                     declared in other units. The compiler assumes a
                     pragma INLINE for any subprogram if it improves
                     execution speed and reduces code size. This
                     option may establish a dependence on the body of
                     another unit, as would be the case if a pragma
                     INLINE were specified explicitly in the source
                     code.

                     With this option, generic inline expansion
                     occurs in the same manner as for INLINE:NORMAL.
    GENERICS         Provides normal subprogram inline expansion and
                     maximal generic inline expansion.

                     With this option, subprogram inline expansion
                     occurs in the same manner as for INLINE:NORMAL.

                     The compiler assumes a pragma INLINE_GENERIC for
                     every instantiation in the unit being compiled
                     unless an explicit pragma SHARE_GENERIC applies.
                     This option may establish a dependence on the
                     body of another unit, as would be the case if a
                     pragma INLINE_GENERIC were specified explicitly
                     in the source code.
    MAXIMAL          Provides maximal subprogram and generic inline
                     expansion.

                     Maximal subprogram inline expansion occurs as
                     for INLINE:SUBPROGRAMS, and maximal generic
                     inline expansion occurs as for INLINE:GENERICS.

    The SHARE secondary option can have the following values:

    NONE          Disables generic sharing. This option overrides
                  the effect of any occurrences of the pragma SHARE_
                  GENERIC in the source code, without your having to
                  edit the source file. In addition, instances do not
                  share code from previous instantiations.
    NORMAL        Provides normal generic sharing. Normally, the
                  compiler will not attempt to generate sharable
                  code for an instance (code that can be shared
                  by subsequent instantiations) unless an explicit
                  pragma SHARE_GENERIC applies to that instance.
                  However, an instance will attempt to share code
                  that resulted from a previous instantiation to
                  which the pragma SHARE_GENERIC applied.
    MAXIMAL       Provides maximal generic sharing. The compiler
                  assumes that a pragma SHARE_GENERIC applies to
                  every instance in the unit being compiled unless
                  an explicit pragma INLINE_GENERIC applies. Therefore, an
                  instance will attempt to share code that resulted
                  from a previous instantiation or to generate code
                  that can be shared by subsequent instantiations.

                  SHARE:MAXIMAL cannot be used in combination with
                  INLINE:GENERICS or INLINE:MAXIMAL.

    By default, if you specify one of the /OPTIMIZE
    qualifier primary options on the left (for example,
    /OPTIMIZE=TIME), it has the same effect as specifying
    the secondary-option values to the right (in this case,
    /OPTIMIZE=(TIME,INLINE:NORMAL,SHARE:NORMAL)):

    TIME        /OPTIMIZE=(TIME,INLINE:NORMAL,SHARE:NORMAL)
    SPACE       /OPTIMIZE=(SPACE,INLINE:NORMAL,SHARE:NORMAL)
    DEVELOPMENT /OPTIMIZE=(DEVELOPMENT,INLINE:NONE,SHARE:NONE)
    NONE        /OPTIMIZE=(NONE,INLINE:NONE,SHARE:NONE)

    See Developing Ada Programs on OpenVMS Systems for more
    information on the /OPTIMIZE qualifier and its options.

15 - /SHOW

    /SHOW[=option] (D)
    /NOSHOW

    Controls the listing file options included when a listing file is
    provided. You can specify one of the following options:

    ALL            Provides all listing file options.
    [NO]PORTABILITYControls whether a program portability summary is
                   included in the listing file (see Developing Ada
                   Programs on OpenVMS Systems).
    NONE           Provides none of the listing file options (same as
                   /NOSHOW).

    By default, the ADA command provides a portability summary
    (/SHOW=PORTABILITY).

16 - /SMART_RECOMPILATION

    /SMART_RECOMPILATION (D)
    /NOSMART_RECOMPILATION

    Controls whether smart recompilation information is stored and
    used to minimize unnecessary recompilations.

    When the /SMART_RECOMPILATION qualifier is in effect, detailed
    information about dependences is stored in the program
    library for each unit compiled. This information describes the
    dependences of a unit at a finer level than the compilation unit
    level.

    If smart recompilation is not in effect, detailed information
    about dependences is not stored in the program library. (See
    Developing Ada Programs on OpenVMS Systems for more information.)

17 - /SYNTAX_ONLY

    /SYNTAX_ONLY
    /NOSYNTAX_ONLY (D)

    Controls whether the source file is to be checked only for
    correct syntax. If you specify the /SYNTAX_ONLY qualifier,
    other compiler checks are not performed (for example, semantic
    analysis, type checking, and so on).

    In the presence of the /LOAD=REPLACE qualifier (the default),
    the /SYNTAX_ONLY qualifier updates the current program library
    with syntax-checked-only units. The units are considered to be
    obsolete and must be subsequently recompiled.

    In the presence of the /NOLOAD qualifier, the /SYNTAX_ONLY
    qualifier checks the syntax of the specified units but does not
    update the library.

    By default, the compiler performs all compiler checks.

18 - /TUNE

    Selects processor-specific instruction tuning for implementations of
    the Alpha architecture.  Tuning for a specific implementation can
    provide improvements in runtime performance.  The syntax for this switch
    is as follows:

    /TUNE = { GENERIC | HOST | EV4 | EV5 | EV56 }

    For more information, see the Release Notes.

19 - /WARNINGS

    /WARNINGS[=(option[,...])]
    /NOWARNINGS

    Controls which categories of informational (I-level) and warning
    (W-level) messages are displayed and where those messages are
    displayed. You can specify any combination of the following
    message options:

       WARNINGS: (destination[,...])
       NOWARNINGS

       WEAK_WARNINGS: (destination[,...])
       NOWEAK_WARNINGS

       SUPPLEMENTAL: (destination[,...])
       NOSUPPLEMENTAL

       COMPILATION_NOTES: (destination[,...])
       NOCOMPILATION_NOTES

       STATUS: (destination[,...])
       NOSTATUS

    The possible values of destination are ALL, NONE, or any
    combination of TERMINAL (terminal device), LISTING (listing
    file), and DIAGNOSTICS (diagnostics file). The message categories
    are summarized as follows (See the Developing Ada Programs on
    OpenVMS Systems for more information):

    WARNINGS         W-level: Indicates a definite problem in a legal
                     program-for example, an unknown pragma.
    WEAK_WARNINGS    I-level: Indicates a potential problem in
                     a legal program-for example, a possible
                     CONSTRAINT_ERROR at run time. These are the only
                     kind of I-level messages that are counted in the
                     summary statistics at the end of a compilation.
    SUPPLEMENTAL     I-level: Additional information associated with
                     previous E-level or W-level diagnostics.
    COMPILATION_     I-level: Information about how the compiler
    NOTES            translated a program, such as record layout,
                     parameter-passing mechanisms, or decisions
                     made for the pragmas INLINE, INTERFACE, or the
                     import-subprogram pragmas.
    STATUS           I-level: End-of-compilation statistics and other
                     messages.

    The defaults are as follows:

    /WARNINGS=(WARN:ALL,WEAK:ALL,SUPP:ALL,COMP:NONE,STAT:LIST)

    If you specify only some of the message categories with the
    /WARNINGS qualifier, the default values for other categories are
    used.
  Close     Help