@@ -2472,7 +2472,9 @@ Syntax:
This is a configuration pragma
that takes a single argument that is a simple identifier. Any subsequent
use of a pragma whose pragma identifier matches this argument will be
-silently ignored. This may be useful when legacy code or code intended
+silently ignored. Any preceding use of a pragma whose pragma identifier
+matches this argument will be parsed and then ignored.
+This may be useful when legacy code or code intended
for compilation with some other compiler contains pragmas that match the
name, but not the exact implementation, of a GNAT pragma. The use of this
pragma allows such pragmas to be ignored, which may be useful in CodePeer
@@ -185,6 +185,11 @@ package body Errout is
-- Outputs up to N levels of qualification for the given entity. For
-- example, the entity A.B.C.D will output B.C. if N = 2.
+ function Should_Ignore_Pragma_SPARK_Mode return Boolean;
+ -- Return whether pragma Ignore_Pragma (SPARK_Mode) was specified. This is
+ -- similar to Sem_Util.Should_Ignore_Pragma_Par but located here to avoid
+ -- problematic dependency on Sem_Util.
+
function Special_Msg_Delete
(Msg : String;
N : Node_Or_Entity_Id;
@@ -4459,6 +4464,15 @@ package body Errout is
end if;
end Set_Qualification;
+ -------------------------------------
+ -- Should_Ignore_Pragma_SPARK_Mode --
+ -------------------------------------
+
+ function Should_Ignore_Pragma_SPARK_Mode return Boolean is
+ begin
+ return Get_Name_Table_Boolean3 (Name_SPARK_Mode);
+ end Should_Ignore_Pragma_SPARK_Mode;
+
------------------------
-- Special_Msg_Delete --
------------------------
@@ -4522,7 +4536,14 @@ package body Errout is
procedure SPARK_Msg_N (Msg : String; N : Node_Or_Entity_Id) is
begin
- if SPARK_Mode /= Off then
+ -- If SPARK_Mode is Off, we do not report SPARK legality errors to give
+ -- the flexibility to opt out of SPARK checking completely. We do the
+ -- same if pragma Ignore_Pragma (SPARK_Mode) was specified, as a way
+ -- for tools to ignore SPARK checking even on SPARK code.
+
+ if SPARK_Mode /= Off
+ and then not Should_Ignore_Pragma_SPARK_Mode
+ then
Error_Msg_N (Msg, N);
end if;
end SPARK_Msg_N;
@@ -4537,7 +4558,9 @@ package body Errout is
E : Node_Or_Entity_Id)
is
begin
- if SPARK_Mode /= Off then
+ if SPARK_Mode /= Off
+ and then not Should_Ignore_Pragma_SPARK_Mode
+ then
Error_Msg_NE (Msg, N, E);
end if;
end SPARK_Msg_NE;
@@ -3,7 +3,7 @@
@setfilename gnat-style.info
@documentencoding UTF-8
@ifinfo
-@*Generated by Sphinx 5.3.0.@*
+@*Generated by Sphinx 4.3.2.@*
@end ifinfo
@settitle GNAT Coding Style A Guide for GNAT Developers
@defindex ge
@@ -15,11 +15,13 @@
* gnat-style: (gnat-style.info). gnat-style
@end direntry
+@definfoenclose strong,`,'
+@definfoenclose emph,`,'
@c %**end of header
@copying
@quotation
-GNAT Coding Style: A Guide for GNAT Developers , Oct 26, 2023
+GNAT Coding Style: A Guide for GNAT Developers , Dec 14, 2023
AdaCore
@@ -253,7 +255,7 @@ When declarations are commented with ‘hanging’ comments, i.e.
comments after the declaration, there is no blank line before the
comment, and if it is absolutely necessary to have blank lines within
the comments, e.g. to make paragraph separations within a single comment,
-these blank lines `do' have a @code{--} (unlike the
+these blank lines @emph{do} have a @code{--} (unlike the
normal rule, which is to use entirely blank lines for separating
comment paragraphs). The comment starts at same level of indentation
as code it is commenting.
@@ -302,12 +304,12 @@ Other_Id := 6; -- Second comment
@end example
@item
-Short comments that fit on a single line are `not' ended with a
+Short comments that fit on a single line are @emph{not} ended with a
period. Comments taking more than a line are punctuated in the normal
manner.
@item
-Comments should focus on `why' instead of `what'.
+Comments should focus on @emph{why} instead of @emph{what}.
Descriptions of what subprograms do go with the specification.
@item
@@ -317,7 +319,7 @@ depend on the names of things. The names are supplementary, not
sufficient, as comments.
@item
-`Do not' put two spaces after periods in comments.
+@emph{Do not} put two spaces after periods in comments.
@end itemize
@node Declarations and Types,Expressions and Names,Lexical Elements,Top
@@ -956,7 +958,7 @@ Copyright 2000, 2001, 2002, 2007, 2008 Free Software Foundation, Inc
Everyone is permitted to copy and distribute verbatim copies of this
license document, but changing it is not allowed.
-`Preamble'
+@strong{Preamble}
The purpose of this License is to make a manual, textbook, or other
functional and useful document “free” in the sense of freedom: to
@@ -979,23 +981,23 @@ it can be used for any textual work, regardless of subject matter or
whether it is published as a printed book. We recommend this License
principally for works whose purpose is instruction or reference.
-`1. APPLICABILITY AND DEFINITIONS'
+@strong{1. APPLICABILITY AND DEFINITIONS}
This License applies to any manual or other work, in any medium, that
contains a notice placed by the copyright holder saying it can be
distributed under the terms of this License. Such a notice grants a
world-wide, royalty-free license, unlimited in duration, to use that
-work under the conditions stated herein. The `Document', below,
+work under the conditions stated herein. The @strong{Document}, below,
refers to any such manual or work. Any member of the public is a
-licensee, and is addressed as “`you'”. You accept the license if you
+licensee, and is addressed as “@strong{you}”. You accept the license if you
copy, modify or distribute the work in a way requiring permission
under copyright law.
-A “`Modified Version'” of the Document means any work containing the
+A “@strong{Modified Version}” of the Document means any work containing the
Document or a portion of it, either copied verbatim, or with
modifications and/or translated into another language.
-A “`Secondary Section'” is a named appendix or a front-matter section of
+A “@strong{Secondary Section}” is a named appendix or a front-matter section of
the Document that deals exclusively with the relationship of the
publishers or authors of the Document to the Document’s overall subject
(or to related matters) and contains nothing that could fall directly
@@ -1006,7 +1008,7 @@ connection with the subject or with related matters, or of legal,
commercial, philosophical, ethical or political position regarding
them.
-The “`Invariant Sections'” are certain Secondary Sections whose titles
+The “@strong{Invariant Sections}” are certain Secondary Sections whose titles
are designated, as being those of Invariant Sections, in the notice
that says that the Document is released under this License. If a
section does not fit the above definition of Secondary then it is not
@@ -1014,12 +1016,12 @@ allowed to be designated as Invariant. The Document may contain zero
Invariant Sections. If the Document does not identify any Invariant
Sections then there are none.
-The “`Cover Texts'” are certain short passages of text that are listed,
+The “@strong{Cover Texts}” are certain short passages of text that are listed,
as Front-Cover Texts or Back-Cover Texts, in the notice that says that
the Document is released under this License. A Front-Cover Text may
be at most 5 words, and a Back-Cover Text may be at most 25 words.
-A “`Transparent'” copy of the Document means a machine-readable copy,
+A “@strong{Transparent}” copy of the Document means a machine-readable copy,
represented in a format whose specification is available to the
general public, that is suitable for revising the document
straightforwardly with generic text editors or (for images composed of
@@ -1030,7 +1032,7 @@ to text formatters. A copy made in an otherwise Transparent file
format whose markup, or absence of markup, has been arranged to thwart
or discourage subsequent modification by readers is not Transparent.
An image format is not Transparent if used for any substantial amount
-of text. A copy that is not “Transparent” is called `Opaque'.
+of text. A copy that is not “Transparent” is called @strong{Opaque}.
Examples of suitable formats for Transparent copies include plain
ASCII without markup, Texinfo input format, LaTeX input format, SGML
@@ -1043,22 +1045,22 @@ processing tools are not generally available, and the
machine-generated HTML, PostScript or PDF produced by some word
processors for output purposes only.
-The “`Title Page'” means, for a printed book, the title page itself,
+The “@strong{Title Page}” means, for a printed book, the title page itself,
plus such following pages as are needed to hold, legibly, the material
this License requires to appear in the title page. For works in
formats which do not have any title page as such, “Title Page” means
the text near the most prominent appearance of the work’s title,
preceding the beginning of the body of the text.
-The “`publisher'” means any person or entity that distributes
+The “@strong{publisher}” means any person or entity that distributes
copies of the Document to the public.
-A section “`Entitled XYZ'” means a named subunit of the Document whose
+A section “@strong{Entitled XYZ}” means a named subunit of the Document whose
title either is precisely XYZ or contains XYZ in parentheses following
text that translates XYZ in another language. (Here XYZ stands for a
-specific section name mentioned below, such as “`Acknowledgements'”,
-“`Dedications'”, “`Endorsements'”, or “`History'”.)
-To “`Preserve the Title'”
+specific section name mentioned below, such as “@strong{Acknowledgements}”,
+“@strong{Dedications}”, “@strong{Endorsements}”, or “@strong{History}”.)
+To “@strong{Preserve the Title}”
of such a section when you modify the Document means that it remains a
section “Entitled XYZ” according to this definition.
@@ -1069,7 +1071,7 @@ License, but only as regards disclaiming warranties: any other
implication that these Warranty Disclaimers may have is void and has
no effect on the meaning of this License.
-`2. VERBATIM COPYING'
+@strong{2. VERBATIM COPYING}
You may copy and distribute the Document in any medium, either
commercially or noncommercially, provided that this License, the
@@ -1084,7 +1086,7 @@ number of copies you must also follow the conditions in section 3.
You may also lend copies, under the same conditions stated above, and
you may publicly display copies.
-`3. COPYING IN QUANTITY'
+@strong{3. COPYING IN QUANTITY}
If you publish printed copies (or copies in media that commonly have
printed covers) of the Document, numbering more than 100, and the
@@ -1121,7 +1123,7 @@ It is requested, but not required, that you contact the authors of the
Document well before redistributing any large number of copies, to give
them a chance to provide you with an updated version of the Document.
-`4. MODIFICATIONS'
+@strong{4. MODIFICATIONS}
You may copy and distribute a Modified Version of the Document under
the conditions of sections 2 and 3 above, provided that you release
@@ -1238,7 +1240,7 @@ The author(s) and publisher(s) of the Document do not by this License
give permission to use their names for publicity for or to assert or
imply endorsement of any Modified Version.
-`5. COMBINING DOCUMENTS'
+@strong{5. COMBINING DOCUMENTS}
You may combine the Document with other documents released under this
License, under the terms defined in section 4 above for modified
@@ -1262,7 +1264,7 @@ in the various original documents, forming one section Entitled
and any sections Entitled “Dedications”. You must delete all sections
Entitled “Endorsements”.
-`6. COLLECTIONS OF DOCUMENTS'
+@strong{6. COLLECTIONS OF DOCUMENTS}
You may make a collection consisting of the Document and other documents
released under this License, and replace the individual copies of this
@@ -1275,7 +1277,7 @@ it individually under this License, provided you insert a copy of this
License into the extracted document, and follow this License in all
other respects regarding verbatim copying of that document.
-`7. AGGREGATION WITH INDEPENDENT WORKS'
+@strong{7. AGGREGATION WITH INDEPENDENT WORKS}
A compilation of the Document or its derivatives with other separate
and independent documents or works, in or on a volume of a storage or
@@ -1294,7 +1296,7 @@ electronic equivalent of covers if the Document is in electronic form.
Otherwise they must appear on printed covers that bracket the whole
aggregate.
-`8. TRANSLATION'
+@strong{8. TRANSLATION}
Translation is considered a kind of modification, so you may
distribute translations of the Document under the terms of section 4.
@@ -1314,7 +1316,7 @@ If a section in the Document is Entitled “Acknowledgements”,
its Title (section 1) will typically require changing the actual
title.
-`9. TERMINATION'
+@strong{9. TERMINATION}
You may not copy, modify, sublicense, or distribute the Document
except as expressly provided under this License. Any attempt
@@ -1341,7 +1343,7 @@ this License. If your rights have been terminated and not permanently
reinstated, receipt of a copy of some or all of the same material does
not give you any rights to use it.
-`10. FUTURE REVISIONS OF THIS LICENSE'
+@strong{10. FUTURE REVISIONS OF THIS LICENSE}
The Free Software Foundation may publish new, revised versions
of the GNU Free Documentation License from time to time. Such new
@@ -1362,7 +1364,7 @@ License can be used, that proxy’s public statement of acceptance of a
version permanently authorizes you to choose that version for the
Document.
-`11. RELICENSING'
+@strong{11. RELICENSING}
“Massive Multiauthor Collaboration Site” (or “MMC Site”) means any
World Wide Web server that publishes copyrightable works and also
@@ -1391,7 +1393,7 @@ The operator of an MMC Site may republish an MMC contained in the site
under CC-BY-SA on the same site at any time before August 1, 2009,
provided the MMC is eligible for relicensing.
-`ADDENDUM: How to use this License for your documents'
+@strong{ADDENDUM: How to use this License for your documents}
To use this License in a document you have written, include a copy of
the License in the document and put the following copyright and
@@ -3,7 +3,7 @@
@setfilename gnat_rm.info
@documentencoding UTF-8
@ifinfo
-@*Generated by Sphinx 5.3.0.@*
+@*Generated by Sphinx 4.3.2.@*
@end ifinfo
@settitle GNAT Reference Manual
@defindex ge
@@ -15,11 +15,13 @@
* gnat_rm: (gnat_rm.info). gnat_rm
@end direntry
+@definfoenclose strong,`,'
+@definfoenclose emph,`,'
@c %**end of header
@copying
@quotation
-GNAT Reference Manual , Nov 24, 2023
+GNAT Reference Manual , Dec 14, 2023
AdaCore
@@ -46,7 +48,7 @@ Copyright @copyright{} 2008-2023, Free Software Foundation
@c %**start of body
@anchor{gnat_rm doc}@anchor{0}
-`GNAT, The GNU Ada Development Environment'
+@emph{GNAT, The GNU Ada Development Environment}
@include gcc-common.texi
@@ -961,7 +963,7 @@ invoked in Ada 83 compatibility mode.
By default, GNAT assumes Ada 2012,
but you can override with a compiler switch
to explicitly specify the language version.
-(Please refer to the `GNAT User’s Guide' for details on these switches.)
+(Please refer to the @emph{GNAT User’s Guide} for details on these switches.)
Throughout this manual, references to ‘Ada’ without a year suffix
apply to all the Ada versions of the language.
@@ -1127,7 +1129,7 @@ and @code{classes}.
@code{Variables}
@item
-`Emphasis'
+@emph{Emphasis}
@item
[optional information or parameters]
@@ -1804,7 +1806,7 @@ type of the expression is either @code{Standard.Boolean}, or any type derived
from this standard type.
Assert checks can be either checked or ignored. By default they are ignored.
-They will be checked if either the command line switch `-gnata' is
+They will be checked if either the command line switch @emph{-gnata} is
used, or if an @code{Assertion_Policy} or @code{Check_Policy} pragma is used
to enable @code{Assert_Checks}.
@@ -1926,10 +1928,10 @@ If the policy is @code{CHECK}, then assertions are enabled, i.e.
the corresponding pragma or aspect is activated.
If the policy is @code{IGNORE}, then assertions are ignored, i.e.
the corresponding pragma or aspect is deactivated.
-This pragma overrides the effect of the `-gnata' switch on the
+This pragma overrides the effect of the @emph{-gnata} switch on the
command line.
If the policy is @code{SUPPRESSIBLE}, then assertions are enabled by default,
-however, if the `-gnatp' switch is specified all assertions are ignored.
+however, if the @emph{-gnatp} switch is specified all assertions are ignored.
The implementation defined policy @code{DISABLE} is like
@code{IGNORE} except that it completely disables semantic
@@ -2163,7 +2165,7 @@ be independently controlled. The identifier @code{Assertion} is special, it
refers to the normal set of pragma @code{Assert} statements.
Checks introduced by this pragma are normally deactivated by default. They can
-be activated either by the command line option `-gnata', which turns on
+be activated either by the command line option @emph{-gnata}, which turns on
all checks, or individually controlled using pragma @code{Check_Policy}.
The identifiers @code{Assertions} and @code{Statement_Assertions} are not
@@ -2186,7 +2188,7 @@ pragma Check_Float_Overflow;
In Ada, the predefined floating-point types (@code{Short_Float},
@code{Float}, @code{Long_Float}, @code{Long_Long_Float}) are
-defined to be `unconstrained'. This means that even though each
+defined to be @emph{unconstrained}. This means that even though each
has a well-defined base range, an operation that delivers a result
outside this base range is not required to raise an exception.
This implementation permission accommodates the notion
@@ -2225,7 +2227,7 @@ will be generated. The @code{Constraint_Error}
exception is raised if the result is out of range.
This mode can also be set by use of the compiler
-switch `-gnateF'.
+switch @emph{-gnateF}.
@node Pragma Check_Name,Pragma Check_Policy,Pragma Check_Float_Overflow,Implementation Defined Pragmas
@anchor{gnat_rm/implementation_defined_pragmas pragma-check-name}@anchor{37}
@@ -2335,7 +2337,7 @@ is given, then subsequent @code{Check} pragmas whose first argument is also
The check policy is @code{OFF} to turn off corresponding checks, and @code{ON}
to turn on corresponding checks. The default for a set of checks for which no
@code{Check_Policy} is given is @code{OFF} unless the compiler switch
-`-gnata' is given, which turns on all checks by default.
+@emph{-gnata} is given, which turns on all checks by default.
The check policy settings @code{CHECK} and @code{IGNORE} are recognized
as synonyms for @code{ON} and @code{OFF}. These synonyms are provided for
@@ -2434,7 +2436,7 @@ pragma Compile_Time_Warning
@end example
Same as pragma Compile_Time_Error, except a warning is issued instead
-of an error message. If switch `-gnatw_C' is used, a warning is only issued
+of an error message. If switch @emph{-gnatw_C} is used, a warning is only issued
if the value of the expression is known to be True at compile time, not when
the value of the expression is not known at compile time.
Note that if this pragma is used in a package that
@@ -2447,7 +2449,7 @@ of formal parameters are tested, and warnings given appropriately. Another use
with a first parameter of True is to warn a client about use of a package,
for example that it is not fully implemented.
-In previous versions of the compiler, combining `-gnatwe' with
+In previous versions of the compiler, combining @emph{-gnatwe} with
Compile_Time_Warning resulted in a fatal error. Now the compiler always emits
a warning. You can use @ref{3b,,Pragma Compile_Time_Error} to force the generation of
an error.
@@ -2527,7 +2529,7 @@ The meaning of the @code{Form} argument is as follows:
@table @asis
-@item `Component_Size'
+@item @emph{Component_Size}
Aligns scalar components and subcomponents of the array or record type
on boundaries appropriate to their inherent size (naturally
@@ -2539,7 +2541,7 @@ machines except the VAX.
@geindex Component_Size_4 (in pragma Component_Alignment)
-@item `Component_Size_4'
+@item @emph{Component_Size_4}
Naturally aligns components with a size of four or fewer
bytes. Components that are larger than 4 bytes are placed on the next
@@ -2547,7 +2549,7 @@ bytes. Components that are larger than 4 bytes are placed on the next
@geindex Storage_Unit (in pragma Component_Alignment)
-@item `Storage_Unit'
+@item @emph{Storage_Unit}
Specifies that array or record components are byte aligned, i.e.,
aligned on boundaries determined by the value of the constant
@@ -2555,7 +2557,7 @@ aligned on boundaries determined by the value of the constant
@geindex Default (in pragma Component_Alignment)
-@item `Default'
+@item @emph{Default}
Specifies that array or record components are aligned on default
boundaries, appropriate to the underlying hardware or operating system or
@@ -2777,16 +2779,16 @@ must be of one of the following forms:
@itemize *
@item
-`function' @code{Fname} `return' T`
+@strong{function} @code{Fname} @strong{return} T`
@item
-`function' @code{Fname} `return' T’Class
+@strong{function} @code{Fname} @strong{return} T’Class
@item
-`function' @code{Fname} (…) `return' T`
+@strong{function} @code{Fname} (…) @strong{return} T`
@item
-`function' @code{Fname} (…) `return' T’Class
+@strong{function} @code{Fname} (…) @strong{return} T’Class
@end itemize
where @code{T} is a limited record type imported from C++ with pragma
@@ -2896,7 +2898,7 @@ semantics of the pragma is exactly equivalent to the procedure call statement
corresponding to the argument with a terminating semicolon. Pragmas are
permitted in sequences of declarations, so you can use pragma @code{Debug} to
intersperse calls to debug procedures in the middle of declarations. Debug
-pragmas can be enabled either by use of the command line switch `-gnata'
+pragmas can be enabled either by use of the command line switch @emph{-gnata}
or by use of the pragma @code{Check_Policy} with a first argument of
@code{Debug}.
@@ -2988,8 +2990,8 @@ package DSSO1 is
end DSSO1;
@end example
-In this example record types with names starting with `L' have @cite{Low_Order_First} scalar
-storage order, and record types with names starting with `H' have @code{High_Order_First}.
+In this example record types with names starting with @emph{L} have @cite{Low_Order_First} scalar
+storage order, and record types with names starting with @emph{H} have @code{High_Order_First}.
Note that in the case of @code{H4a}, the order is not inherited
from the parent type. Only an explicitly set @code{Scalar_Storage_Order}
gets inherited on type derivation.
@@ -3154,8 +3156,8 @@ pragma Elaboration_Checks (Dynamic | Static);
This is a configuration pragma which specifies the elaboration model to be
used during compilation. For more information on the elaboration models of
-GNAT, consult the chapter on elaboration order handling in the `GNAT User’s
-Guide'.
+GNAT, consult the chapter on elaboration order handling in the @emph{GNAT User’s
+Guide}.
The pragma may appear in the following contexts:
@@ -3602,14 +3604,14 @@ the Ada RM. However, other implementations, notably the DEC Ada 83
implementation, provide many extensions to package @code{System}.
For each such implementation accommodated by this pragma, GNAT provides a
-package @code{Aux_@var{xxx}}, e.g., @code{Aux_DEC} for the DEC Ada 83
+package @code{Aux_@emph{xxx}}, e.g., @code{Aux_DEC} for the DEC Ada 83
implementation, which provides the required additional definitions. You
can use this package in two ways. You can @code{with} it in the normal
way and access entities either by selection or using a @code{use}
clause. In this case no special processing is required.
However, if existing code contains references such as
-@code{System.@var{xxx}} where `xxx' is an entity in the extended
+@code{System.@emph{xxx}} where @emph{xxx} is an entity in the extended
definitions provided in package @code{System}, you may use this pragma
to extend visibility in @code{System} in a non-standard way that
provides greater compatibility with the existing code. Pragma
@@ -3617,8 +3619,8 @@ provides greater compatibility with the existing code. Pragma
the name of the package containing the extended definition
(e.g., @code{Aux_DEC} for the DEC Ada case). A unit compiled under
control of this pragma will be processed using special visibility
-processing that looks in package @code{System.Aux_@var{xxx}} where
-@code{Aux_@var{xxx}} is the pragma argument for any entity referenced in
+processing that looks in package @code{System.Aux_@emph{xxx}} where
+@code{Aux_@emph{xxx}} is the pragma argument for any entity referenced in
package @code{System}, but not found in package @code{System}.
You can use this pragma either to access a predefined @code{System}
@@ -3626,7 +3628,7 @@ extension supplied with the compiler, for example @code{Aux_DEC} or
you can construct your own extension unit following the above
definition. Note that such a package is a child of @code{System}
and thus is considered part of the implementation.
-To compile it you will have to use the `-gnatg' switch
+To compile it you will have to use the @emph{-gnatg} switch
for compiling System units, as explained in the
GNAT User’s Guide.
@@ -3801,7 +3803,7 @@ following operations are affected:
@table @asis
-@item `Complex Multiplication'
+@item @emph{Complex Multiplication}
The normal simple formula for complex multiplication can result in intermediate
overflows for numbers near the end of the range. The Ada standard requires that
@@ -3952,7 +3954,9 @@ pragma Ignore_Pragma (pragma_IDENTIFIER);
This is a configuration pragma
that takes a single argument that is a simple identifier. Any subsequent
use of a pragma whose pragma identifier matches this argument will be
-silently ignored. This may be useful when legacy code or code intended
+silently ignored. Any preceding use of a pragma whose pragma identifier
+matches this argument will be parsed and then ignored.
+This may be useful when legacy code or code intended
for compilation with some other compiler contains pragmas that match the
name, but not the exact implementation, of a GNAT pragma. The use of this
pragma allows such pragmas to be ignored, which may be useful in CodePeer
@@ -4425,7 +4429,7 @@ program.
Note that pragma @code{Initialize_Scalars} is particularly useful in conjunction
with the enhanced validity checking that is now provided in GNAT, which checks
for invalid values under more conditions. Using this feature (see description
-of the `-gnatV' flag in the GNAT User’s Guide) in conjunction with pragma
+of the @emph{-gnatV} flag in the GNAT User’s Guide) in conjunction with pragma
@code{Initialize_Scalars} provides a powerful new tool to assist in the detection
of problems caused by uninitialized variables.
@@ -4476,7 +4480,7 @@ pragma Inline_Always (NAME [, NAME]);
Similar to pragma @code{Inline} except that inlining is unconditional.
Inline_Always instructs the compiler to inline every direct call to the
subprogram or else to emit a compilation error, independently of any
-option, in particular `-gnatn' or `-gnatN' or the optimization level.
+option, in particular @emph{-gnatn} or @emph{-gnatN} or the optimization level.
It is an error to take the address or access of @code{NAME}. It is also an error to
apply this pragma to a primitive operation of a tagged type. Thanks to such
restrictions, the compiler is allowed to remove the out-of-line body of @code{NAME}.
@@ -5141,7 +5145,7 @@ unrolling, but there is no guarantee that the loop will be vectorized.
These hints do not remove the need to pass the appropriate switches to the
compiler in order to enable the relevant optimizations, that is to say
-`-funroll-loops' for unrolling and `-ftree-vectorize' for
+@emph{-funroll-loops} for unrolling and @emph{-ftree-vectorize} for
vectorization.
@node Pragma Loop_Variant,Pragma Machine_Attribute,Pragma Loop_Optimize,Implementation Defined Pragmas
@@ -5207,10 +5211,10 @@ pragma Machine_Attribute (
Machine-dependent attributes can be specified for types and/or
declarations. This pragma is semantically equivalent to
-@code{__attribute__((@var{attribute_name}))} (if @code{info} is not
-specified) or @code{__attribute__((@var{attribute_name(info})))}
-or @code{__attribute__((@var{attribute_name(info,...})))} in GNU C,
-where `attribute_name' is recognized by the compiler middle-end
+@code{__attribute__((@emph{attribute_name}))} (if @code{info} is not
+specified) or @code{__attribute__((@emph{attribute_name(info})))}
+or @code{__attribute__((@emph{attribute_name(info,...})))} in GNU C,
+where @emph{attribute_name} is recognized by the compiler middle-end
or the @code{TARGET_ATTRIBUTE_TABLE} machine specific macro. Note
that a string literal for the optional parameter @code{info} or the
following ones is transformed by default into an identifier,
@@ -5395,8 +5399,8 @@ pragma No_Inline (NAME @{, NAME@});
This pragma suppresses inlining for the callable entity or the instances of
the generic subprogram designated by @code{NAME}, including inlining that
results from the use of pragma @code{Inline}. This pragma is always active,
-in particular it is not subject to the use of option `-gnatn' or
-`-gnatN'. It is illegal to specify both pragma @code{No_Inline} and
+in particular it is not subject to the use of option @emph{-gnatn} or
+@emph{-gnatN}. It is illegal to specify both pragma @code{No_Inline} and
pragma @code{Inline_Always} for the same @code{NAME}.
@node Pragma No_Return,Pragma No_Strict_Aliasing,Pragma No_Inline,Implementation Defined Pragmas
@@ -5506,28 +5510,28 @@ are as follows:
@table @asis
-@item `Standard.Character'
+@item @emph{Standard.Character}
Objects whose root type is Standard.Character are initialized to
Character’Last unless the subtype range excludes NUL (in which case
NUL is used). This choice will always generate an invalid value if
one exists.
-@item `Standard.Wide_Character'
+@item @emph{Standard.Wide_Character}
Objects whose root type is Standard.Wide_Character are initialized to
Wide_Character’Last unless the subtype range excludes NUL (in which case
NUL is used). This choice will always generate an invalid value if
one exists.
-@item `Standard.Wide_Wide_Character'
+@item @emph{Standard.Wide_Wide_Character}
Objects whose root type is Standard.Wide_Wide_Character are initialized to
the invalid value 16#FFFF_FFFF# unless the subtype range excludes NUL (in
which case NUL is used). This choice will always generate an invalid value if
one exists.
-@item `Integer types'
+@item @emph{Integer types}
Objects of an integer type are treated differently depending on whether
negative values are present in the subtype. If no negative values are
@@ -5542,26 +5546,26 @@ is in the subtype, and the largest positive number is not, in which case
the largest positive value is used. This choice will always generate
an invalid value if one exists.
-@item `Floating-Point Types'
+@item @emph{Floating-Point Types}
Objects of all floating-point types are initialized to all 1-bits. For
standard IEEE format, this corresponds to a NaN (not a number) which is
indeed an invalid value.
-@item `Fixed-Point Types'
+@item @emph{Fixed-Point Types}
Objects of all fixed-point types are treated as described above for integers,
with the rules applying to the underlying integer value used to represent
the fixed-point value.
-@item `Modular types'
+@item @emph{Modular types}
Objects of a modular type are initialized to all one bits, except in
the special case where zero is excluded from the subtype, in which
case all zero bits are used. This choice will always generate an
invalid value if one exists.
-@item `Enumeration types'
+@item @emph{Enumeration types}
Objects of an enumeration type are initialized to all one-bits, i.e., to
the value @code{2 ** typ'Size - 1} unless the subtype excludes the literal
@@ -5775,7 +5779,7 @@ specifies a set of possible colors, and the order is unimportant.
For unordered enumeration types, it is generally a good idea if
clients avoid comparisons (other than equality or inequality) and
-explicit ranges. (A `client' is a unit where the type is referenced,
+explicit ranges. (A @emph{client} is a unit where the type is referenced,
other than the unit where the type is declared, its body, and its subunits.)
For example, if code buried in some client says:
@@ -5818,7 +5822,7 @@ if D in Mon .. Fri then ...
if D < Wed then ...
@end example
-The pragma `Ordered' is provided to mark enumeration types that
+The pragma @emph{Ordered} is provided to mark enumeration types that
are conceptually ordered, alerting the reader that clients may depend
on the ordering. GNAT provides a pragma to mark enumerations as ordered
rather than one to mark them as unordered, since in our experience,
@@ -5830,7 +5834,7 @@ are considered to be ordered types, so each is declared with a
pragma @code{Ordered} in package @code{Standard}.
Normally pragma @code{Ordered} serves only as documentation and a guide for
-coding standards, but GNAT provides a warning switch `-gnatw.u' that
+coding standards, but GNAT provides a warning switch @emph{-gnatw.u} that
requests warnings for inappropriate uses (comparisons and explicit
subranges) for unordered types. If this switch is used, then any
enumeration type not marked with pragma @code{Ordered} will be considered
@@ -5841,7 +5845,7 @@ template can be instantiated for both cases), so we never generate warnings
for the case of generic enumerated types.
For additional information please refer to the description of the
-`-gnatw.u' switch in the GNAT User’s Guide.
+@emph{-gnatw.u} switch in the GNAT User’s Guide.
@node Pragma Overflow_Mode,Pragma Overriding_Renamings,Pragma Ordered,Implementation Defined Pragmas
@anchor{gnat_rm/implementation_defined_pragmas pragma-overflow-mode}@anchor{b2}
@@ -6072,7 +6076,7 @@ referenced in the postcondition expressions.
The postconditions are collected and automatically tested just
before any return (implicit or explicit) in the subprogram body.
A postcondition is only recognized if postconditions are active
-at the time the pragma is encountered. The compiler switch `gnata'
+at the time the pragma is encountered. The compiler switch @emph{gnata}
turns on all postconditions by default, and pragma @code{Check_Policy}
with an identifier of @code{Postcondition} can also be used to
control whether postconditions are active.
@@ -7204,22 +7208,22 @@ run with various special switches as follows:
@itemize *
@item
-`Where compiler-generated run-time checks remain'
+@emph{Where compiler-generated run-time checks remain}
-The switch `-gnatGL'
+The switch @emph{-gnatGL}
may be used to list the expanded code in pseudo-Ada form.
Runtime checks show up in the listing either as explicit
checks or operators marked with @{@} to indicate a check is present.
@item
-`An identification of known exceptions at compile time'
+@emph{An identification of known exceptions at compile time}
-If the program is compiled with `-gnatwa',
+If the program is compiled with @emph{-gnatwa},
the compiler warning messages will indicate all cases where the compiler
detects that an exception is certain to occur at run time.
@item
-`Possible reads of uninitialized variables'
+@emph{Possible reads of uninitialized variables}
The compiler warns of many such cases, but its output is incomplete.
@end itemize
@@ -7233,29 +7237,29 @@ possible points at which uninitialized data may be read.
@itemize *
@item
-`Where run-time support routines are implicitly invoked'
+@emph{Where run-time support routines are implicitly invoked}
-In the output from `-gnatGL',
+In the output from @emph{-gnatGL},
run-time calls are explicitly listed as calls to the relevant
run-time routine.
@item
-`Object code listing'
+@emph{Object code listing}
-This may be obtained either by using the `-S' switch,
+This may be obtained either by using the @emph{-S} switch,
or the objdump utility.
@item
-`Constructs known to be erroneous at compile time'
+@emph{Constructs known to be erroneous at compile time}
-These are identified by warnings issued by the compiler (use `-gnatwa').
+These are identified by warnings issued by the compiler (use @emph{-gnatwa}).
@item
-`Stack usage information'
+@emph{Stack usage information}
Static stack usage data (maximum per-subprogram) can be obtained via the
-`-fstack-usage' switch to the compiler.
-Dynamic stack usage data (per task) can be obtained via the `-u' switch
+@emph{-fstack-usage} switch to the compiler.
+Dynamic stack usage data (per task) can be obtained via the @emph{-u} switch
to gnatbind
@end itemize
@@ -7264,21 +7268,21 @@ to gnatbind
@itemize *
@item
-`Object code listing of entire partition'
+@emph{Object code listing of entire partition}
-This can be obtained by compiling the partition with `-S',
+This can be obtained by compiling the partition with @emph{-S},
or by applying objdump
to all the object files that are part of the partition.
@item
-`A description of the run-time model'
+@emph{A description of the run-time model}
The full sources of the run-time are available, and the documentation of
these routines describes how these run-time routines interface to the
underlying operating system facilities.
@item
-`Control and data-flow information'
+@emph{Control and data-flow information}
@end itemize
@@ -7598,7 +7602,7 @@ the pragma line (for use in error messages and debugging
information). @code{string_literal} is a static string constant that
specifies the file name to be used in error messages and debugging
information. This is most notably used for the output of @code{gnatchop}
-with the `-r' switch, to make sure that the original unchopped
+with the @emph{-r} switch, to make sure that the original unchopped
source file is the one referred to.
The second argument must be a string literal, it cannot be a static
@@ -7811,7 +7815,7 @@ the @code{gnat.adc} file).
The form with a string literal specifies which style options are to be
activated. These are additive, so they apply in addition to any previously
set style check options. The codes for the options are the same as those
-used in the `-gnaty' switch to `gcc' or `gnatmake'.
+used in the @emph{-gnaty} switch to @emph{gcc} or @emph{gnatmake}.
For example the following two methods can be used to enable
layout checking:
@@ -8727,7 +8731,7 @@ The form with a string literal specifies which validity options are to be
activated. The validity checks are first set to include only the default
reference manual settings, and then a string of letters in the string
specifies the exact set of options required. The form of this string
-is exactly as described for the `-gnatVx' compiler switch (see the
+is exactly as described for the @emph{-gnatVx} compiler switch (see the
GNAT User’s Guide for details). For example the following two
methods can be used to enable validity checking for mode @code{in} and
@code{in out} subprogram parameters:
@@ -8851,8 +8855,8 @@ message string (it is not necessary to put an asterisk at the start and
the end of the message, since this is implied).
Another possibility for the static_string_EXPRESSION which works whether
-or not error tags are enabled (`-gnatw.d') is to use a single
-`-gnatw' tag string, enclosed in brackets,
+or not error tags are enabled (@emph{-gnatw.d}) is to use a single
+@emph{-gnatw} tag string, enclosed in brackets,
as shown in the example below, to treat one category of warnings as errors.
Note that if you want to treat multiple categories of warnings as errors,
you can use multiple pragma Warning_As_Error.
@@ -8860,7 +8864,7 @@ you can use multiple pragma Warning_As_Error.
The above use of patterns to match the message applies only to warning
messages generated by the front end. This pragma can also be applied to
warnings provided by the back end and mentioned in @ref{120,,Pragma Warnings}.
-By using a single full `-Wxxx' switch in the pragma, such warnings
+By using a single full @emph{-Wxxx} switch in the pragma, such warnings
can also be treated as errors.
The pragma can appear either in a global configuration pragma file
@@ -8873,7 +8877,7 @@ pragma Warning_As_Error ("[-gnatwj]");
which will treat all obsolescent feature warnings as errors, the
following program compiles as shown (compile options here are
-`-gnatwa.d -gnatl -gnatj55').
+@emph{-gnatwa.d -gnatl -gnatj55}).
@example
1. pragma Warning_As_Error ("*never assigned*");
@@ -8934,7 +8938,7 @@ expression (which does not exist in Ada 83).
Note if the second argument of @code{DETAILS} is a @code{local_NAME} then the
second form is always understood. If the intention is to use
the fourth form, then you can write @code{NAME & ""} to force the
-interpretation as a `static_string_EXPRESSION'.
+interpretation as a @emph{static_string_EXPRESSION}.
Note: if the first argument is a valid @code{TOOL_NAME}, it will be interpreted
that way. The use of the @code{TOOL_NAME} argument is relevant only to users
@@ -8982,9 +8986,9 @@ The warnings controlled by the @code{-gnatw} switch are generated by the
front end of the compiler. The GCC back end can provide additional warnings
and they are controlled by the @code{-W} switch. Such warnings can be
identified by the appearance of a string of the form @code{[-W@{xxx@}]} in the
-message which designates the @code{-W`xxx'} switch that controls the message.
-The form with a single `static_string_EXPRESSION' argument also works for these
-warnings, but the string must be a single full @code{-W`xxx'} switch in this
+message which designates the @code{-W@emph{xxx}} switch that controls the message.
+The form with a single @emph{static_string_EXPRESSION} argument also works for these
+warnings, but the string must be a single full @code{-W@emph{xxx}} switch in this
case. The above reference lists a few examples of these additional warnings.
The specified warnings will be in effect until the end of the program
@@ -8997,7 +9001,7 @@ also be used as a configuration pragma.
The fourth form, with an @code{On|Off} parameter and a string, is used to
control individual messages, based on their text. The string argument
is a pattern that is used to match against the text of individual
-warning messages (not including the initial “warning: ” tag).
+warning messages (not including the initial “warning: “ tag).
The pattern may contain asterisks, which match zero or more characters in
the message. For example, you can use
@@ -9014,7 +9018,7 @@ the end of the message, since this is implied).
The above use of patterns to match the message applies only to warning
messages generated by the front end. This form of the pragma with a string
argument can also be used to control warnings provided by the back end and
-mentioned above. By using a single full @code{-W`xxx'} switch in the pragma,
+mentioned above. By using a single full @code{-W@emph{xxx}} switch in the pragma,
such warnings can be turned on and off.
There are two ways to use the pragma in this form. The OFF form can be used
@@ -9032,7 +9036,7 @@ pragma Warnings (On, Pattern);
@end example
In this usage, the pattern string must match in the Off and On
-pragmas, and (if `-gnatw.w' is given) at least one matching
+pragmas, and (if @emph{-gnatw.w} is given) at least one matching
warning must be suppressed.
Note: if the ON form is not found, then the effect of the OFF form extends
@@ -9293,15 +9297,15 @@ corresponding to @ref{29,,pragma Annotate}.
@table @asis
-@item `Annotate => ID'
+@item @emph{Annotate => ID}
Equivalent to @code{pragma Annotate (ID, Entity => Name);}
-@item `Annotate => (ID)'
+@item @emph{Annotate => (ID)}
Equivalent to @code{pragma Annotate (ID, Entity => Name);}
-@item `Annotate => (ID ,ID @{, ARG@})'
+@item @emph{Annotate => (ID ,ID @{, ARG@})}
Equivalent to @code{pragma Annotate (ID, ID @{, ARG@}, Entity => Name);}
@end table
@@ -10310,7 +10314,7 @@ supported by the target for the given type.
@code{obj'Bit}, where @code{obj} is any object, yields the bit
offset within the storage unit (byte) that contains the first bit of
storage allocated for the object. The value of this attribute is of the
-type `universal_integer' and is always a nonnegative number smaller
+type @emph{universal_integer} and is always a nonnegative number smaller
than @code{System.Storage_Unit}.
For an object that is a variable or a constant allocated in a register,
@@ -10342,7 +10346,7 @@ and implementation of the @code{Bit} attribute.
of the fields of the record type, yields the bit
offset within the record contains the first bit of
storage allocated for the object. The value of this attribute is of the
-type `universal_integer'. The value depends only on the field
+type @emph{universal_integer}. The value depends only on the field
@code{C} and is independent of the alignment of
the containing record @code{R}.
@@ -10689,7 +10693,7 @@ prefix) yields a static Boolean value that is True if pragma
The prefix of attribute @code{Finalization_Size} must be an object or
a non-class-wide type. This attribute returns the size of any hidden data
reserved by the compiler to handle finalization-related actions. The type of
-the attribute is `universal_integer'.
+the attribute is @emph{universal_integer}.
@code{Finalization_Size} yields a value of zero for a type with no controlled
parts, an object whose type has no controlled parts, or an object of a
@@ -11014,17 +11018,17 @@ the target. The result is a static constant.
@code{func'Mechanism_Code} yields an integer code for the
mechanism used for the result of function @code{func}, and
@code{subprog'Mechanism_Code (n)} yields the mechanism
-used for formal parameter number `n' (a static integer value, with 1
+used for formal parameter number @emph{n} (a static integer value, with 1
meaning the first parameter) of subprogram @code{subprog}. The code returned is:
@table @asis
-@item `1'
+@item @emph{1}
by copy (value)
-@item `2'
+@item @emph{2}
by reference
@end table
@@ -11424,7 +11428,7 @@ the native ordering of the target, but this default can be overridden using
pragma @code{Default_Scalar_Storage_Order}.
If a component of @code{T} is itself of a record or array type, the specfied
-@code{Scalar_Storage_Order} does `not' apply to that nested type: an explicit
+@code{Scalar_Storage_Order} does @emph{not} apply to that nested type: an explicit
attribute definition clause must be provided for the component type as well
if desired.
@@ -11528,7 +11532,7 @@ the primitive @code{Allocate} procedure for type @code{SSP}, passing
@code{S'Simple_Storage_Pool} as the pool parameter. The detailed
semantics of such allocators is the same as those defined for allocators
in section 13.11 of the @cite{Ada Reference Manual}, with the term
-`simple storage pool' substituted for `storage pool'.
+@emph{simple storage pool} substituted for @emph{storage pool}.
If an access type @code{S} has a specified simple storage pool of type
@code{SSP}, then a call to an instance of the @code{Ada.Unchecked_Deallocation}
@@ -11536,7 +11540,7 @@ for that access type invokes the primitive @code{Deallocate} procedure
for type @code{SSP}, passing @code{S'Simple_Storage_Pool} as the pool
parameter. The detailed semantics of such unchecked deallocations is the same
as defined in section 13.11.2 of the Ada Reference Manual, except that the
-term `simple storage pool' is substituted for `storage pool'.
+term @emph{simple storage pool} is substituted for @emph{storage pool}.
@node Attribute Small,Attribute Small_Denominator,Attribute Simple_Storage_Pool,Implementation Defined Attributes
@anchor{gnat_rm/implementation_defined_attributes attribute-small}@anchor{1a7}
@@ -13882,7 +13886,7 @@ Explanation
@item
-`Abort_Defer'
+@emph{Abort_Defer}
@tab
@@ -13890,7 +13894,7 @@ Affects semantics
@item
-`Ada_83'
+@emph{Ada_83}
@tab
@@ -13898,7 +13902,7 @@ Affects legality
@item
-`Assert'
+@emph{Assert}
@tab
@@ -13906,7 +13910,7 @@ Affects semantics
@item
-`CPP_Class'
+@emph{CPP_Class}
@tab
@@ -13914,7 +13918,7 @@ Affects semantics
@item
-`CPP_Constructor'
+@emph{CPP_Constructor}
@tab
@@ -13922,7 +13926,7 @@ Affects semantics
@item
-`Debug'
+@emph{Debug}
@tab
@@ -13930,7 +13934,7 @@ Affects semantics
@item
-`Interface_Name'
+@emph{Interface_Name}
@tab
@@ -13938,7 +13942,7 @@ Affects semantics
@item
-`Machine_Attribute'
+@emph{Machine_Attribute}
@tab
@@ -13946,7 +13950,7 @@ Affects semantics
@item
-`Unimplemented_Unit'
+@emph{Unimplemented_Unit}
@tab
@@ -13954,7 +13958,7 @@ Affects legality
@item
-`Unchecked_Union'
+@emph{Unchecked_Union}
@tab
@@ -14119,7 +14123,7 @@ is a software rather than a hardware format.
row-major order, consistent with the notation used for multidimensional
array aggregates (see 4.3.3). However, if a pragma @code{Convention}
(@code{Fortran}, …) applies to a multidimensional array type, then
-column-major order should be used instead (see B.5, `Interfacing with Fortran').”
+column-major order should be used instead (see B.5, @emph{Interfacing with Fortran}).”
@end quotation
Followed.
@@ -14280,7 +14284,7 @@ The recommended level of support pragma @code{Pack} is:
For a packed record type, the components should be packed as tightly as
possible subject to the Sizes of the component subtypes, and subject to
-any `record_representation_clause' that applies to the type; the
+any @emph{record_representation_clause} that applies to the type; the
implementation may, but need not, reorder components or cross aligned
word boundaries to improve the packing. A component whose @code{Size} is
greater than the word size may be allocated an integral number of words.”
@@ -14538,7 +14542,7 @@ Followed.
@quotation
“The recommended level of support for
-`record_representation_clause's is:
+@emph{record_representation_clause}s is:
An implementation should support storage places that can be extracted
with a load, mask, shift sequence of machine code, and set with a load,
@@ -14579,7 +14583,7 @@ clause for the tag field.
@quotation
-“An implementation need not support a `component_clause' for a
+“An implementation need not support a @emph{component_clause} for a
component of an extension part if the storage place is not after the
storage places of all components of the parent type, whether or not
those storage places had been specified.”
@@ -14965,10 +14969,10 @@ packages.
@quotation
-“For each supported convention `L' other than @code{Intrinsic}, an
+“For each supported convention @emph{L} other than @code{Intrinsic}, an
implementation should support @code{Import} and @code{Export} pragmas
-for objects of `L'-compatible types and for subprograms, and pragma
-@cite{Convention} for `L'-eligible types and for subprograms,
+for objects of @emph{L}-compatible types and for subprograms, and pragma
+@cite{Convention} for @emph{L}-eligible types and for subprograms,
presuming the other language has corresponding features. Pragma
@code{Convention} need not be supported for scalar types.”
@end quotation
@@ -15441,10 +15445,10 @@ Followed. No such implementation-defined queuing policies exist.
@quotation
-“Even though the `abort_statement' is included in the list of
+“Even though the @emph{abort_statement} is included in the list of
potentially blocking operations (see 9.5.1), it is recommended that this
statement be implemented in a way that never requires the task executing
-the `abort_statement' to block.”
+the @emph{abort_statement} to block.”
@end quotation
Followed.
@@ -15800,7 +15804,7 @@ There are no variations from the standard.
interactions. See 1.1.3(10).”
@end itemize
-Any `code_statement' can potentially cause external interactions.
+Any @emph{code_statement} can potentially cause external interactions.
@itemize *
@@ -15841,8 +15845,8 @@ length. See 2.2(15).”
The maximum line length is 255 characters and the maximum length of
a lexical element is also 255 characters. This is the default setting
-if not overridden by the use of compiler switch `-gnaty' (which
-sets the maximum to 79) or `-gnatyMnn' which allows the maximum
+if not overridden by the use of compiler switch @emph{-gnaty} (which
+sets the maximum to 79) or @emph{-gnatyMnn} which allows the maximum
line length to be specified to be any value up to 32767. The maximum
length of a lexical element is the same as the maximum line length.
@@ -15900,7 +15904,7 @@ Representation
@item
-`Short_Short_Integer'
+@emph{Short_Short_Integer}
@tab
@@ -15908,7 +15912,7 @@ Representation
@item
-`Short_Integer'
+@emph{Short_Integer}
@tab
@@ -15916,7 +15920,7 @@ Representation
@item
-`Integer'
+@emph{Integer}
@tab
@@ -15924,7 +15928,7 @@ Representation
@item
-`Long_Integer'
+@emph{Long_Integer}
@tab
@@ -15934,7 +15938,7 @@ depending on the C definition of long)
@item
-`Long_Long_Integer'
+@emph{Long_Long_Integer}
@tab
@@ -15942,7 +15946,7 @@ depending on the C definition of long)
@item
-`Long_Long_Long_Integer'
+@emph{Long_Long_Long_Integer}
@tab
@@ -16003,7 +16007,7 @@ Representation
@item
-`Short_Float'
+@emph{Short_Float}
@tab
@@ -16011,7 +16015,7 @@ IEEE Binary32 (Single)
@item
-`Float'
+@emph{Float}
@tab
@@ -16019,7 +16023,7 @@ IEEE Binary32 (Single)
@item
-`Long_Float'
+@emph{Long_Float}
@tab
@@ -16027,7 +16031,7 @@ IEEE Binary64 (Double)
@item
-`Long_Long_Float'
+@emph{Long_Long_Float}
@tab
@@ -16088,10 +16092,10 @@ small must lie in 1.0E-38 .. 1.0E+38 and the digits in 1 .. 38.
@item
“The result of @code{Tags.Expanded_Name} for types declared
-within an unnamed `block_statement'. See 3.9(10).”
+within an unnamed @emph{block_statement}. See 3.9(10).”
@end itemize
-Block numbers of the form @code{B@var{nnn}}, where `nnn' is a
+Block numbers of the form @code{B@emph{nnn}}, where @emph{nnn} is a
decimal integer are allocated.
@@ -16192,7 +16196,7 @@ Difficult to characterize.
“Any extensions of the Default_Initial_Condition aspect. See 7.3.3(11).”
@end itemize
-SPARK allows specifying `null' as the Default_Initial_Condition
+SPARK allows specifying @emph{null} as the Default_Initial_Condition
aspect of a type. See the SPARK reference manual for further details.
@@ -16240,8 +16244,8 @@ setting for local time, as accessed by the C library function
@itemize *
@item
-“Any limit on `delay_until_statements' of
-`select_statements'. See 9.6(29).”
+“Any limit on @emph{delay_until_statements} of
+@emph{select_statements}. See 9.6(29).”
@end itemize
There are no such limits.
@@ -16273,7 +16277,7 @@ There are no implementation-defined conflict check policies.
@end itemize
A compilation is represented by a sequence of files presented to the
-compiler in a single invocation of the `gcc' command.
+compiler in a single invocation of the @emph{gcc} command.
@itemize *
@@ -16317,11 +16321,11 @@ mentioned in the context clause of one of the needed Ada units.
If the partition contains no main program, or if the main program is in
a language other than Ada, then GNAT
-provides the binder options `-z' and `-n' respectively, and in
+provides the binder options @emph{-z} and @emph{-n} respectively, and in
this case a list of units can be explicitly supplied to the binder for
inclusion in the partition (all units needed by these units will also
be included automatically). For full details on the use of these
-options, refer to `GNAT Make Program gnatmake' in the
+options, refer to @emph{GNAT Make Program gnatmake} in the
@cite{GNAT User’s Guide}.
@@ -16352,7 +16356,7 @@ corresponding @code{ALI} file as the input parameter to the binder.
@itemize *
@item
-“The order of elaboration of `library_items'. See 10.2(18).”
+“The order of elaboration of @emph{library_items}. See 10.2(18).”
@end itemize
The first constraint on ordering is that it meets the requirements of
@@ -16424,11 +16428,11 @@ been passed by the program.
@item
“The result of @code{Exceptions.Exception_Name} for types
-declared within an unnamed `block_statement'. See 11.4.1(12).”
+declared within an unnamed @emph{block_statement}. See 11.4.1(12).”
@end itemize
-Blocks have implementation defined names of the form @code{B@var{nnn}}
-where `nnn' is an integer.
+Blocks have implementation defined names of the form @code{B@emph{nnn}}
+where @emph{nnn} is an integer.
@itemize *
@@ -16694,7 +16698,7 @@ See the definition of package System.Storage_Elements in @code{s-stoele.ads}.
@item
“The contents of the visible part of package @code{System.Machine_Code},
-and the meaning of `code_statements'. See 13.8(7).”
+and the meaning of @emph{code_statements}. See 13.8(7).”
@end itemize
See the definition and documentation in file @code{s-maccod.ads}.
@@ -16928,7 +16932,7 @@ of the state vector.
Annex is not supported. See A.5.3(72).”
@end itemize
-Running the compiler with `-gnatS' to produce a listing of package
+Running the compiler with @emph{-gnatS} to produce a listing of package
@code{Standard} displays the values of these attributes.
@@ -17108,7 +17112,7 @@ Interpretation
@item
-`Ada'
+@emph{Ada}
@tab
@@ -17116,7 +17120,7 @@ Ada
@item
-`Ada_Pass_By_Copy'
+@emph{Ada_Pass_By_Copy}
@tab
@@ -17126,7 +17130,7 @@ with this convention to be passed by copy.
@item
-`Ada_Pass_By_Reference'
+@emph{Ada_Pass_By_Reference}
@tab
@@ -17136,7 +17140,7 @@ with this convention to be passed by reference.
@item
-`Assembler'
+@emph{Assembler}
@tab
@@ -17144,7 +17148,7 @@ Assembly language
@item
-`Asm'
+@emph{Asm}
@tab
@@ -17152,7 +17156,7 @@ Synonym for Assembler
@item
-`Assembly'
+@emph{Assembly}
@tab
@@ -17160,7 +17164,7 @@ Synonym for Assembler
@item
-`C'
+@emph{C}
@tab
@@ -17168,7 +17172,7 @@ C
@item
-`C_Pass_By_Copy'
+@emph{C_Pass_By_Copy}
@tab
@@ -17177,7 +17181,7 @@ is to be passed by copy rather than reference.
@item
-`COBOL'
+@emph{COBOL}
@tab
@@ -17185,7 +17189,7 @@ COBOL
@item
-`C_Plus_Plus (or CPP)'
+@emph{C_Plus_Plus (or CPP)}
@tab
@@ -17193,7 +17197,7 @@ C++
@item
-`Default'
+@emph{Default}
@tab
@@ -17201,7 +17205,7 @@ Treated the same as C
@item
-`External'
+@emph{External}
@tab
@@ -17209,7 +17213,7 @@ Treated the same as C
@item
-`Fortran'
+@emph{Fortran}
@tab
@@ -17217,7 +17221,7 @@ Fortran
@item
-`Intrinsic'
+@emph{Intrinsic}
@tab
@@ -17226,7 +17230,7 @@ separate section on Intrinsic Subprograms.
@item
-`Stdcall'
+@emph{Stdcall}
@tab
@@ -17237,7 +17241,7 @@ exit. This pragma cannot be applied to a dispatching call.
@item
-`DLL'
+@emph{DLL}
@tab
@@ -17245,7 +17249,7 @@ Synonym for Stdcall
@item
-`Win32'
+@emph{Win32}
@tab
@@ -17253,7 +17257,7 @@ Synonym for Stdcall
@item
-`Stubbed'
+@emph{Stubbed}
@tab
@@ -17366,7 +17370,7 @@ Ada
@item
-`Floating'
+@emph{Floating}
@tab
@@ -17374,7 +17378,7 @@ Float
@item
-`Long_Floating'
+@emph{Long_Floating}
@tab
@@ -17382,7 +17386,7 @@ Float
@item
-`Binary'
+@emph{Binary}
@tab
@@ -17390,7 +17394,7 @@ Integer
@item
-`Long_Binary'
+@emph{Long_Binary}
@tab
@@ -17398,7 +17402,7 @@ Long_Long_Integer
@item
-`Decimal_Element'
+@emph{Decimal_Element}
@tab
@@ -17406,7 +17410,7 @@ Character
@item
-`COBOL_Character'
+@emph{COBOL_Character}
@tab
@@ -17503,12 +17507,12 @@ attribute. See C.7.1(7).”
The result of this attribute is a string that identifies
the object or component that denotes a given task. If a variable @code{Var}
-has a task type, the image for this task will have the form @code{Var_@var{XXXXXXXX}},
-where the suffix `XXXXXXXX'
+has a task type, the image for this task will have the form @code{Var_@emph{XXXXXXXX}},
+where the suffix @emph{XXXXXXXX}
is the hexadecimal representation of the virtual address of the corresponding
task control block. If the variable is an array of tasks, the image of each
task will have the form of an indexed component indicating the position of a
-given task in the array, e.g., @code{Group(5)_@var{XXXXXXX}}. If the task is a
+given task in the array, e.g., @code{Group(5)_@emph{XXXXXXX}}. If the task is a
component of a record, the image of the task will have the form of a selected
component. These rules are fully recursive, so that the image of a task that
is a subcomponent of a composite object corresponds to the expression that
@@ -17611,7 +17615,7 @@ The value is 10 milliseconds.
@itemize *
@item
-“Implementation-defined `policy_identifiers' allowed
+“Implementation-defined @emph{policy_identifiers} allowed
in a pragma @code{Locking_Policy}. See D.3(4).”
@end itemize
@@ -17867,7 +17871,7 @@ Value
@item
-`Max_Scale'
+@emph{Max_Scale}
@tab
@@ -17875,7 +17879,7 @@ Value
@item
-`Min_Scale'
+@emph{Min_Scale}
@tab
@@ -17883,7 +17887,7 @@ Value
@item
-`Min_Delta'
+@emph{Min_Delta}
@tab
@@ -17891,7 +17895,7 @@ Value
@item
-`Max_Delta'
+@emph{Max_Delta}
@tab
@@ -17899,7 +17903,7 @@ Value
@item
-`Max_Decimal_Digits'
+@emph{Max_Decimal_Digits}
@tab
@@ -17991,7 +17995,7 @@ result type is @code{False}. See G.2.1(13).”
Infinite and NaN values are produced as dictated by the IEEE
floating-point standard.
Note that on machines that are not fully compliant with the IEEE
-floating-point standard, such as Alpha, the `-mieee' compiler flag
+floating-point standard, such as Alpha, the @emph{-mieee} compiler flag
must be used for achieving IEEE conforming behavior (although at the cost
of a significant performance penalty), so infinite and NaN values are
properly generated.
@@ -18024,7 +18028,7 @@ is converted to the target type.
@itemize *
@item
-“Conditions on a `universal_real' operand of a fixed
+“Conditions on a @emph{universal_real} operand of a fixed
point multiplication or division for which the result shall be in the
perfect result set. See G.2.3(22).”
@end itemize
@@ -18443,7 +18447,7 @@ The default alignment values are as follows:
@itemize *
@item
-`Elementary Types'.
+@emph{Elementary Types}.
For elementary types, the alignment is the minimum of the actual size of
objects of the type divided by @code{Storage_Unit},
@@ -18460,7 +18464,7 @@ than 8, in which case objects of type @code{Long_Float} will be maximally
aligned.
@item
-`Arrays'.
+@emph{Arrays}.
For arrays, the alignment is equal to the alignment of the component type
for the normal case where no packing or component size is given. If the
@@ -18473,7 +18477,7 @@ will be as described for elementary types, e.g. a packed array of length
31 bits will have an object size of four bytes, and an alignment of 4.
@item
-`Records'.
+@emph{Records}.
For the normal unpacked case, the alignment of a record is equal to
the maximum alignment of any of its components. For tagged records, this
@@ -18657,7 +18661,7 @@ Then @code{Default_Stack_Size} can be defined in a global package, and
modified as required. Any tasks requiring stack sizes different from the
default can have an appropriate alternative reference in the pragma.
-You can also use the `-d' binder switch to modify the default stack
+You can also use the @emph{-d} binder switch to modify the default stack
size.
For access types, the @code{Storage_Size} clause specifies the maximum
@@ -18917,7 +18921,7 @@ discrete types are as follows:
@item
The @code{Object_Size} for base subtypes reflect the natural hardware
-size in bits (run the compiler with `-gnatS' to find those values
+size in bits (run the compiler with @emph{-gnatS} to find those values
for numeric types). Enumeration types and fixed-point base subtypes have
8, 16, 32, or 64 bits for this size, depending on the range of values
to be stored.
@@ -19590,7 +19594,7 @@ an appropriate manner.
@geindex Pragma Pack (for arrays)
Pragma @code{Pack} applied to an array has an effect that depends upon whether the
-component type is `packable'. For a component type to be `packable', it must
+component type is @emph{packable}. For a component type to be @emph{packable}, it must
be one of the following cases:
@@ -19711,8 +19715,8 @@ since in this case the programmer intention is clear.
Pragma @code{Pack} applied to a record will pack the components to reduce
wasted space from alignment gaps and by reducing the amount of space
-taken by components. We distinguish between `packable' components and
-`non-packable' components.
+taken by components. We distinguish between @emph{packable} components and
+@emph{non-packable} components.
Components of the following types are considered packable:
@@ -19961,7 +19965,7 @@ be in the range:
0 .. System.Max_Binary_Modulus;
@end example
-A `confirming' representation clause is one in which the values range
+A @emph{confirming} representation clause is one in which the values range
from 0 in sequence, i.e., a clause that confirms the default representation
for an enumeration type.
Such a confirming representation
@@ -20403,7 +20407,7 @@ There are four exceptions to this general rule:
@itemize *
@item
-`Convention Fortran and array subtypes'.
+@emph{Convention Fortran and array subtypes}.
If pragma Convention Fortran is specified for an array subtype, then in
accordance with the implementation advice in section 3.6.2(11) of the
@@ -20411,7 +20415,7 @@ Ada Reference Manual, the array will be stored in a Fortran-compatible
column-major manner, instead of the normal default row-major order.
@item
-`Convention C and enumeration types'
+@emph{Convention C and enumeration types}
GNAT normally stores enumeration types in 8, 16, or 32 bits as required
to accommodate all values of the type. For example, for the enumeration
@@ -20437,7 +20441,7 @@ warning in this situation. The warning can be suppressed by giving an explicit
size clause specifying the desired size.
@item
-`Convention C/Fortran and Boolean types'
+@emph{Convention C/Fortran and Boolean types}
In C, the usual convention for boolean values, that is values used for
conditions, is that zero represents false, and nonzero values represent
@@ -20561,7 +20565,7 @@ fields placed? The section on pragma @code{Pack} in this chapter can be
used to answer the second question, but it is often easier to just see
what the compiler does.
-For this purpose, GNAT provides the option `-gnatR'. If you compile
+For this purpose, GNAT provides the option @emph{-gnatR}. If you compile
with this option, then the compiler will output information on the actual
representations chosen, in a format similar to source representation
clauses. For example, if we compile the package:
@@ -20610,7 +20614,7 @@ package q is
end q;
@end example
-using the switch `-gnatR' we obtain the following output:
+using the switch @emph{-gnatR} we obtain the following output:
@example
Representation information for unit q
@@ -20720,56 +20724,56 @@ the unit is not implemented.
@table @asis
-@item @code{Ada} `(A.2)'
+@item @code{Ada} @emph{(A.2)}
This is a parent package for all the standard library packages. It is
usually included implicitly in your program, and itself contains no
useful data or routines.
-@item @code{Ada.Assertions} `(11.4.2)'
+@item @code{Ada.Assertions} @emph{(11.4.2)}
@code{Assertions} provides the @code{Assert} subprograms, and also
the declaration of the @code{Assertion_Error} exception.
-@item @code{Ada.Asynchronous_Task_Control} `(D.11)'
+@item @code{Ada.Asynchronous_Task_Control} @emph{(D.11)}
@code{Asynchronous_Task_Control} provides low level facilities for task
synchronization. It is typically not implemented. See package spec for details.
-@item @code{Ada.Calendar} `(9.6)'
+@item @code{Ada.Calendar} @emph{(9.6)}
@code{Calendar} provides time of day access, and routines for
manipulating times and durations.
-@item @code{Ada.Calendar.Arithmetic} `(9.6.1)'
+@item @code{Ada.Calendar.Arithmetic} @emph{(9.6.1)}
This package provides additional arithmetic
operations for @code{Calendar}.
-@item @code{Ada.Calendar.Formatting} `(9.6.1)'
+@item @code{Ada.Calendar.Formatting} @emph{(9.6.1)}
This package provides formatting operations for @code{Calendar}.
-@item @code{Ada.Calendar.Time_Zones} `(9.6.1)'
+@item @code{Ada.Calendar.Time_Zones} @emph{(9.6.1)}
This package provides additional @code{Calendar} facilities
for handling time zones.
-@item @code{Ada.Characters} `(A.3.1)'
+@item @code{Ada.Characters} @emph{(A.3.1)}
This is a dummy parent package that contains no useful entities
-@item @code{Ada.Characters.Conversions} `(A.3.2)'
+@item @code{Ada.Characters.Conversions} @emph{(A.3.2)}
This package provides character conversion functions.
-@item @code{Ada.Characters.Handling} `(A.3.2)'
+@item @code{Ada.Characters.Handling} @emph{(A.3.2)}
This package provides some basic character handling capabilities,
including classification functions for classes of characters (e.g., test
for letters, or digits).
-@item @code{Ada.Characters.Latin_1} `(A.3.3)'
+@item @code{Ada.Characters.Latin_1} @emph{(A.3.3)}
This package includes a complete set of definitions of the characters
that appear in type CHARACTER. It is useful for writing programs that
@@ -20779,194 +20783,194 @@ the definition of @code{UC_E_Acute} in this package. Then your program
will print in an understandable manner even if your environment does not
support these extended characters.
-@item @code{Ada.Command_Line} `(A.15)'
+@item @code{Ada.Command_Line} @emph{(A.15)}
This package provides access to the command line parameters and the name
of the current program (analogous to the use of @code{argc} and @code{argv}
in C), and also allows the exit status for the program to be set in a
system-independent manner.
-@item @code{Ada.Complex_Text_IO} `(G.1.3)'
+@item @code{Ada.Complex_Text_IO} @emph{(G.1.3)}
This package provides text input and output of complex numbers.
-@item @code{Ada.Containers} `(A.18.1)'
+@item @code{Ada.Containers} @emph{(A.18.1)}
A top level package providing a few basic definitions used by all the
following specific child packages that provide specific kinds of
containers.
@end table
-@code{Ada.Containers.Bounded_Priority_Queues} `(A.18.31)'
+@code{Ada.Containers.Bounded_Priority_Queues} @emph{(A.18.31)}
-@code{Ada.Containers.Bounded_Synchronized_Queues} `(A.18.29)'
+@code{Ada.Containers.Bounded_Synchronized_Queues} @emph{(A.18.29)}
-@code{Ada.Containers.Doubly_Linked_Lists} `(A.18.3)'
+@code{Ada.Containers.Doubly_Linked_Lists} @emph{(A.18.3)}
-@code{Ada.Containers.Generic_Array_Sort} `(A.18.26)'
+@code{Ada.Containers.Generic_Array_Sort} @emph{(A.18.26)}
-@code{Ada.Containers.Generic_Constrained_Array_Sort} `(A.18.26)'
+@code{Ada.Containers.Generic_Constrained_Array_Sort} @emph{(A.18.26)}
-@code{Ada.Containers.Generic_Sort} `(A.18.26)'
+@code{Ada.Containers.Generic_Sort} @emph{(A.18.26)}
-@code{Ada.Containers.Hashed_Maps} `(A.18.5)'
+@code{Ada.Containers.Hashed_Maps} @emph{(A.18.5)}
-@code{Ada.Containers.Hashed_Sets} `(A.18.8)'
+@code{Ada.Containers.Hashed_Sets} @emph{(A.18.8)}
-@code{Ada.Containers.Indefinite_Doubly_Linked_Lists} `(A.18.12)'
+@code{Ada.Containers.Indefinite_Doubly_Linked_Lists} @emph{(A.18.12)}
-@code{Ada.Containers.Indefinite_Hashed_Maps} `(A.18.13)'
+@code{Ada.Containers.Indefinite_Hashed_Maps} @emph{(A.18.13)}
-@code{Ada.Containers.Indefinite_Hashed_Sets} `(A.18.15)'
+@code{Ada.Containers.Indefinite_Hashed_Sets} @emph{(A.18.15)}
-@code{Ada.Containers.Indefinite_Holders} `(A.18.18)'
+@code{Ada.Containers.Indefinite_Holders} @emph{(A.18.18)}
-@code{Ada.Containers.Indefinite_Multiway_Trees} `(A.18.17)'
+@code{Ada.Containers.Indefinite_Multiway_Trees} @emph{(A.18.17)}
-@code{Ada.Containers.Indefinite_Ordered_Maps} `(A.18.14)'
+@code{Ada.Containers.Indefinite_Ordered_Maps} @emph{(A.18.14)}
-@code{Ada.Containers.Indefinite_Ordered_Sets} `(A.18.16)'
+@code{Ada.Containers.Indefinite_Ordered_Sets} @emph{(A.18.16)}
-@code{Ada.Containers.Indefinite_Vectors} `(A.18.11)'
+@code{Ada.Containers.Indefinite_Vectors} @emph{(A.18.11)}
-@code{Ada.Containers.Multiway_Trees} `(A.18.10)'
+@code{Ada.Containers.Multiway_Trees} @emph{(A.18.10)}
-@code{Ada.Containers.Ordered_Maps} `(A.18.6)'
+@code{Ada.Containers.Ordered_Maps} @emph{(A.18.6)}
-@code{Ada.Containers.Ordered_Sets} `(A.18.9)'
+@code{Ada.Containers.Ordered_Sets} @emph{(A.18.9)}
-@code{Ada.Containers.Synchronized_Queue_Interfaces} `(A.18.27)'
+@code{Ada.Containers.Synchronized_Queue_Interfaces} @emph{(A.18.27)}
-@code{Ada.Containers.Unbounded_Priority_Queues} `(A.18.30)'
+@code{Ada.Containers.Unbounded_Priority_Queues} @emph{(A.18.30)}
-@code{Ada.Containers.Unbounded_Synchronized_Queues} `(A.18.28)'
+@code{Ada.Containers.Unbounded_Synchronized_Queues} @emph{(A.18.28)}
-@code{Ada.Containers.Vectors} `(A.18.2)'
+@code{Ada.Containers.Vectors} @emph{(A.18.2)}
@table @asis
-@item @code{Ada.Directories} `(A.16)'
+@item @code{Ada.Directories} @emph{(A.16)}
This package provides operations on directories.
-@item @code{Ada.Directories.Hierarchical_File_Names} `(A.16.1)'
+@item @code{Ada.Directories.Hierarchical_File_Names} @emph{(A.16.1)}
This package provides additional directory operations handling
hierarchical file names.
-@item @code{Ada.Directories.Information} `(A.16)'
+@item @code{Ada.Directories.Information} @emph{(A.16)}
This is an implementation defined package for additional directory
operations, which is not implemented in GNAT.
-@item @code{Ada.Decimal} `(F.2)'
+@item @code{Ada.Decimal} @emph{(F.2)}
This package provides constants describing the range of decimal numbers
implemented, and also a decimal divide routine (analogous to the COBOL
verb DIVIDE … GIVING … REMAINDER …)
-@item @code{Ada.Direct_IO} `(A.8.4)'
+@item @code{Ada.Direct_IO} @emph{(A.8.4)}
This package provides input-output using a model of a set of records of
fixed-length, containing an arbitrary definite Ada type, indexed by an
integer record number.
-@item @code{Ada.Dispatching} `(D.2.1)'
+@item @code{Ada.Dispatching} @emph{(D.2.1)}
A parent package containing definitions for task dispatching operations.
-@item @code{Ada.Dispatching.EDF} `(D.2.6)'
+@item @code{Ada.Dispatching.EDF} @emph{(D.2.6)}
Not implemented in GNAT.
-@item @code{Ada.Dispatching.Non_Preemptive} `(D.2.4)'
+@item @code{Ada.Dispatching.Non_Preemptive} @emph{(D.2.4)}
Not implemented in GNAT.
-@item @code{Ada.Dispatching.Round_Robin} `(D.2.5)'
+@item @code{Ada.Dispatching.Round_Robin} @emph{(D.2.5)}
Not implemented in GNAT.
-@item @code{Ada.Dynamic_Priorities} `(D.5)'
+@item @code{Ada.Dynamic_Priorities} @emph{(D.5)}
This package allows the priorities of a task to be adjusted dynamically
as the task is running.
-@item @code{Ada.Environment_Variables} `(A.17)'
+@item @code{Ada.Environment_Variables} @emph{(A.17)}
This package provides facilities for accessing environment variables.
-@item @code{Ada.Exceptions} `(11.4.1)'
+@item @code{Ada.Exceptions} @emph{(11.4.1)}
This package provides additional information on exceptions, and also
contains facilities for treating exceptions as data objects, and raising
exceptions with associated messages.
-@item @code{Ada.Execution_Time} `(D.14)'
+@item @code{Ada.Execution_Time} @emph{(D.14)}
This package provides CPU clock functionalities. It is not implemented on
all targets (see package spec for details).
-@item @code{Ada.Execution_Time.Group_Budgets} `(D.14.2)'
+@item @code{Ada.Execution_Time.Group_Budgets} @emph{(D.14.2)}
Not implemented in GNAT.
-@item @code{Ada.Execution_Time.Timers} `(D.14.1)’'
+@item @code{Ada.Execution_Time.Timers} @emph{(D.14.1)’}
Not implemented in GNAT.
-@item @code{Ada.Finalization} `(7.6)'
+@item @code{Ada.Finalization} @emph{(7.6)}
This package contains the declarations and subprograms to support the
use of controlled types, providing for automatic initialization and
finalization (analogous to the constructors and destructors of C++).
-@item @code{Ada.Float_Text_IO} `(A.10.9)'
+@item @code{Ada.Float_Text_IO} @emph{(A.10.9)}
A library level instantiation of Text_IO.Float_IO for type Float.
-@item @code{Ada.Float_Wide_Text_IO} `(A.10.9)'
+@item @code{Ada.Float_Wide_Text_IO} @emph{(A.10.9)}
A library level instantiation of Wide_Text_IO.Float_IO for type Float.
-@item @code{Ada.Float_Wide_Wide_Text_IO} `(A.10.9)'
+@item @code{Ada.Float_Wide_Wide_Text_IO} @emph{(A.10.9)}
A library level instantiation of Wide_Wide_Text_IO.Float_IO for type Float.
-@item @code{Ada.Integer_Text_IO} `(A.10.9)'
+@item @code{Ada.Integer_Text_IO} @emph{(A.10.9)}
A library level instantiation of Text_IO.Integer_IO for type Integer.
-@item @code{Ada.Integer_Wide_Text_IO} `(A.10.9)'
+@item @code{Ada.Integer_Wide_Text_IO} @emph{(A.10.9)}
A library level instantiation of Wide_Text_IO.Integer_IO for type Integer.
-@item @code{Ada.Integer_Wide_Wide_Text_IO} `(A.10.9)'
+@item @code{Ada.Integer_Wide_Wide_Text_IO} @emph{(A.10.9)}
A library level instantiation of Wide_Wide_Text_IO.Integer_IO for type Integer.
-@item @code{Ada.Interrupts} `(C.3.2)'
+@item @code{Ada.Interrupts} @emph{(C.3.2)}
This package provides facilities for interfacing to interrupts, which
includes the set of signals or conditions that can be raised and
recognized as interrupts.
-@item @code{Ada.Interrupts.Names} `(C.3.2)'
+@item @code{Ada.Interrupts.Names} @emph{(C.3.2)}
This package provides the set of interrupt names (actually signal
or condition names) that can be handled by GNAT.
-@item @code{Ada.IO_Exceptions} `(A.13)'
+@item @code{Ada.IO_Exceptions} @emph{(A.13)}
This package defines the set of exceptions that can be raised by use of
the standard IO packages.
-@item @code{Ada.Iterator_Interfaces} `(5.5.1)'
+@item @code{Ada.Iterator_Interfaces} @emph{(5.5.1)}
This package provides a generic interface to generalized iterators.
-@item @code{Ada.Locales} `(A.19)'
+@item @code{Ada.Locales} @emph{(A.19)}
This package provides declarations providing information (Language
and Country) about the current locale.
@@ -20978,7 +20982,7 @@ throughout the numerics packages. Note that the constants pi and e are
defined here, and it is better to use these definitions than rolling
your own.
-@item @code{Ada.Numerics.Complex_Arrays} `(G.3.2)'
+@item @code{Ada.Numerics.Complex_Arrays} @emph{(G.3.2)}
Provides operations on arrays of complex numbers.
@@ -21085,15 +21089,15 @@ The following predefined instantiations of this package exist
@code{Ada.Numerics.Long_Elementary_Functions}
@end itemize
-@item @code{Ada.Numerics.Generic_Real_Arrays} `(G.3.1)'
+@item @code{Ada.Numerics.Generic_Real_Arrays} @emph{(G.3.1)}
Generic operations on arrays of reals
-@item @code{Ada.Numerics.Real_Arrays} `(G.3.1)'
+@item @code{Ada.Numerics.Real_Arrays} @emph{(G.3.1)}
Preinstantiation of Ada.Numerics.Generic_Real_Arrays (Float).
-@item @code{Ada.Real_Time} `(D.8)'
+@item @code{Ada.Real_Time} @emph{(D.8)}
This package provides facilities similar to those of @code{Calendar}, but
operating with a finer clock suitable for real time control. Note that
@@ -21102,29 +21106,29 @@ guarantees this behavior, but of course if the external clock on which
the GNAT runtime depends is deliberately reset by some external event,
then such a backward jump may occur.
-@item @code{Ada.Real_Time.Timing_Events} `(D.15)'
+@item @code{Ada.Real_Time.Timing_Events} @emph{(D.15)}
Not implemented in GNAT.
-@item @code{Ada.Sequential_IO} `(A.8.1)'
+@item @code{Ada.Sequential_IO} @emph{(A.8.1)}
This package provides input-output facilities for sequential files,
which can contain a sequence of values of a single type, which can be
any Ada type, including indefinite (unconstrained) types.
-@item @code{Ada.Storage_IO} `(A.9)'
+@item @code{Ada.Storage_IO} @emph{(A.9)}
This package provides a facility for mapping arbitrary Ada types to and
from a storage buffer. It is primarily intended for the creation of new
IO packages.
-@item @code{Ada.Streams} `(13.13.1)'
+@item @code{Ada.Streams} @emph{(13.13.1)}
This is a generic package that provides the basic support for the
concept of streams as used by the stream attributes (@code{Input},
@code{Output}, @code{Read} and @code{Write}).
-@item @code{Ada.Streams.Stream_IO} `(A.12.1)'
+@item @code{Ada.Streams.Stream_IO} @emph{(A.12.1)}
This package is a specialization of the type @code{Streams} defined in
package @code{Streams} together with a set of operations providing
@@ -21132,76 +21136,76 @@ Stream_IO capability. The Stream_IO model permits both random and
sequential access to a file which can contain an arbitrary set of values
of one or more Ada types.
-@item @code{Ada.Strings} `(A.4.1)'
+@item @code{Ada.Strings} @emph{(A.4.1)}
This package provides some basic constants used by the string handling
packages.
-@item @code{Ada.Strings.Bounded} `(A.4.4)'
+@item @code{Ada.Strings.Bounded} @emph{(A.4.4)}
This package provides facilities for handling variable length
strings. The bounded model requires a maximum length. It is thus
somewhat more limited than the unbounded model, but avoids the use of
dynamic allocation or finalization.
-@item @code{Ada.Strings.Bounded.Equal_Case_Insensitive} `(A.4.10)'
+@item @code{Ada.Strings.Bounded.Equal_Case_Insensitive} @emph{(A.4.10)}
Provides case-insensitive comparisons of bounded strings
-@item @code{Ada.Strings.Bounded.Hash} `(A.4.9)'
+@item @code{Ada.Strings.Bounded.Hash} @emph{(A.4.9)}
This package provides a generic hash function for bounded strings
-@item @code{Ada.Strings.Bounded.Hash_Case_Insensitive} `(A.4.9)'
+@item @code{Ada.Strings.Bounded.Hash_Case_Insensitive} @emph{(A.4.9)}
This package provides a generic hash function for bounded strings that
converts the string to be hashed to lower case.
-@item @code{Ada.Strings.Bounded.Less_Case_Insensitive} `(A.4.10)'
+@item @code{Ada.Strings.Bounded.Less_Case_Insensitive} @emph{(A.4.10)}
This package provides a comparison function for bounded strings that works
in a case insensitive manner by converting to lower case before the comparison.
-@item @code{Ada.Strings.Fixed} `(A.4.3)'
+@item @code{Ada.Strings.Fixed} @emph{(A.4.3)}
This package provides facilities for handling fixed length strings.
-@item @code{Ada.Strings.Fixed.Equal_Case_Insensitive} `(A.4.10)'
+@item @code{Ada.Strings.Fixed.Equal_Case_Insensitive} @emph{(A.4.10)}
This package provides an equality function for fixed strings that compares
the strings after converting both to lower case.
-@item @code{Ada.Strings.Fixed.Hash_Case_Insensitive} `(A.4.9)'
+@item @code{Ada.Strings.Fixed.Hash_Case_Insensitive} @emph{(A.4.9)}
This package provides a case insensitive hash function for fixed strings that
converts the string to lower case before computing the hash.
-@item @code{Ada.Strings.Fixed.Less_Case_Insensitive} `(A.4.10)'
+@item @code{Ada.Strings.Fixed.Less_Case_Insensitive} @emph{(A.4.10)}
This package provides a comparison function for fixed strings that works
in a case insensitive manner by converting to lower case before the comparison.
-@item @code{Ada.Strings.Hash} `(A.4.9)'
+@item @code{Ada.Strings.Hash} @emph{(A.4.9)}
This package provides a hash function for strings.
-@item @code{Ada.Strings.Hash_Case_Insensitive} `(A.4.9)'
+@item @code{Ada.Strings.Hash_Case_Insensitive} @emph{(A.4.9)}
This package provides a hash function for strings that is case insensitive.
The string is converted to lower case before computing the hash.
-@item @code{Ada.Strings.Less_Case_Insensitive} `(A.4.10)'
+@item @code{Ada.Strings.Less_Case_Insensitive} @emph{(A.4.10)}
This package provides a comparison function for\strings that works
in a case insensitive manner by converting to lower case before the comparison.
-@item @code{Ada.Strings.Maps} `(A.4.2)'
+@item @code{Ada.Strings.Maps} @emph{(A.4.2)}
This package provides facilities for handling character mappings and
arbitrarily defined subsets of characters. For instance it is useful in
defining specialized translation tables.
-@item @code{Ada.Strings.Maps.Constants} `(A.4.6)'
+@item @code{Ada.Strings.Maps.Constants} @emph{(A.4.6)}
This package provides a standard set of predefined mappings and
predefined character sets. For example, the standard upper to lower case
@@ -21211,62 +21215,62 @@ characters, including extended characters like E with an acute accent,
into account. You should use the mappings in this package (rather than
adding 32 yourself) to do case mappings.
-@item @code{Ada.Strings.Unbounded} `(A.4.5)'
+@item @code{Ada.Strings.Unbounded} @emph{(A.4.5)}
This package provides facilities for handling variable length
strings. The unbounded model allows arbitrary length strings, but
requires the use of dynamic allocation and finalization.
-@item @code{Ada.Strings.Unbounded.Equal_Case_Insensitive} `(A.4.10)'
+@item @code{Ada.Strings.Unbounded.Equal_Case_Insensitive} @emph{(A.4.10)}
Provides case-insensitive comparisons of unbounded strings
-@item @code{Ada.Strings.Unbounded.Hash} `(A.4.9)'
+@item @code{Ada.Strings.Unbounded.Hash} @emph{(A.4.9)}
This package provides a generic hash function for unbounded strings
-@item @code{Ada.Strings.Unbounded.Hash_Case_Insensitive} `(A.4.9)'
+@item @code{Ada.Strings.Unbounded.Hash_Case_Insensitive} @emph{(A.4.9)}
This package provides a generic hash function for unbounded strings that
converts the string to be hashed to lower case.
-@item @code{Ada.Strings.Unbounded.Less_Case_Insensitive} `(A.4.10)'
+@item @code{Ada.Strings.Unbounded.Less_Case_Insensitive} @emph{(A.4.10)}
This package provides a comparison function for unbounded strings that works
in a case insensitive manner by converting to lower case before the comparison.
-@item @code{Ada.Strings.UTF_Encoding} `(A.4.11)'
+@item @code{Ada.Strings.UTF_Encoding} @emph{(A.4.11)}
This package provides basic definitions for dealing with UTF-encoded strings.
-@item @code{Ada.Strings.UTF_Encoding.Conversions} `(A.4.11)'
+@item @code{Ada.Strings.UTF_Encoding.Conversions} @emph{(A.4.11)}
This package provides conversion functions for UTF-encoded strings.
@end table
-@code{Ada.Strings.UTF_Encoding.Strings} `(A.4.11)'
+@code{Ada.Strings.UTF_Encoding.Strings} @emph{(A.4.11)}
-@code{Ada.Strings.UTF_Encoding.Wide_Strings} `(A.4.11)'
+@code{Ada.Strings.UTF_Encoding.Wide_Strings} @emph{(A.4.11)}
@table @asis
-@item @code{Ada.Strings.UTF_Encoding.Wide_Wide_Strings} `(A.4.11)'
+@item @code{Ada.Strings.UTF_Encoding.Wide_Wide_Strings} @emph{(A.4.11)}
These packages provide facilities for handling UTF encodings for
Strings, Wide_Strings and Wide_Wide_Strings.
@end table
-@code{Ada.Strings.Wide_Bounded} `(A.4.7)'
+@code{Ada.Strings.Wide_Bounded} @emph{(A.4.7)}
-@code{Ada.Strings.Wide_Fixed} `(A.4.7)'
+@code{Ada.Strings.Wide_Fixed} @emph{(A.4.7)}
-@code{Ada.Strings.Wide_Maps} `(A.4.7)'
+@code{Ada.Strings.Wide_Maps} @emph{(A.4.7)}
@table @asis
-@item @code{Ada.Strings.Wide_Unbounded} `(A.4.7)'
+@item @code{Ada.Strings.Wide_Unbounded} @emph{(A.4.7)}
These packages provide analogous capabilities to the corresponding
packages without @code{Wide_} in the name, but operate with the types
@@ -21274,33 +21278,33 @@ packages without @code{Wide_} in the name, but operate with the types
and @code{Character}. Versions of all the child packages are available.
@end table
-@code{Ada.Strings.Wide_Wide_Bounded} `(A.4.7)'
+@code{Ada.Strings.Wide_Wide_Bounded} @emph{(A.4.7)}
-@code{Ada.Strings.Wide_Wide_Fixed} `(A.4.7)'
+@code{Ada.Strings.Wide_Wide_Fixed} @emph{(A.4.7)}
-@code{Ada.Strings.Wide_Wide_Maps} `(A.4.7)'
+@code{Ada.Strings.Wide_Wide_Maps} @emph{(A.4.7)}
@table @asis
-@item @code{Ada.Strings.Wide_Wide_Unbounded} `(A.4.7)'
+@item @code{Ada.Strings.Wide_Wide_Unbounded} @emph{(A.4.7)}
These packages provide analogous capabilities to the corresponding
packages without @code{Wide_} in the name, but operate with the types
@code{Wide_Wide_String} and @code{Wide_Wide_Character} instead
of @code{String} and @code{Character}.
-@item @code{Ada.Synchronous_Barriers} `(D.10.1)'
+@item @code{Ada.Synchronous_Barriers} @emph{(D.10.1)}
This package provides facilities for synchronizing tasks at a low level
with barriers.
-@item @code{Ada.Synchronous_Task_Control} `(D.10)'
+@item @code{Ada.Synchronous_Task_Control} @emph{(D.10)}
This package provides some standard facilities for controlling task
communication in a synchronous manner.
-@item @code{Ada.Synchronous_Task_Control.EDF} `(D.10)'
+@item @code{Ada.Synchronous_Task_Control.EDF} @emph{(D.10)}
Not implemented in GNAT.
@@ -21309,21 +21313,21 @@ Not implemented in GNAT.
This package contains definitions for manipulation of the tags of tagged
values.
-@item @code{Ada.Tags.Generic_Dispatching_Constructor} `(3.9)'
+@item @code{Ada.Tags.Generic_Dispatching_Constructor} @emph{(3.9)}
This package provides a way of constructing tagged class-wide values given
only the tag value.
-@item @code{Ada.Task_Attributes} `(C.7.2)'
+@item @code{Ada.Task_Attributes} @emph{(C.7.2)}
This package provides the capability of associating arbitrary
task-specific data with separate tasks.
-@item @code{Ada.Task_Identification} `(C.7.1)'
+@item @code{Ada.Task_Identification} @emph{(C.7.1)}
This package provides capabilities for task identification.
-@item @code{Ada.Task_Termination} `(C.7.3)'
+@item @code{Ada.Task_Termination} @emph{(C.7.3)}
This package provides control over task termination.
@@ -21487,12 +21491,12 @@ unchecked conversion nor Ada.Address_To_Access_Conversions should be
used in conjunction with pointers to unconstrained objects, since
the bounds information cannot be handled correctly in this case.
-@item @code{Ada.Unchecked_Deallocation} `(13.11.2)'
+@item @code{Ada.Unchecked_Deallocation} @emph{(13.11.2)}
This generic package allows explicit freeing of storage previously
allocated by use of an allocator.
-@item @code{Ada.Wide_Text_IO} `(A.11)'
+@item @code{Ada.Wide_Text_IO} @emph{(A.11)}
This package is similar to @code{Ada.Text_IO}, except that the external
file supports wide character representations, and the internal types are
@@ -21500,7 +21504,7 @@ file supports wide character representations, and the internal types are
and @code{String}. The corresponding set of nested packages and child
packages are defined.
-@item @code{Ada.Wide_Wide_Text_IO} `(A.11)'
+@item @code{Ada.Wide_Wide_Text_IO} @emph{(A.11)}
This package is similar to @code{Ada.Text_IO}, except that the external
file supports wide character representations, and the internal types are
@@ -22036,7 +22040,7 @@ Encoding
@item
-`h'
+@emph{h}
@tab
@@ -22044,7 +22048,7 @@ Hex ESC encoding
@item
-`u'
+@emph{u}
@tab
@@ -22052,7 +22056,7 @@ Upper half encoding
@item
-`s'
+@emph{s}
@tab
@@ -22060,7 +22064,7 @@ Shift-JIS encoding
@item
-`e'
+@emph{e}
@tab
@@ -22068,7 +22072,7 @@ EUC Encoding
@item
-`8'
+@emph{8}
@tab
@@ -22076,7 +22080,7 @@ UTF-8 encoding
@item
-`b'
+@emph{b}
@tab
@@ -22099,7 +22103,7 @@ being brackets encoding if no coding method was specified with -gnatW).
@table @asis
-@item `Hex Coding'
+@item @emph{Hex Coding}
In this encoding, a wide character is represented by a five character
sequence:
@@ -22122,7 +22126,7 @@ example, ESC A345 is used to represent the wide character with code
@table @asis
-@item `Upper Half Coding'
+@item @emph{Upper Half Coding}
The wide character with encoding 16#abcd#, where the upper bit is on
(i.e., a is in the range 8-F) is represented as two bytes 16#ab# and
@@ -22130,7 +22134,7 @@ The wide character with encoding 16#abcd#, where the upper bit is on
not required to be in the upper half. This method can be also used for
shift-JIS or EUC where the internal coding matches the external coding.
-@item `Shift JIS Coding'
+@item @emph{Shift JIS Coding}
A wide character is represented by a two character sequence 16#ab# and
16#cd#, with the restrictions described for upper half encoding as
@@ -22139,7 +22143,7 @@ character according to the standard algorithm for Shift-JIS
conversion. Only characters defined in the JIS code set table can be
used with this encoding method.
-@item `EUC Coding'
+@item @emph{EUC Coding}
A wide character is represented by a two character sequence 16#ab# and
16#cd#, with both characters being in the upper half. The internal
@@ -22147,7 +22151,7 @@ character code is the corresponding JIS character according to the EUC
encoding algorithm. Only characters defined in the JIS code set table
can be used with this encoding method.
-@item `UTF-8 Coding'
+@item @emph{UTF-8 Coding}
A wide character is represented using
UCS Transformation Format 8 (UTF-8) as defined in Annex R of ISO
@@ -22177,7 +22181,7 @@ will all invalid UTF-8 sequences.)
@table @asis
-@item `Brackets Coding'
+@item @emph{Brackets Coding}
In this encoding, a wide character is represented by the following eight
character sequence:
@@ -22318,7 +22322,7 @@ Encoding
@item
-`h'
+@emph{h}
@tab
@@ -22326,7 +22330,7 @@ Hex ESC encoding
@item
-`u'
+@emph{u}
@tab
@@ -22334,7 +22338,7 @@ Upper half encoding
@item
-`s'
+@emph{s}
@tab
@@ -22342,7 +22346,7 @@ Shift-JIS encoding
@item
-`e'
+@emph{e}
@tab
@@ -22350,7 +22354,7 @@ EUC Encoding
@item
-`8'
+@emph{8}
@tab
@@ -22358,7 +22362,7 @@ UTF-8 encoding
@item
-`b'
+@emph{b}
@tab
@@ -22381,7 +22385,7 @@ being brackets encoding if no coding method was specified with -gnatW).
@table @asis
-@item `UTF-8 Coding'
+@item @emph{UTF-8 Coding}
A wide character is represented using
UCS Transformation Format 8 (UTF-8) as defined in Annex R of ISO
@@ -22409,7 +22413,7 @@ characters.
@table @asis
-@item `Brackets Coding'
+@item @emph{Brackets Coding}
In this encoding, a wide wide character is represented by the following eight
character sequence if is in wide character range
@@ -22639,11 +22643,11 @@ variable. And if not set @code{utf8} is assumed.
@table @asis
-@item `CP_ACP'
+@item @emph{CP_ACP}
The current system Windows ANSI code page.
-@item `CP_UTF8'
+@item @emph{CP_UTF8}
UTF-8 encoding
@end table
@@ -22666,19 +22670,19 @@ The possible values are those supported on Windows:
@table @asis
-@item `TEXT'
+@item @emph{TEXT}
Translated text mode
-@item `WTEXT'
+@item @emph{WTEXT}
Translated unicode encoding
-@item `U16TEXT'
+@item @emph{U16TEXT}
Unicode 16-bit encoding
-@item `U8TEXT'
+@item @emph{U8TEXT}
Unicode 8-bit encoding
@end table
@@ -22707,11 +22711,11 @@ using the mode shown in the following table:
@tab
-`OPEN'
+@strong{OPEN}
@tab
-`CREATE'
+@strong{CREATE}
@item
@@ -23912,7 +23916,7 @@ C @code{timeval} format.
This package implements the CRC-32 algorithm. For a full description
of this algorithm see
-`Computation of Cyclic Redundancy Checks via Table Look-Up',
+@emph{Computation of Cyclic Redundancy Checks via Table Look-Up},
@cite{Communications of the ACM}, Vol. 31 No. 8, pp. 1008-1013,
Aug. 1988. Sarwate, D.V.
@@ -25582,7 +25586,7 @@ See @ref{7,,Implementation Defined Pragmas}, for more details.
@table @asis
-@item @code{pragma CPP_Class ([Entity =>] @var{LOCAL_NAME})}
+@item @code{pragma CPP_Class ([Entity =>] @emph{LOCAL_NAME})}
The argument denotes an entity in the current declarative region that is
declared as a tagged or untagged record type. It indicates that the type
@@ -25593,7 +25597,7 @@ Note: Pragma @code{CPP_Class} is currently obsolete. It is supported
for backward compatibility but its functionality is available
using pragma @code{Import} with @code{Convention} = @code{CPP}.
-@item @code{pragma CPP_Constructor ([Entity =>] @var{LOCAL_NAME})}
+@item @code{pragma CPP_Constructor ([Entity =>] @emph{LOCAL_NAME})}
This pragma identifies an imported function (imported in the usual way
with pragma @code{Import}) as corresponding to a C++ constructor.
@@ -25677,30 +25681,30 @@ GNAT implements all of these annexes:
@table @asis
-@item `Systems Programming (Annex C)'
+@item @emph{Systems Programming (Annex C)}
The Systems Programming Annex is fully implemented.
-@item `Real-Time Systems (Annex D)'
+@item @emph{Real-Time Systems (Annex D)}
The Real-Time Systems Annex is fully implemented.
-@item `Distributed Systems (Annex E)'
+@item @emph{Distributed Systems (Annex E)}
Stub generation is fully implemented in the GNAT compiler. In addition,
a complete compatible PCS is available as part of the GLADE system,
a separate product. When the two
products are used in conjunction, this annex is fully implemented.
-@item `Information Systems (Annex F)'
+@item @emph{Information Systems (Annex F)}
The Information Systems annex is fully implemented.
-@item `Numerics (Annex G)'
+@item @emph{Numerics (Annex G)}
The Numerics Annex is fully implemented.
-@item `Safety and Security / High-Integrity Systems (Annex H)'
+@item @emph{Safety and Security / High-Integrity Systems (Annex H)}
The Safety and Security Annex (termed the High-Integrity Systems Annex
in Ada 2005) is fully implemented.
@@ -25815,7 +25819,7 @@ No support is provided for GNU C’s symbolic names for input parameters.
If there are no input operands, this argument may either be omitted, or
explicitly given as @code{No_Input_Operands}. The fourth argument, not
present in the above example, is a list of register names, called the
-`clobber' argument. This argument, if given, must be a static string
+@emph{clobber} argument. This argument, if given, must be a static string
expression, and is a space or comma separated list of names of registers
that must be considered destroyed as a result of the @code{Asm} call. If
this argument is the null string (the default value), then the code
@@ -25824,7 +25828,7 @@ In addition to registers, the special clobbers @code{memory} and
@code{cc} as described in the GNU C docs are both supported.
The fifth argument, not present in the above example, called the
-`volatile' argument, is by default @code{False}. It can be set to
+@emph{volatile} argument, is by default @code{False}. It can be set to
the literal value @code{True} to indicate to the code generator that all
optimizations with respect to the instruction specified should be
suppressed, and in particular an instruction that has outputs
@@ -25995,13 +25999,13 @@ scheduling policy states:
@quotation
-`When the active priority of a ready task that is not running
+@emph{When the active priority of a ready task that is not running
changes, or the setting of its base priority takes effect, the
task is removed from the ready queue for its old active priority
and is added at the tail of the ready queue for its new active
priority, except in the case where the active priority is lowered
due to the loss of inherited priority, in which case the task is
-added at the head of the ready queue for its new active priority.'
+added at the head of the ready queue for its new active priority.}
@end quotation
While most kernels do put tasks at the end of the priority queue when
@@ -26090,7 +26094,7 @@ extensive usage as follows:
@table @asis
-@item `Communication between separate programs'
+@item @emph{Communication between separate programs}
This allows separate programs to access the data in passive
partitions, using protected objects for synchronization where
@@ -26100,7 +26104,7 @@ running on different machines with different architectures
(e.g., different endianness) to communicate via the data in
a passive partition.
-@item `Persistence between program runs'
+@item @emph{Persistence between program runs}
The data in a passive package can persist from one run of a
program to another, so that a later program sees the final
@@ -26354,7 +26358,7 @@ end T;
Word : Rec;
@end example
-Such an object is said to be `unconstrained'.
+Such an object is said to be @emph{unconstrained}.
The discriminant of the object
can be modified by a full assignment to the object, as long as it preserves the
relation between the value of the discriminant, and the value of the components
@@ -26407,7 +26411,7 @@ index type of ‘reasonable’ range so that unconstrained objects are not too
large.
One final wrinkle: if the object is declared to be @code{aliased}, or if it is
-created in the heap by means of an allocator, then it is `not'
+created in the heap by means of an allocator, then it is @emph{not}
unconstrained:
it is constrained by the default values of the discriminants, and those values
cannot be modified by full assignment. This is because in the presence of
@@ -26450,15 +26454,15 @@ perform this check by default).
Strict conformance to the Ada Reference Manual can be achieved by adding two
compiler options for dynamic checks for access-before-elaboration on subprogram
-calls and generic instantiations (`-gnatE'), and stack overflow checking
-(`-fstack-check').
+calls and generic instantiations (@emph{-gnatE}), and stack overflow checking
+(@emph{-fstack-check}).
Note that the result of a floating point arithmetic operation in overflow and
invalid situations, when the @code{Machine_Overflows} attribute of the result
type is @code{False}, is to generate IEEE NaN and infinite values. This is the
case for machines compliant with the IEEE floating-point standard, but on
machines that are not fully compliant with this standard, such as Alpha, the
-`-mieee' compiler flag must be used for achieving IEEE confirming
+@emph{-mieee} compiler flag must be used for achieving IEEE confirming
behavior (although at the cost of a significant performance penalty), so
infinite and NaN values are properly generated.
@@ -26480,7 +26484,7 @@ infinite and NaN values are properly generated.
This chapter contains a complete list of Ada 2012 features that have been
implemented.
Generally, these features are only
-available if the `-gnat12' (Ada 2012 features enabled) option is set,
+available if the @emph{-gnat12} (Ada 2012 features enabled) option is set,
which is the default behavior,
or if the configuration pragma @code{Ada_2012} is used.
@@ -26512,7 +26516,7 @@ A complete description of the AIs may be found in
@itemize *
@item
-`AI-0176 Quantified expressions (2010-09-29)'
+@emph{AI-0176 Quantified expressions (2010-09-29)}
Both universally and existentially quantified expressions are implemented.
They use the new syntax for iterators proposed in AI05-139-2, as well as
@@ -26527,9 +26531,9 @@ RM References: 1.01.04 (12) 2.09 (2/2) 4.04 (7) 4.05.09 (0)
@itemize *
@item
-`AI-0079 Allow other_format characters in source (2010-07-10)'
+@emph{AI-0079 Allow other_format characters in source (2010-07-10)}
-Wide characters in the unicode category `other_format' are now allowed in
+Wide characters in the unicode category @emph{other_format} are now allowed in
source programs between tokens, but not within a token such as an identifier.
RM References: 2.01 (4/2) 2.02 (7)
@@ -26541,9 +26545,9 @@ RM References: 2.01 (4/2) 2.02 (7)
@itemize *
@item
-`AI-0091 Do not allow other_format in identifiers (0000-00-00)'
+@emph{AI-0091 Do not allow other_format in identifiers (0000-00-00)}
-Wide characters in the unicode category `other_format' are not permitted
+Wide characters in the unicode category @emph{other_format} are not permitted
within an identifier, since this can be a security problem. The error
message for this case has been improved to be more specific, but GNAT has
never allowed such characters to appear in identifiers.
@@ -26557,7 +26561,7 @@ RM References: 2.03 (3.1/2) 2.03 (4/2) 2.03 (5/2) 2.03 (5.1/2) 2.03 (5.
@itemize *
@item
-`AI-0100 Placement of pragmas (2010-07-01)'
+@emph{AI-0100 Placement of pragmas (2010-07-01)}
This AI is an earlier version of AI-163. It simplifies the rules
for legal placement of pragmas. In the case of lists that allow pragmas, if
@@ -26572,7 +26576,7 @@ RM References: 2.08 (7)
@itemize *
@item
-`AI-0163 Pragmas in place of null (2010-07-01)'
+@emph{AI-0163 Pragmas in place of null (2010-07-01)}
A statement sequence may be composed entirely of pragmas. It is no longer
necessary to add a dummy @code{null} statement to make the sequence legal.
@@ -26586,7 +26590,7 @@ RM References: 2.08 (7) 2.08 (16)
@itemize *
@item
-`AI-0080 ‘View of’ not needed if clear from context (0000-00-00)'
+@emph{AI-0080 ‘View of’ not needed if clear from context (0000-00-00)}
This is an editorial change only, described as non-testable in the AI.
@@ -26599,7 +26603,7 @@ RM References: 3.01 (7)
@itemize *
@item
-`AI-0183 Aspect specifications (2010-08-16)'
+@emph{AI-0183 Aspect specifications (2010-08-16)}
Aspect specifications have been fully implemented except for pre and post-
conditions, and type invariants, which have their own separate AI’s. All
@@ -26957,7 +26961,7 @@ RM References: 3.02.01 (3) 3.02.02 (2) 3.03.01 (2/2) 3.08 (6)
@itemize *
@item
-`AI-0128 Inequality is a primitive operation (0000-00-00)'
+@emph{AI-0128 Inequality is a primitive operation (0000-00-00)}
If an equality operator (“=”) is declared for a type, then the implicitly
declared inequality operator (“/=”) is a primitive operation of the type.
@@ -26973,7 +26977,7 @@ RM References: 3.02.03 (6) 6.06 (6)
@itemize *
@item
-`AI-0003 Qualified expressions as names (2010-07-11)'
+@emph{AI-0003 Qualified expressions as names (2010-07-11)}
In Ada 2012, a qualified expression is considered to be syntactically a name,
meaning that constructs such as @code{A'(F(X)).B} are now legal. This is
@@ -26989,7 +26993,7 @@ RM References: 3.03 (11) 3.03 (21) 4.01 (2) 4.04 (7) 4.07 (3)
@itemize *
@item
-`AI-0120 Constant instance of protected object (0000-00-00)'
+@emph{AI-0120 Constant instance of protected object (0000-00-00)}
This is an RM editorial change only. The section that lists objects that are
constant failed to include the current instance of a protected object
@@ -27005,7 +27009,7 @@ RM References: 3.03 (21)
@itemize *
@item
-`AI-0008 General access to constrained objects (0000-00-00)'
+@emph{AI-0008 General access to constrained objects (0000-00-00)}
The wording in the RM implied that if you have a general access to a
constrained object, it could be used to modify the discriminants. This was
@@ -27021,7 +27025,7 @@ RM References: 3.03 (23) 3.10.02 (26/2) 4.01 (9) 6.04.01 (17) 8.05.01 (
@itemize *
@item
-`AI-0093 Additional rules use immutably limited (0000-00-00)'
+@emph{AI-0093 Additional rules use immutably limited (0000-00-00)}
This is an editorial change only, to make more widespread use of the Ada 2012
‘immutably limited’.
@@ -27035,7 +27039,7 @@ RM References: 3.03 (23.4/3)
@itemize *
@item
-`AI-0096 Deriving from formal private types (2010-07-20)'
+@emph{AI-0096 Deriving from formal private types (2010-07-20)}
In general it is illegal for a type derived from a formal limited type to be
nonlimited. This AI makes an exception to this rule: derivation is legal
@@ -27052,7 +27056,7 @@ RM References: 3.04 (5.1/2) 6.02 (7)
@itemize *
@item
-`AI-0181 Soft hyphen is a non-graphic character (2010-07-23)'
+@emph{AI-0181 Soft hyphen is a non-graphic character (2010-07-23)}
From Ada 2005 on, soft hyphen is considered a non-graphic character, which
means that it has a special name (@code{SOFT_HYPHEN}) in conjunction with the
@@ -27069,7 +27073,7 @@ RM References: 3.05.02 (2/2) A.01 (35/2) A.03.03 (21)
@itemize *
@item
-`AI-0182 Additional forms for' @code{Character'Value} `(0000-00-00)'
+@emph{AI-0182 Additional forms for} @code{Character'Value} @emph{(0000-00-00)}
This AI allows @code{Character'Value} to accept the string @code{'?'} where
@code{?} is any character including non-graphic control characters. GNAT has
@@ -27087,7 +27091,7 @@ RM References: 3.05 (56/2)
@itemize *
@item
-`AI-0214 Defaulted discriminants for limited tagged (2010-10-01)'
+@emph{AI-0214 Defaulted discriminants for limited tagged (2010-10-01)}
Ada 2012 relaxes the restriction that forbids discriminants of tagged types
to have default expressions by allowing them when the type is limited. It
@@ -27103,7 +27107,7 @@ RM References: 3.07 (9.1/2) 3.07.02 (3)
@itemize *
@item
-`AI-0102 Some implicit conversions are illegal (0000-00-00)'
+@emph{AI-0102 Some implicit conversions are illegal (0000-00-00)}
It is illegal to assign an anonymous access constant to an anonymous access
variable. The RM did not have a clear rule to prevent this, but GNAT has
@@ -27118,7 +27122,7 @@ RM References: 3.07 (16) 3.07.01 (9) 6.04.01 (6) 8.06 (27/2)
@itemize *
@item
-`AI-0158 Generalizing membership tests (2010-09-16)'
+@emph{AI-0158 Generalizing membership tests (2010-09-16)}
This AI extends the syntax of membership tests to simplify complex conditions
that can be expressed as membership in a subset of values of any type. It
@@ -27134,7 +27138,7 @@ RM References: 3.08.01 (5) 4.04 (3) 4.05.02 (3) 4.05.02 (5) 4.05.02 (27
@itemize *
@item
-`AI-0173 Testing if tags represent abstract types (2010-07-03)'
+@emph{AI-0173 Testing if tags represent abstract types (2010-07-03)}
The function @code{Ada.Tags.Type_Is_Abstract} returns @code{True} if invoked
with the tag of an abstract type, and @code{False} otherwise.
@@ -27148,7 +27152,7 @@ RM References: 3.09 (7.4/2) 3.09 (12.4/2)
@itemize *
@item
-`AI-0076 function with controlling result (0000-00-00)'
+@emph{AI-0076 function with controlling result (0000-00-00)}
This is an editorial change only. The RM defines calls with controlling
results, but uses the term ‘function with controlling result’ without an
@@ -27163,7 +27167,7 @@ RM References: 3.09.02 (2/2)
@itemize *
@item
-`AI-0126 Dispatching with no declared operation (0000-00-00)'
+@emph{AI-0126 Dispatching with no declared operation (0000-00-00)}
This AI clarifies dispatching rules, and simply confirms that dispatching
executes the operation of the parent type when there is no explicitly or
@@ -27179,7 +27183,7 @@ RM References: 3.09.02 (20/2) 3.09.02 (20.1/2) 3.09.02 (20.2/2)
@itemize *
@item
-`AI-0097 Treatment of abstract null extension (2010-07-19)'
+@emph{AI-0097 Treatment of abstract null extension (2010-07-19)}
The RM as written implied that in some cases it was possible to create an
object of an abstract type, by having an abstract extension inherit a non-
@@ -27195,7 +27199,7 @@ RM References: 3.09.03 (4/2)
@itemize *
@item
-`AI-0203 Extended return cannot be abstract (0000-00-00)'
+@emph{AI-0203 Extended return cannot be abstract (0000-00-00)}
A return_subtype_indication cannot denote an abstract subtype. GNAT has never
permitted such usage.
@@ -27209,7 +27213,7 @@ RM References: 3.09.03 (8/3)
@itemize *
@item
-`AI-0198 Inheriting abstract operators (0000-00-00)'
+@emph{AI-0198 Inheriting abstract operators (0000-00-00)}
This AI resolves a conflict between two rules involving inherited abstract
operations and predefined operators. If a derived numeric type inherits
@@ -27225,7 +27229,7 @@ RM References: 3.09.03 (4/3)
@itemize *
@item
-`AI-0073 Functions returning abstract types (2010-07-10)'
+@emph{AI-0073 Functions returning abstract types (2010-07-10)}
This AI covers a number of issues regarding returning abstract types. In
particular generic functions cannot have abstract result types or access
@@ -27243,7 +27247,7 @@ RM References: 3.09.03 (8) 3.09.03 (10) 6.05 (8/2)
@itemize *
@item
-`AI-0070 Elaboration of interface types (0000-00-00)'
+@emph{AI-0070 Elaboration of interface types (0000-00-00)}
This is an editorial change only, there are no testable consequences short of
checking for the absence of generated code for an interface declaration.
@@ -27257,7 +27261,7 @@ RM References: 3.09.04 (18/2)
@itemize *
@item
-`AI-0208 Characteristics of incomplete views (0000-00-00)'
+@emph{AI-0208 Characteristics of incomplete views (0000-00-00)}
The wording in the Ada 2005 RM concerning characteristics of incomplete views
was incorrect and implied that some programs intended to be legal were now
@@ -27273,7 +27277,7 @@ RM References: 3.10.01 (2.4/2) 3.10.01 (2.6/2)
@itemize *
@item
-`AI-0162 Incomplete type completed by partial view (2010-09-15)'
+@emph{AI-0162 Incomplete type completed by partial view (2010-09-15)}
Incomplete types are made more useful by allowing them to be completed by
private types and private extensions.
@@ -27287,7 +27291,7 @@ RM References: 3.10.01 (2.5/2) 3.10.01 (2.6/2) 3.10.01 (3) 3.10.01 (4/2)
@itemize *
@item
-`AI-0098 Anonymous subprogram access restrictions (0000-00-00)'
+@emph{AI-0098 Anonymous subprogram access restrictions (0000-00-00)}
An unintentional omission in the RM implied some inconsistent restrictions on
the use of anonymous access to subprogram values. These restrictions were not
@@ -27302,7 +27306,7 @@ RM References: 3.10.01 (6) 3.10.01 (9.2/2)
@itemize *
@item
-`AI-0199 Aggregate with anonymous access components (2010-07-14)'
+@emph{AI-0199 Aggregate with anonymous access components (2010-07-14)}
A choice list in a record aggregate can include several components of
(distinct) anonymous access types as long as they have matching designated
@@ -27317,7 +27321,7 @@ RM References: 4.03.01 (16)
@itemize *
@item
-`AI-0220 Needed components for aggregates (0000-00-00)'
+@emph{AI-0220 Needed components for aggregates (0000-00-00)}
This AI addresses a wording problem in the RM that appears to permit some
complex cases of aggregates with nonstatic discriminants. GNAT has always
@@ -27332,7 +27336,7 @@ RM References: 4.03.01 (17)
@itemize *
@item
-`AI-0147 Conditional expressions (2009-03-29)'
+@emph{AI-0147 Conditional expressions (2009-03-29)}
Conditional expressions are permitted. The form of such an expression is:
@@ -27341,10 +27345,10 @@ Conditional expressions are permitted. The form of such an expression is:
@end example
The parentheses can be omitted in contexts where parentheses are present
-anyway, such as subprogram arguments and pragma arguments. If the `else'
-clause is omitted, `else' `True' is assumed;
+anyway, such as subprogram arguments and pragma arguments. If the @strong{else}
+clause is omitted, @strong{else} @emph{True} is assumed;
thus @code{(if A then B)} is a way to conveniently represent
-`(A implies B)' in standard logic.
+@emph{(A implies B)} in standard logic.
RM References: 4.03.03 (15) 4.04 (1) 4.04 (7) 4.05.07 (0) 4.07 (2)
4.07 (3) 4.09 (12) 4.09 (33) 5.03 (3) 5.03 (4) 7.05 (2.1/2)
@@ -27356,7 +27360,7 @@ RM References: 4.03.03 (15) 4.04 (1) 4.04 (7) 4.05.07 (0) 4.07 (2)
@itemize *
@item
-`AI-0037 Out-of-range box associations in aggregate (0000-00-00)'
+@emph{AI-0037 Out-of-range box associations in aggregate (0000-00-00)}
This AI confirms that an association of the form @code{Indx => <>} in an
array aggregate must raise @code{Constraint_Error} if @code{Indx}
@@ -27373,7 +27377,7 @@ RM References: 4.03.03 (29)
@itemize *
@item
-`AI-0123 Composability of equality (2010-04-13)'
+@emph{AI-0123 Composability of equality (2010-04-13)}
Equality of untagged record composes, so that the predefined equality for a
composite type that includes a component of some untagged record type
@@ -27399,7 +27403,7 @@ RM References: 4.05.02 (9.7/2) 4.05.02 (14) 4.05.02 (15) 4.05.02 (24)
@itemize *
@item
-`AI-0088 The value of exponentiation (0000-00-00)'
+@emph{AI-0088 The value of exponentiation (0000-00-00)}
This AI clarifies the equivalence rule given for the dynamic semantics of
exponentiation: the value of the operation can be obtained by repeated
@@ -27416,7 +27420,7 @@ RM References: 4.05.06 (11)
@itemize *
@item
-`AI-0188 Case expressions (2010-01-09)'
+@emph{AI-0188 Case expressions (2010-01-09)}
Case expressions are permitted. This allows use of constructs such as:
@@ -27433,11 +27437,11 @@ RM References: 4.05.07 (0) 4.05.08 (0) 4.09 (12) 4.09 (33)
@itemize *
@item
-`AI-0104 Null exclusion and uninitialized allocator (2010-07-15)'
+@emph{AI-0104 Null exclusion and uninitialized allocator (2010-07-15)}
The assignment @code{Ptr := new not null Some_Ptr;} will raise
@code{Constraint_Error} because the default value of the allocated object is
-`null'. This useless construct is illegal in Ada 2012.
+@strong{null}. This useless construct is illegal in Ada 2012.
RM References: 4.08 (2)
@end itemize
@@ -27448,7 +27452,7 @@ RM References: 4.08 (2)
@itemize *
@item
-`AI-0157 Allocation/Deallocation from empty pool (2010-07-11)'
+@emph{AI-0157 Allocation/Deallocation from empty pool (2010-07-11)}
Allocation and Deallocation from an empty storage pool (i.e. allocation or
deallocation of a pointer for which a static storage size clause of zero
@@ -27464,7 +27468,7 @@ RM References: 4.08 (5.3/2) 13.11.02 (4) 13.11.02 (17)
@itemize *
@item
-`AI-0179 Statement not required after label (2010-04-10)'
+@emph{AI-0179 Statement not required after label (2010-04-10)}
It is not necessary to have a statement following a label, so a label
can appear at the end of a statement sequence without the need for putting a
@@ -27480,7 +27484,7 @@ RM References: 5.01 (2)
@itemize *
@item
-`AI-0139-2 Syntactic sugar for iterators (2010-09-29)'
+@emph{AI-0139-2 Syntactic sugar for iterators (2010-09-29)}
The new syntax for iterating over arrays and containers is now implemented.
Iteration over containers is for now limited to read-only iterators. Only
@@ -27495,7 +27499,7 @@ RM References: 5.05
@itemize *
@item
-`AI-0134 Profiles must match for full conformance (0000-00-00)'
+@emph{AI-0134 Profiles must match for full conformance (0000-00-00)}
For full conformance, the profiles of anonymous-access-to-subprogram
parameters must match. GNAT has always enforced this rule.
@@ -27509,7 +27513,7 @@ RM References: 6.03.01 (18)
@itemize *
@item
-`AI-0207 Mode conformance and access constant (0000-00-00)'
+@emph{AI-0207 Mode conformance and access constant (0000-00-00)}
This AI confirms that access_to_constant indication must match for mode
conformance. This was implemented in GNAT when the qualifier was originally
@@ -27524,7 +27528,7 @@ RM References: 6.03.01 (16/2)
@itemize *
@item
-`AI-0046 Null exclusion match for full conformance (2010-07-17)'
+@emph{AI-0046 Null exclusion match for full conformance (2010-07-17)}
For full conformance, in the case of access parameters, the null exclusion
must match (either both or neither must have @code{not null}).
@@ -27538,7 +27542,7 @@ RM References: 6.03.02 (18)
@itemize *
@item
-`AI-0118 The association of parameter associations (0000-00-00)'
+@emph{AI-0118 The association of parameter associations (0000-00-00)}
This AI clarifies the rules for named associations in subprogram calls and
generic instantiations. The rules have been in place since Ada 83.
@@ -27552,7 +27556,7 @@ RM References: 6.04.01 (2) 12.03 (9)
@itemize *
@item
-`AI-0196 Null exclusion tests for out parameters (0000-00-00)'
+@emph{AI-0196 Null exclusion tests for out parameters (0000-00-00)}
Null exclusion checks are not made for @code{out} parameters when
evaluating the actual parameters. GNAT has never generated these checks.
@@ -27566,9 +27570,9 @@ RM References: 6.04.01 (13)
@itemize *
@item
-`AI-0015 Constant return objects (0000-00-00)'
+@emph{AI-0015 Constant return objects (0000-00-00)}
-The return object declared in an `extended_return_statement' may be
+The return object declared in an @emph{extended_return_statement} may be
declared constant. This was always intended, and GNAT has always allowed it.
RM References: 6.05 (2.1/2) 3.03 (10/2) 3.03 (21) 6.05 (5/2)
@@ -27581,7 +27585,7 @@ RM References: 6.05 (2.1/2) 3.03 (10/2) 3.03 (21) 6.05 (5/2)
@itemize *
@item
-`AI-0032 Extended return for class-wide functions (0000-00-00)'
+@emph{AI-0032 Extended return for class-wide functions (0000-00-00)}
If a function returns a class-wide type, the object of an extended return
statement can be declared with a specific type that is covered by the class-
@@ -27599,7 +27603,7 @@ RM References: 6.05 (5.2/2) 6.05 (5.3/2) 6.05 (5.6/2) 6.05 (5.8/2)
@itemize *
@item
-`AI-0103 Static matching for extended return (2010-07-23)'
+@emph{AI-0103 Static matching for extended return (2010-07-23)}
If the return subtype of a function is an elementary type or a constrained
type, the subtype indication in an extended return statement must match
@@ -27614,7 +27618,7 @@ RM References: 6.05 (5.2/2)
@itemize *
@item
-`AI-0058 Abnormal completion of an extended return (0000-00-00)'
+@emph{AI-0058 Abnormal completion of an extended return (0000-00-00)}
The RM had some incorrect wording implying wrong treatment of abnormal
completion in an extended return. GNAT has always implemented the intended
@@ -27629,7 +27633,7 @@ RM References: 6.05 (22/2)
@itemize *
@item
-`AI-0050 Raising Constraint_Error early for function call (0000-00-00)'
+@emph{AI-0050 Raising Constraint_Error early for function call (0000-00-00)}
The implementation permissions for raising @code{Constraint_Error} early on a function call
when it was clear an exception would be raised were over-permissive and allowed
@@ -27645,7 +27649,7 @@ RM References: 6.05 (24/2)
@itemize *
@item
-`AI-0125 Nonoverridable operations of an ancestor (2010-09-28)'
+@emph{AI-0125 Nonoverridable operations of an ancestor (2010-09-28)}
In Ada 2012, the declaration of a primitive operation of a type extension
or private extension can also override an inherited primitive that is not
@@ -27660,7 +27664,7 @@ RM References: 7.03.01 (6) 8.03 (23) 8.03.01 (5/2) 8.03.01 (6/2)
@itemize *
@item
-`AI-0062 Null exclusions and deferred constants (0000-00-00)'
+@emph{AI-0062 Null exclusions and deferred constants (0000-00-00)}
A full constant may have a null exclusion even if its associated deferred
constant does not. GNAT has always allowed this.
@@ -27674,7 +27678,7 @@ RM References: 7.04 (6/2) 7.04 (7.1/2)
@itemize *
@item
-`AI-0178 Incomplete views are limited (0000-00-00)'
+@emph{AI-0178 Incomplete views are limited (0000-00-00)}
This AI clarifies the role of incomplete views and plugs an omission in the
RM. GNAT always correctly restricted the use of incomplete views and types.
@@ -27688,7 +27692,7 @@ RM References: 7.05 (3/2) 7.05 (6/2)
@itemize *
@item
-`AI-0087 Actual for formal nonlimited derived type (2010-07-15)'
+@emph{AI-0087 Actual for formal nonlimited derived type (2010-07-15)}
The actual for a formal nonlimited derived type cannot be limited. In
particular, a formal derived type that extends a limited interface but which
@@ -27703,7 +27707,7 @@ RM References: 7.05 (5/2) 12.05.01 (5.1/2)
@itemize *
@item
-`AI-0099 Tag determines whether finalization needed (0000-00-00)'
+@emph{AI-0099 Tag determines whether finalization needed (0000-00-00)}
This AI clarifies that ‘needs finalization’ is part of dynamic semantics,
and therefore depends on the run-time characteristics of an object (i.e. its
@@ -27719,7 +27723,7 @@ RM References: 7.06.01 (6) 7.06.01 (7) 7.06.01 (8) 7.06.01 (9/2)
@itemize *
@item
-`AI-0064 Redundant finalization rule (0000-00-00)'
+@emph{AI-0064 Redundant finalization rule (0000-00-00)}
This is an editorial change only. The intended behavior is already checked
by an existing ACATS test, which GNAT has always executed correctly.
@@ -27733,7 +27737,7 @@ RM References: 7.06.01 (17.1/1)
@itemize *
@item
-`AI-0026 Missing rules for Unchecked_Union (2010-07-07)'
+@emph{AI-0026 Missing rules for Unchecked_Union (2010-07-07)}
Record representation clauses concerning Unchecked_Union types cannot mention
the discriminant of the type. The type of a component declared in the variant
@@ -27752,7 +27756,7 @@ RM References: 7.06 (9.4/2) B.03.03 (9/2) B.03.03 (10/2)
@itemize *
@item
-`AI-0205 Extended return declares visible name (0000-00-00)'
+@emph{AI-0205 Extended return declares visible name (0000-00-00)}
This AI corrects a simple omission in the RM. Return objects have always
been visible within an extended return statement.
@@ -27766,7 +27770,7 @@ RM References: 8.03 (17)
@itemize *
@item
-`AI-0042 Overriding versus implemented-by (0000-00-00)'
+@emph{AI-0042 Overriding versus implemented-by (0000-00-00)}
This AI fixes a wording gap in the RM. An operation of a synchronized
interface can be implemented by a protected or task entry, but the abstract
@@ -27783,7 +27787,7 @@ RM References: 9.01 (9.2/2) 9.04 (11.1/2)
@itemize *
@item
-`AI-0030 Requeue on synchronized interfaces (2010-07-19)'
+@emph{AI-0030 Requeue on synchronized interfaces (2010-07-19)}
Requeue is permitted to a protected, synchronized or task interface primitive
providing it is known that the overriding operation is an entry. Otherwise
@@ -27802,7 +27806,7 @@ RM References: 9.05 (9) 9.05.04 (2) 9.05.04 (3) 9.05.04 (5)
@itemize *
@item
-`AI-0201 Independence of atomic object components (2010-07-22)'
+@emph{AI-0201 Independence of atomic object components (2010-07-22)}
If an Atomic object has a pragma @code{Pack} or a @code{Component_Size}
attribute, then individual components may not be addressable by independent
@@ -27821,7 +27825,7 @@ RM References: 9.10 (1/3) C.06 (22/2) C.06 (23/2)
@itemize *
@item
-`AI-0009 Pragma Independent[_Components] (2010-07-23)'
+@emph{AI-0009 Pragma Independent[_Components] (2010-07-23)}
This AI introduces the new pragmas @code{Independent} and
@code{Independent_Components},
@@ -27838,7 +27842,7 @@ C.06 (4) C.06 (6) C.06 (9) C.06 (13) C.06 (14)
@itemize *
@item
-`AI-0072 Task signalling using ‘Terminated (0000-00-00)'
+@emph{AI-0072 Task signalling using ‘Terminated (0000-00-00)}
This AI clarifies that task signalling for reading @code{'Terminated} only
occurs if the result is True. GNAT semantics has always been consistent with
@@ -27853,7 +27857,7 @@ RM References: 9.10 (6.1/1)
@itemize *
@item
-`AI-0108 Limited incomplete view and discriminants (0000-00-00)'
+@emph{AI-0108 Limited incomplete view and discriminants (0000-00-00)}
This AI confirms that an incomplete type from a limited view does not have
discriminants. This has always been the case in GNAT.
@@ -27867,7 +27871,7 @@ RM References: 10.01.01 (12.3/2)
@itemize *
@item
-`AI-0129 Limited views and incomplete types (0000-00-00)'
+@emph{AI-0129 Limited views and incomplete types (0000-00-00)}
This AI clarifies the description of limited views: a limited view of a
package includes only one view of a type that has an incomplete declaration
@@ -27884,7 +27888,7 @@ RM References: 10.01.01 (12.2/2) 10.01.01 (12.3/2)
@itemize *
@item
-`AI-0077 Limited withs and scope of declarations (0000-00-00)'
+@emph{AI-0077 Limited withs and scope of declarations (0000-00-00)}
This AI clarifies that a declaration does not include a context clause,
and confirms that it is illegal to have a context in which both a limited
@@ -27900,7 +27904,7 @@ RM References: 10.01.02 (12/2) 10.01.02 (21/2) 10.01.02 (22/2)
@itemize *
@item
-`AI-0122 Private with and children of generics (0000-00-00)'
+@emph{AI-0122 Private with and children of generics (0000-00-00)}
This AI clarifies the visibility of private children of generic units within
instantiations of a parent. GNAT has always handled this correctly.
@@ -27914,7 +27918,7 @@ RM References: 10.01.02 (12/2)
@itemize *
@item
-`AI-0040 Limited with clauses on descendant (0000-00-00)'
+@emph{AI-0040 Limited with clauses on descendant (0000-00-00)}
This AI confirms that a limited with clause in a child unit cannot name
an ancestor of the unit. This has always been checked in GNAT.
@@ -27928,7 +27932,7 @@ RM References: 10.01.02 (20/2)
@itemize *
@item
-`AI-0132 Placement of library unit pragmas (0000-00-00)'
+@emph{AI-0132 Placement of library unit pragmas (0000-00-00)}
This AI fills a gap in the description of library unit pragmas. The pragma
clearly must apply to a library unit, even if it does not carry the name
@@ -27943,7 +27947,7 @@ RM References: 10.01.05 (7)
@itemize *
@item
-`AI-0034 Categorization of limited views (0000-00-00)'
+@emph{AI-0034 Categorization of limited views (0000-00-00)}
The RM makes certain limited with clauses illegal because of categorization
considerations, when the corresponding normal with would be legal. This is
@@ -27958,7 +27962,7 @@ RM References: 10.02.01 (11/1) 10.02.01 (17/2)
@itemize *
@item
-`AI-0035 Inconsistencies with Pure units (0000-00-00)'
+@emph{AI-0035 Inconsistencies with Pure units (0000-00-00)}
This AI remedies some inconsistencies in the legality rules for Pure units.
Derived access types are legal in a pure unit (on the assumption that the
@@ -27975,7 +27979,7 @@ RM References: 10.02.01 (15.1/2) 10.02.01 (15.4/2) 10.02.01 (15.5/2) 10.0
@itemize *
@item
-`AI-0219 Pure permissions and limited parameters (2010-05-25)'
+@emph{AI-0219 Pure permissions and limited parameters (2010-05-25)}
This AI refines the rules for the cases with limited parameters which do not
allow the implementations to omit ‘redundant’. GNAT now properly conforms
@@ -27990,7 +27994,7 @@ RM References: 10.02.01 (18/2)
@itemize *
@item
-`AI-0043 Rules about raising exceptions (0000-00-00)'
+@emph{AI-0043 Rules about raising exceptions (0000-00-00)}
This AI covers various omissions in the RM regarding the raising of
exceptions. GNAT has always implemented the intended semantics.
@@ -28004,7 +28008,7 @@ RM References: 11.04.01 (10.1/2) 11 (2)
@itemize *
@item
-`AI-0200 Mismatches in formal package declarations (0000-00-00)'
+@emph{AI-0200 Mismatches in formal package declarations (0000-00-00)}
This AI plugs a gap in the RM which appeared to allow some obviously intended
illegal instantiations. GNAT has never allowed these instantiations.
@@ -28018,7 +28022,7 @@ RM References: 12.07 (16)
@itemize *
@item
-`AI-0112 Detection of duplicate pragmas (2010-07-24)'
+@emph{AI-0112 Detection of duplicate pragmas (2010-07-24)}
This AI concerns giving names to various representation aspects, but the
practical effect is simply to make the use of duplicate
@@ -28036,7 +28040,7 @@ RM References: 13.01 (8)
@itemize *
@item
-`AI-0106 No representation pragmas on generic formals (0000-00-00)'
+@emph{AI-0106 No representation pragmas on generic formals (0000-00-00)}
The RM appeared to allow representation pragmas on generic formal parameters,
but this was not intended, and GNAT has never permitted this usage.
@@ -28050,7 +28054,7 @@ RM References: 13.01 (9.1/1)
@itemize *
@item
-`AI-0012 Pack/Component_Size for aliased/atomic (2010-07-15)'
+@emph{AI-0012 Pack/Component_Size for aliased/atomic (2010-07-15)}
It is now illegal to give an inappropriate component size or a pragma
@code{Pack} that attempts to change the component size in the case of atomic
@@ -28066,7 +28070,7 @@ RM References: 13.02 (6.1/2) 13.02 (7) C.06 (10) C.06 (11) C.06 (21)
@itemize *
@item
-`AI-0039 Stream attributes cannot be dynamic (0000-00-00)'
+@emph{AI-0039 Stream attributes cannot be dynamic (0000-00-00)}
The RM permitted the use of dynamic expressions (such as @code{ptr.all})`
for stream attributes, but these were never useful and are now illegal. GNAT
@@ -28081,7 +28085,7 @@ RM References: 13.03 (4) 13.03 (6) 13.13.02 (38/2)
@itemize *
@item
-`AI-0095 Address of intrinsic subprograms (0000-00-00)'
+@emph{AI-0095 Address of intrinsic subprograms (0000-00-00)}
The prefix of @code{'Address} cannot statically denote a subprogram with
convention @code{Intrinsic}. The use of the @code{Address} attribute raises
@@ -28097,7 +28101,7 @@ RM References: 13.03 (11/1)
@itemize *
@item
-`AI-0116 Alignment of class-wide objects (0000-00-00)'
+@emph{AI-0116 Alignment of class-wide objects (0000-00-00)}
This AI requires that the alignment of a class-wide object be no greater
than the alignment of any type in the class. GNAT has always followed this
@@ -28112,7 +28116,7 @@ RM References: 13.03 (29) 13.11 (16)
@itemize *
@item
-`AI-0146 Type invariants (2009-09-21)'
+@emph{AI-0146 Type invariants (2009-09-21)}
Type invariants may be specified for private types using the aspect notation.
Aspect @code{Type_Invariant} may be specified for any private type,
@@ -28121,7 +28125,7 @@ only be specified for tagged types, and is inherited by any descendent of the
tagged types. The invariant is a boolean expression that is tested for being
true in the following situations: conversions to the private type, object
declarations for the private type that are default initialized, and
-[`in'] `out'
+[@strong{in}] @strong{out}
parameters and returned result on return from any primitive operation for
the type that is visible to a client.
GNAT defines the synonyms @code{Invariant} for @code{Type_Invariant} and
@@ -28136,7 +28140,7 @@ RM References: 13.03.03 (00)
@itemize *
@item
-`AI-0078 Relax Unchecked_Conversion alignment rules (0000-00-00)'
+@emph{AI-0078 Relax Unchecked_Conversion alignment rules (0000-00-00)}
In Ada 2012, compilers are required to support unchecked conversion where the
target alignment is a multiple of the source alignment. GNAT always supported
@@ -28152,7 +28156,7 @@ RM References: 13.09 (7)
@itemize *
@item
-`AI-0195 Invalid value handling is implementation defined (2010-07-03)'
+@emph{AI-0195 Invalid value handling is implementation defined (2010-07-03)}
The handling of invalid values is now designated to be implementation
defined. This is a documentation change only, requiring Annex M in the GNAT
@@ -28172,7 +28176,7 @@ RM References: 13.09.01 (10)
@itemize *
@item
-`AI-0193 Alignment of allocators (2010-09-16)'
+@emph{AI-0193 Alignment of allocators (2010-09-16)}
This AI introduces a new attribute @code{Max_Alignment_For_Allocation},
analogous to @code{Max_Size_In_Storage_Elements}, but for alignment instead
@@ -28188,7 +28192,7 @@ RM References: 13.11 (16) 13.11 (21) 13.11.01 (0) 13.11.01 (1)
@itemize *
@item
-`AI-0177 Parameterized expressions (2010-07-10)'
+@emph{AI-0177 Parameterized expressions (2010-07-10)}
The new Ada 2012 notion of parameterized expressions is implemented. The form
is:
@@ -28210,7 +28214,7 @@ RM References: 13.11.01 (3/2)
@itemize *
@item
-`AI-0033 Attach/Interrupt_Handler in generic (2010-07-24)'
+@emph{AI-0033 Attach/Interrupt_Handler in generic (2010-07-24)}
Neither of these two pragmas may appear within a generic template, because
the generic might be instantiated at other than the library level.
@@ -28224,7 +28228,7 @@ RM References: 13.11.02 (16) C.03.01 (7/2) C.03.01 (8/2)
@itemize *
@item
-`AI-0161 Restriction No_Default_Stream_Attributes (2010-09-11)'
+@emph{AI-0161 Restriction No_Default_Stream_Attributes (2010-09-11)}
A new restriction @code{No_Default_Stream_Attributes} prevents the use of any
of the default stream attributes for elementary types. If this restriction is
@@ -28240,7 +28244,7 @@ RM References: 13.12.01 (4/2) 13.13.02 (40/2) 13.13.02 (52/2)
@itemize *
@item
-`AI-0194 Value of Stream_Size attribute (0000-00-00)'
+@emph{AI-0194 Value of Stream_Size attribute (0000-00-00)}
The @code{Stream_Size} attribute returns the default number of bits in the
stream representation of the given type.
@@ -28257,7 +28261,7 @@ RM References: 13.13.02 (1.2/2)
@itemize *
@item
-`AI-0109 Redundant check in S’Class’Input (0000-00-00)'
+@emph{AI-0109 Redundant check in S’Class’Input (0000-00-00)}
This AI is an editorial change only. It removes the need for a tag check
that can never fail.
@@ -28271,7 +28275,7 @@ RM References: 13.13.02 (34/2)
@itemize *
@item
-`AI-0007 Stream read and private scalar types (0000-00-00)'
+@emph{AI-0007 Stream read and private scalar types (0000-00-00)}
The RM as written appeared to limit the possibilities of declaring read
attribute procedures for private scalar types. This limitation was not
@@ -28286,7 +28290,7 @@ RM References: 13.13.02 (50/2) 13.13.02 (51/2)
@itemize *
@item
-`AI-0065 Remote access types and external streaming (0000-00-00)'
+@emph{AI-0065 Remote access types and external streaming (0000-00-00)}
This AI clarifies the fact that all remote access types support external
streaming. This fixes an obvious oversight in the definition of the
@@ -28301,7 +28305,7 @@ RM References: 13.13.02 (52/2)
@itemize *
@item
-`AI-0019 Freezing of primitives for tagged types (0000-00-00)'
+@emph{AI-0019 Freezing of primitives for tagged types (0000-00-00)}
The RM suggests that primitive subprograms of a specific tagged type are
frozen when the tagged type is frozen. This would be an incompatible change
@@ -28317,7 +28321,7 @@ RM References: 13.14 (2) 13.14 (3/1) 13.14 (8.1/1) 13.14 (10) 13.14 (14
@itemize *
@item
-`AI-0017 Freezing and incomplete types (0000-00-00)'
+@emph{AI-0017 Freezing and incomplete types (0000-00-00)}
So-called ‘Taft-amendment types’ (i.e., types that are completed in package
bodies) are not frozen by the occurrence of bodies in the
@@ -28332,7 +28336,7 @@ RM References: 13.14 (3/1)
@itemize *
@item
-`AI-0060 Extended definition of remote access types (0000-00-00)'
+@emph{AI-0060 Extended definition of remote access types (0000-00-00)}
This AI extends the definition of remote access types to include access
to limited, synchronized, protected or task class-wide interface types.
@@ -28347,7 +28351,7 @@ RM References: A (4) E.02.02 (9/1) E.02.02 (9.2/1) E.02.02 (14/2) E.02.
@itemize *
@item
-`AI-0114 Classification of letters (0000-00-00)'
+@emph{AI-0114 Classification of letters (0000-00-00)}
The code points 170 (@code{FEMININE ORDINAL INDICATOR}),
181 (@code{MICRO SIGN}), and
@@ -28366,7 +28370,7 @@ RM References: A.03.02 (59) A.04.06 (7)
@itemize *
@item
-`AI-0185 Ada.Wide_[Wide_]Characters.Handling (2010-07-06)'
+@emph{AI-0185 Ada.Wide_[Wide_]Characters.Handling (2010-07-06)}
Two new packages @code{Ada.Wide_[Wide_]Characters.Handling} provide
classification functions for @code{Wide_Character} and
@@ -28383,7 +28387,7 @@ RM References: A.03.05 (0) A.03.06 (0)
@itemize *
@item
-`AI-0031 Add From parameter to Find_Token (2010-07-25)'
+@emph{AI-0031 Add From parameter to Find_Token (2010-07-25)}
A new version of @code{Find_Token} is added to all relevant string packages,
with an extra parameter @code{From}. Instead of starting at the first
@@ -28403,7 +28407,7 @@ A.04.05 (46)
@itemize *
@item
-`AI-0056 Index on null string returns zero (0000-00-00)'
+@emph{AI-0056 Index on null string returns zero (0000-00-00)}
The wording in the Ada 2005 RM implied an incompatible handling of the
@code{Index} functions, resulting in raising an exception instead of
@@ -28420,7 +28424,7 @@ RM References: A.04.03 (56.2/2) A.04.03 (58.5/2)
@itemize *
@item
-`AI-0137 String encoding package (2010-03-25)'
+@emph{AI-0137 String encoding package (2010-03-25)}
The packages @code{Ada.Strings.UTF_Encoding}, together with its child
packages, @code{Conversions}, @code{Strings}, @code{Wide_Strings},
@@ -28446,7 +28450,7 @@ RM References: A.04.11
@itemize *
@item
-`AI-0038 Minor errors in Text_IO (0000-00-00)'
+@emph{AI-0038 Minor errors in Text_IO (0000-00-00)}
These are minor errors in the description on three points. The intent on
all these points has always been clear, and GNAT has always implemented the
@@ -28461,7 +28465,7 @@ RM References: A.10.05 (37) A.10.07 (8/1) A.10.07 (10) A.10.07 (12) A.1
@itemize *
@item
-`AI-0044 Restrictions on container instantiations (0000-00-00)'
+@emph{AI-0044 Restrictions on container instantiations (0000-00-00)}
This AI places restrictions on allowed instantiations of generic containers.
These restrictions are not checked by the compiler, so there is nothing to
@@ -28476,7 +28480,7 @@ RM References: A.18 (4/2) A.18.02 (231/2) A.18.03 (145/2) A.18.06 (56/2)
@itemize *
@item
-`AI-0127 Adding Locale Capabilities (2010-09-29)'
+@emph{AI-0127 Adding Locale Capabilities (2010-09-29)}
This package provides an interface for identifying the current locale.
@@ -28490,7 +28494,7 @@ A.19.07 A.19.08 A.19.09 A.19.10 A.19.11 A.19.12 A.19.13
@itemize *
@item
-`AI-0002 Export C with unconstrained arrays (0000-00-00)'
+@emph{AI-0002 Export C with unconstrained arrays (0000-00-00)}
The compiler is not required to support exporting an Ada subprogram with
convention C if there are parameters or a return type of an unconstrained
@@ -28508,7 +28512,7 @@ RM References: B.01 (17) B.03 (62) B.03 (71.1/2)
@itemize *
@item
-`AI-0216 No_Task_Hierarchy forbids local tasks (0000-00-00)'
+@emph{AI-0216 No_Task_Hierarchy forbids local tasks (0000-00-00)}
It is clearly the intention that @code{No_Task_Hierarchy} is intended to
forbid tasks declared locally within subprograms, or functions returning task
@@ -28525,7 +28529,7 @@ RM References: D.07 (3/3)
@itemize *
@item
-`AI-0211 No_Relative_Delays forbids Set_Handler use (2010-07-09)'
+@emph{AI-0211 No_Relative_Delays forbids Set_Handler use (2010-07-09)}
The restriction @code{No_Relative_Delays} forbids any calls to the subprogram
@code{Ada.Real_Time.Timing_Events.Set_Handler}.
@@ -28539,12 +28543,12 @@ RM References: D.07 (5) D.07 (10/2) D.07 (10.4/2) D.07 (10.7/2)
@itemize *
@item
-`AI-0190 pragma Default_Storage_Pool (2010-09-15)'
+@emph{AI-0190 pragma Default_Storage_Pool (2010-09-15)}
This AI introduces a new pragma @code{Default_Storage_Pool}, which can be
used to control storage pools globally.
In particular, you can force every access
-type that is used for allocation (`new') to have an explicit storage pool,
+type that is used for allocation (@strong{new}) to have an explicit storage pool,
or you can declare a pool globally to be used for all access types that lack
an explicit one.
@@ -28557,7 +28561,7 @@ RM References: D.07 (8)
@itemize *
@item
-`AI-0189 No_Allocators_After_Elaboration (2010-01-23)'
+@emph{AI-0189 No_Allocators_After_Elaboration (2010-01-23)}
This AI introduces a new restriction @code{No_Allocators_After_Elaboration},
which says that no dynamic allocation will occur once elaboration is
@@ -28576,7 +28580,7 @@ RM References: D.07 (19.1/2) H.04 (23.3/2)
@itemize *
@item
-`AI-0171 Pragma CPU and Ravenscar Profile (2010-09-24)'
+@emph{AI-0171 Pragma CPU and Ravenscar Profile (2010-09-24)}
A new package @code{System.Multiprocessors} is added, together with the
definition of pragma @code{CPU} for controlling task affinity. A new no
@@ -28592,7 +28596,7 @@ RM References: D.13.01 (4/2) D.16
@itemize *
@item
-`AI-0210 Correct Timing_Events metric (0000-00-00)'
+@emph{AI-0210 Correct Timing_Events metric (0000-00-00)}
This is a documentation only issue regarding wording of metric requirements,
that does not affect the implementation of the compiler.
@@ -28606,7 +28610,7 @@ RM References: D.15 (24/2)
@itemize *
@item
-`AI-0206 Remote types packages and preelaborate (2010-07-24)'
+@emph{AI-0206 Remote types packages and preelaborate (2010-07-24)}
Remote types packages are now allowed to depend on preelaborated packages.
This was formerly considered illegal.
@@ -28620,7 +28624,7 @@ RM References: E.02.02 (6)
@itemize *
@item
-`AI-0152 Restriction No_Anonymous_Allocators (2010-09-08)'
+@emph{AI-0152 Restriction No_Anonymous_Allocators (2010-09-08)}
Restriction @code{No_Anonymous_Allocators} prevents the use of allocators
where the type of the returned value is an anonymous access type.
@@ -29331,7 +29335,7 @@ change.
GNAT can generate code to zero-out hardware registers before returning
from a subprogram.
-It can be enabled with the @code{-fzero-call-used-regs=`choice'}
+It can be enabled with the @code{-fzero-call-used-regs=@emph{choice}}
command-line option, to affect all subprograms in a compilation, and
with a @code{Machine_Attribute} pragma, to affect only specific
subprograms.
@@ -29440,7 +29444,7 @@ begin
end Bar;
@end example
-There are also @code{-fstrub=`choice'} command-line options to
+There are also @code{-fstrub=@emph{choice}} command-line options to
control default settings. For usage and more details on the
command-line options, on the @code{strub} attribute, and their use with
other programming languages, see @cite{Using the GNU Compiler Collection (GCC)}.
@@ -30093,7 +30097,7 @@ Ada 95 and later versions of the standard:
@itemize *
@item
-`Character literals'
+@emph{Character literals}
Some uses of character literals are ambiguous. Since Ada 95 has introduced
@code{Wide_Character} as a new predefined character type, some uses of
@@ -30113,7 +30117,7 @@ for Char in Character range 'A' .. 'Z' loop ... end loop;
@end example
@item
-`New reserved words'
+@emph{New reserved words}
The identifiers @code{abstract}, @code{aliased}, @code{protected},
@code{requeue}, @code{tagged}, and @code{until} are reserved in Ada 95.
@@ -30121,7 +30125,7 @@ Existing Ada 83 code using any of these identifiers must be edited to
use some alternative name.
@item
-`Freezing rules'
+@emph{Freezing rules}
The rules in Ada 95 are slightly different with regard to the point at
which entities are frozen, and representation pragmas and clauses are
@@ -30135,7 +30139,7 @@ cannot be applied to a subprogram body. If necessary, a separate subprogram
declaration must be introduced to which the pragma can be applied.
@item
-`Optional bodies for library packages'
+@emph{Optional bodies for library packages}
In Ada 83, a package that did not require a package body was nevertheless
allowed to have one. This lead to certain surprises in compiling large
@@ -30152,7 +30156,7 @@ circularities) is to add an @code{Elaborate_Body} pragma to the package spec,
since one effect of this pragma is to require the presence of a package body.
@item
-`Numeric_Error is the same exception as Constraint_Error'
+@emph{Numeric_Error is the same exception as Constraint_Error}
In Ada 95, the exception @code{Numeric_Error} is a renaming of @code{Constraint_Error}.
This means that it is illegal to have separate exception handlers for
@@ -30161,7 +30165,7 @@ the two exceptions. The fix is simply to remove the handler for the
@code{Constraint_Error} in place of @code{Numeric_Error} in all cases).
@item
-`Indefinite subtypes in generics'
+@emph{Indefinite subtypes in generics}
In Ada 83, it was permissible to pass an indefinite type (e.g, @code{String})
as the actual for a generic formal private type, but then the instantiation
@@ -30190,7 +30194,7 @@ the fix is usually simply to add the @code{(<>)} to the generic declaration.
@itemize *
@item
-`Conversions'
+@emph{Conversions}
Conversions from real types to integer types round away from 0. In Ada 83
the conversion Integer(2.5) could deliver either 2 or 3 as its value. This
@@ -30202,7 +30206,7 @@ Note, though, that this issue is no worse than already existed in Ada 83
when porting code from one vendor to another.
@item
-`Tasking'
+@emph{Tasking}
The Real-Time Annex introduces a set of policies that define the behavior of
features that were implementation dependent in Ada 83, such as the order in
@@ -30229,7 +30233,7 @@ situation that you should be alert to is the change in the predefined type
@itemize *
@item
-`Range of type `@w{`}Character`@w{`}'
+@emph{Range of type `@w{`}Character`@w{`}}
The range of @code{Standard.Character} is now the full 256 characters
of Latin-1, whereas in most Ada 83 implementations it was restricted
@@ -30260,7 +30264,7 @@ covers only the restricted range.
@itemize *
@item
-`-gnat83' switch
+@emph{-gnat83} switch
All implementations of GNAT provide a switch that causes GNAT to operate
in Ada 83 mode. In this mode, some but not all compatibility problems
@@ -30301,7 +30305,7 @@ for a complete description please see the
@itemize *
@item
-`New reserved words.'
+@emph{New reserved words.}
The words @code{interface}, @code{overriding} and @code{synchronized} are
reserved in Ada 2005.
@@ -30309,7 +30313,7 @@ A pre-Ada 2005 program that uses any of these as an identifier will be
illegal.
@item
-`New declarations in predefined packages.'
+@emph{New declarations in predefined packages.}
A number of packages in the predefined environment contain new declarations:
@code{Ada.Exceptions}, @code{Ada.Real_Time}, @code{Ada.Strings},
@@ -30321,26 +30325,26 @@ If an Ada 95 program does a @code{with} and @code{use} of any of these
packages, the new declarations may cause name clashes.
@item
-`Access parameters.'
+@emph{Access parameters.}
A nondispatching subprogram with an access parameter cannot be renamed
as a dispatching operation. This was permitted in Ada 95.
@item
-`Access types, discriminants, and constraints.'
+@emph{Access types, discriminants, and constraints.}
Rule changes in this area have led to some incompatibilities; for example,
constrained subtypes of some access types are not permitted in Ada 2005.
@item
-`Aggregates for limited types.'
+@emph{Aggregates for limited types.}
The allowance of aggregates for limited types in Ada 2005 raises the
possibility of ambiguities in legal Ada 95 programs, since additional types
now need to be considered in expression resolution.
@item
-`Fixed-point multiplication and division.'
+@emph{Fixed-point multiplication and division.}
Certain expressions involving ‘*’ or ‘/’ for a fixed-point type, which
were legal in Ada 95 and invoked the predefined versions of these operations,
@@ -30350,7 +30354,7 @@ expression, or by explicitly invoking the operation from package
@code{Standard}.
@item
-`Return-by-reference types.'
+@emph{Return-by-reference types.}
The Ada 95 return-by-reference mechanism has been removed. Instead, the user
can declare a function returning a value from an anonymous access type.
@@ -30459,7 +30463,7 @@ elaboration problems) by implicitly inserting @code{Elaborate} or
@code{Elaborate_All} pragmas where
needed. However, this can lead to the creation of elaboration circularities
and a resulting rejection of the program by gnatbind. This issue is
-thoroughly described in the `Elaboration Order Handling in GNAT' appendix
+thoroughly described in the @emph{Elaboration Order Handling in GNAT} appendix
in the @cite{GNAT User’s Guide}.
In brief, there are several
ways to deal with this situation:
@@ -30475,7 +30479,7 @@ elaboration-time code into explicitly-invoked procedures
Constrain the elaboration order by including explicit @code{Elaborate_Body} or
@code{Elaborate} pragmas, and then inhibit the generation of implicit
@code{Elaborate_All}
-pragmas either globally (as an effect of the `-gnatE' switch) or locally
+pragmas either globally (as an effect of the @emph{-gnatE} switch) or locally
(by selectively suppressing elaboration checks via pragma
@code{Suppress(Elaboration_Check)} when it is safe to do so).
@end itemize
@@ -30515,7 +30519,7 @@ when other compilers appear.)
@itemize *
@item
-`Ada 83 Pragmas and Attributes'
+@emph{Ada 83 Pragmas and Attributes}
Ada 95 compilers are allowed, but not required, to implement the missing
Ada 83 pragmas and attributes that are no longer defined in Ada 95.
@@ -30524,7 +30528,7 @@ a compatibility concern, but some other Ada 95 compilers reject these
pragmas and attributes.
@item
-`Specialized Needs Annexes'
+@emph{Specialized Needs Annexes}
GNAT implements the full set of special needs annexes. At the
current time, it is the only Ada 95 compiler to do so. This means that
@@ -30532,7 +30536,7 @@ programs making use of these features may not be portable to other Ada
95 compilation systems.
@item
-`Representation Clauses'
+@emph{Representation Clauses}
Some other Ada 95 compilers implement only the minimal set of
representation clauses required by the Ada 95 reference manual. GNAT goes
@@ -30564,7 +30568,7 @@ the cases most likely to arise in existing Ada 83 code.
@itemize *
@item
-`Implicit Packing'
+@emph{Implicit Packing}
Some Ada 83 compilers allowed a Size specification to cause implicit
packing of an array or record. This could cause expensive implicit
@@ -30580,7 +30584,7 @@ the explicit pragma @code{Pack}, or for more fine tuned control, provide
a Component_Size clause.
@item
-`Meaning of Size Attribute'
+@emph{Meaning of Size Attribute}
The Size attribute in Ada 95 (and Ada 2005) for discrete types is defined as
the minimal number of bits required to hold values of the type. For example,
@@ -30593,7 +30597,7 @@ Object_Size can provide a useful way of duplicating the behavior of
some Ada 83 compiler systems.
@item
-`Size of Access Types'
+@emph{Size of Access Types}
A common assumption in Ada 83 code is that an access type is in fact a pointer,
and that therefore it will be the same size as a System.Address value. This
@@ -30646,13 +30650,13 @@ applicable to GNAT.
@itemize *
@item
-`Default floating-point representation'
+@emph{Default floating-point representation}
In GNAT, the default floating-point format is IEEE, whereas in HP Ada 83,
it is VMS format.
@item
-`System'
+@emph{System}
the package System in GNAT exactly corresponds to the definition in the
Ada 95 reference manual, which means that it excludes many of the
@@ -30675,7 +30679,7 @@ Copyright 2000, 2001, 2002, 2007, 2008 Free Software Foundation, Inc
Everyone is permitted to copy and distribute verbatim copies of this
license document, but changing it is not allowed.
-`Preamble'
+@strong{Preamble}
The purpose of this License is to make a manual, textbook, or other
functional and useful document “free” in the sense of freedom: to
@@ -30698,23 +30702,23 @@ it can be used for any textual work, regardless of subject matter or
whether it is published as a printed book. We recommend this License
principally for works whose purpose is instruction or reference.
-`1. APPLICABILITY AND DEFINITIONS'
+@strong{1. APPLICABILITY AND DEFINITIONS}
This License applies to any manual or other work, in any medium, that
contains a notice placed by the copyright holder saying it can be
distributed under the terms of this License. Such a notice grants a
world-wide, royalty-free license, unlimited in duration, to use that
-work under the conditions stated herein. The `Document', below,
+work under the conditions stated herein. The @strong{Document}, below,
refers to any such manual or work. Any member of the public is a
-licensee, and is addressed as “`you'”. You accept the license if you
+licensee, and is addressed as “@strong{you}”. You accept the license if you
copy, modify or distribute the work in a way requiring permission
under copyright law.
-A “`Modified Version'” of the Document means any work containing the
+A “@strong{Modified Version}” of the Document means any work containing the
Document or a portion of it, either copied verbatim, or with
modifications and/or translated into another language.
-A “`Secondary Section'” is a named appendix or a front-matter section of
+A “@strong{Secondary Section}” is a named appendix or a front-matter section of
the Document that deals exclusively with the relationship of the
publishers or authors of the Document to the Document’s overall subject
(or to related matters) and contains nothing that could fall directly
@@ -30725,7 +30729,7 @@ connection with the subject or with related matters, or of legal,
commercial, philosophical, ethical or political position regarding
them.
-The “`Invariant Sections'” are certain Secondary Sections whose titles
+The “@strong{Invariant Sections}” are certain Secondary Sections whose titles
are designated, as being those of Invariant Sections, in the notice
that says that the Document is released under this License. If a
section does not fit the above definition of Secondary then it is not
@@ -30733,12 +30737,12 @@ allowed to be designated as Invariant. The Document may contain zero
Invariant Sections. If the Document does not identify any Invariant
Sections then there are none.
-The “`Cover Texts'” are certain short passages of text that are listed,
+The “@strong{Cover Texts}” are certain short passages of text that are listed,
as Front-Cover Texts or Back-Cover Texts, in the notice that says that
the Document is released under this License. A Front-Cover Text may
be at most 5 words, and a Back-Cover Text may be at most 25 words.
-A “`Transparent'” copy of the Document means a machine-readable copy,
+A “@strong{Transparent}” copy of the Document means a machine-readable copy,
represented in a format whose specification is available to the
general public, that is suitable for revising the document
straightforwardly with generic text editors or (for images composed of
@@ -30749,7 +30753,7 @@ to text formatters. A copy made in an otherwise Transparent file
format whose markup, or absence of markup, has been arranged to thwart
or discourage subsequent modification by readers is not Transparent.
An image format is not Transparent if used for any substantial amount
-of text. A copy that is not “Transparent” is called `Opaque'.
+of text. A copy that is not “Transparent” is called @strong{Opaque}.
Examples of suitable formats for Transparent copies include plain
ASCII without markup, Texinfo input format, LaTeX input format, SGML
@@ -30762,22 +30766,22 @@ processing tools are not generally available, and the
machine-generated HTML, PostScript or PDF produced by some word
processors for output purposes only.
-The “`Title Page'” means, for a printed book, the title page itself,
+The “@strong{Title Page}” means, for a printed book, the title page itself,
plus such following pages as are needed to hold, legibly, the material
this License requires to appear in the title page. For works in
formats which do not have any title page as such, “Title Page” means
the text near the most prominent appearance of the work’s title,
preceding the beginning of the body of the text.
-The “`publisher'” means any person or entity that distributes
+The “@strong{publisher}” means any person or entity that distributes
copies of the Document to the public.
-A section “`Entitled XYZ'” means a named subunit of the Document whose
+A section “@strong{Entitled XYZ}” means a named subunit of the Document whose
title either is precisely XYZ or contains XYZ in parentheses following
text that translates XYZ in another language. (Here XYZ stands for a
-specific section name mentioned below, such as “`Acknowledgements'”,
-“`Dedications'”, “`Endorsements'”, or “`History'”.)
-To “`Preserve the Title'”
+specific section name mentioned below, such as “@strong{Acknowledgements}”,
+“@strong{Dedications}”, “@strong{Endorsements}”, or “@strong{History}”.)
+To “@strong{Preserve the Title}”
of such a section when you modify the Document means that it remains a
section “Entitled XYZ” according to this definition.
@@ -30788,7 +30792,7 @@ License, but only as regards disclaiming warranties: any other
implication that these Warranty Disclaimers may have is void and has
no effect on the meaning of this License.
-`2. VERBATIM COPYING'
+@strong{2. VERBATIM COPYING}
You may copy and distribute the Document in any medium, either
commercially or noncommercially, provided that this License, the
@@ -30803,7 +30807,7 @@ number of copies you must also follow the conditions in section 3.
You may also lend copies, under the same conditions stated above, and
you may publicly display copies.
-`3. COPYING IN QUANTITY'
+@strong{3. COPYING IN QUANTITY}
If you publish printed copies (or copies in media that commonly have
printed covers) of the Document, numbering more than 100, and the
@@ -30840,7 +30844,7 @@ It is requested, but not required, that you contact the authors of the
Document well before redistributing any large number of copies, to give
them a chance to provide you with an updated version of the Document.
-`4. MODIFICATIONS'
+@strong{4. MODIFICATIONS}
You may copy and distribute a Modified Version of the Document under
the conditions of sections 2 and 3 above, provided that you release
@@ -30957,7 +30961,7 @@ The author(s) and publisher(s) of the Document do not by this License
give permission to use their names for publicity for or to assert or
imply endorsement of any Modified Version.
-`5. COMBINING DOCUMENTS'
+@strong{5. COMBINING DOCUMENTS}
You may combine the Document with other documents released under this
License, under the terms defined in section 4 above for modified
@@ -30981,7 +30985,7 @@ in the various original documents, forming one section Entitled
and any sections Entitled “Dedications”. You must delete all sections
Entitled “Endorsements”.
-`6. COLLECTIONS OF DOCUMENTS'
+@strong{6. COLLECTIONS OF DOCUMENTS}
You may make a collection consisting of the Document and other documents
released under this License, and replace the individual copies of this
@@ -30994,7 +30998,7 @@ it individually under this License, provided you insert a copy of this
License into the extracted document, and follow this License in all
other respects regarding verbatim copying of that document.
-`7. AGGREGATION WITH INDEPENDENT WORKS'
+@strong{7. AGGREGATION WITH INDEPENDENT WORKS}
A compilation of the Document or its derivatives with other separate
and independent documents or works, in or on a volume of a storage or
@@ -31013,7 +31017,7 @@ electronic equivalent of covers if the Document is in electronic form.
Otherwise they must appear on printed covers that bracket the whole
aggregate.
-`8. TRANSLATION'
+@strong{8. TRANSLATION}
Translation is considered a kind of modification, so you may
distribute translations of the Document under the terms of section 4.
@@ -31033,7 +31037,7 @@ If a section in the Document is Entitled “Acknowledgements”,
its Title (section 1) will typically require changing the actual
title.
-`9. TERMINATION'
+@strong{9. TERMINATION}
You may not copy, modify, sublicense, or distribute the Document
except as expressly provided under this License. Any attempt
@@ -31060,7 +31064,7 @@ this License. If your rights have been terminated and not permanently
reinstated, receipt of a copy of some or all of the same material does
not give you any rights to use it.
-`10. FUTURE REVISIONS OF THIS LICENSE'
+@strong{10. FUTURE REVISIONS OF THIS LICENSE}
The Free Software Foundation may publish new, revised versions
of the GNU Free Documentation License from time to time. Such new
@@ -31081,7 +31085,7 @@ License can be used, that proxy’s public statement of acceptance of a
version permanently authorizes you to choose that version for the
Document.
-`11. RELICENSING'
+@strong{11. RELICENSING}
“Massive Multiauthor Collaboration Site” (or “MMC Site”) means any
World Wide Web server that publishes copyrightable works and also
@@ -31110,7 +31114,7 @@ The operator of an MMC Site may republish an MMC contained in the site
under CC-BY-SA on the same site at any time before August 1, 2009,
provided the MMC is eligible for relicensing.
-`ADDENDUM: How to use this License for your documents'
+@strong{ADDENDUM: How to use this License for your documents}
To use this License in a document you have written, include a copy of
the License in the document and put the following copyright and
@@ -3,7 +3,7 @@
@setfilename gnat_ugn.info
@documentencoding UTF-8
@ifinfo
-@*Generated by Sphinx 5.3.0.@*
+@*Generated by Sphinx 4.3.2.@*
@end ifinfo
@settitle GNAT User's Guide for Native Platforms
@defindex ge
@@ -15,11 +15,13 @@
* gnat_ugn: (gnat_ugn.info). gnat_ugn
@end direntry
+@definfoenclose strong,`,'
+@definfoenclose emph,`,'
@c %**end of header
@copying
@quotation
-GNAT User's Guide for Native Platforms , Nov 10, 2023
+GNAT User's Guide for Native Platforms , Dec 14, 2023
AdaCore
@@ -46,7 +48,7 @@ Copyright @copyright{} 2008-2023, Free Software Foundation
@c %**start of body
@anchor{gnat_ugn doc}@anchor{0}
-`GNAT, The GNU Ada Development Environment'
+@emph{GNAT, The GNU Ada Development Environment}
@include gcc-common.texi
@@ -705,7 +707,7 @@ and @code{classes}.
@code{Variables}
@item
-`Emphasis'
+@emph{Emphasis}
@item
[optional information or parameters]
@@ -939,15 +941,15 @@ following three separate files:
@table @asis
-@item `greetings.ads'
+@item @emph{greetings.ads}
spec of package @code{Greetings}
-@item `greetings.adb'
+@item @emph{greetings.adb}
body of package @code{Greetings}
-@item `gmain.adb'
+@item @emph{gmain.adb}
body of main program
@end table
@@ -1175,8 +1177,8 @@ code is used to represent the end of file.
Each file contains a single Ada compilation unit, including any pragmas
associated with the unit. For example, this means you must place a
-package declaration (a package `spec') and the corresponding body in
-separate files. An Ada `compilation' (which is a sequence of
+package declaration (a package @emph{spec}) and the corresponding body in
+separate files. An Ada @emph{compilation} (which is a sequence of
compilation units) is represented using a sequence of files. Similarly,
you will place each subunit or child unit in a separate file.
@@ -1234,7 +1236,7 @@ GNAT also supports several other 8-bit coding schemes:
@table @asis
-@item `ISO 8859-2 (Latin-2)'
+@item @emph{ISO 8859-2 (Latin-2)}
Latin-2 letters allowed in identifiers, with uppercase and lowercase
equivalence.
@@ -1247,7 +1249,7 @@ equivalence.
@table @asis
-@item `ISO 8859-3 (Latin-3)'
+@item @emph{ISO 8859-3 (Latin-3)}
Latin-3 letters allowed in identifiers, with uppercase and lowercase
equivalence.
@@ -1260,7 +1262,7 @@ equivalence.
@table @asis
-@item `ISO 8859-4 (Latin-4)'
+@item @emph{ISO 8859-4 (Latin-4)}
Latin-4 letters allowed in identifiers, with uppercase and lowercase
equivalence.
@@ -1273,7 +1275,7 @@ equivalence.
@table @asis
-@item `ISO 8859-5 (Cyrillic)'
+@item @emph{ISO 8859-5 (Cyrillic)}
ISO 8859-5 letters (Cyrillic) allowed in identifiers, with uppercase and
lowercase equivalence.
@@ -1286,7 +1288,7 @@ lowercase equivalence.
@table @asis
-@item `ISO 8859-15 (Latin-9)'
+@item @emph{ISO 8859-15 (Latin-9)}
ISO 8859-15 (Latin-9) letters allowed in identifiers, with uppercase and
lowercase equivalence.
@@ -1297,7 +1299,7 @@ lowercase equivalence.
@table @asis
-@item `IBM PC (code page 437)'
+@item @emph{IBM PC (code page 437)}
This code page is the normal default for PCs in the U.S. It corresponds
to the original IBM PC character set. This set has some, but not all, of
@@ -1311,14 +1313,14 @@ identifiers with uppercase and lowercase equivalence.
@table @asis
-@item `IBM PC (code page 850)'
+@item @emph{IBM PC (code page 850)}
This code page is a modification of 437 extended to include all the
Latin-1 letters, but still not with the usual Latin-1 encoding. In this
mode, all these letters are allowed in identifiers with uppercase and
lowercase equivalence.
-@item `Full Upper 8-bit'
+@item @emph{Full Upper 8-bit}
Any character in the range 80-FF allowed in identifiers, and all are
considered distinct. In other words, there are no uppercase and lowercase
@@ -1326,7 +1328,7 @@ equivalences in this range. This is useful in conjunction with
certain encoding schemes used for some foreign character sets (e.g.,
the typical method of representing Chinese characters on the PC).
-@item `No Upper-Half'
+@item @emph{No Upper-Half}
No upper-half characters in the range 80-FF are allowed in identifiers.
This gives Ada 83 compatibility for identifier names.
@@ -1349,7 +1351,7 @@ possible encoding schemes:
@table @asis
-@item `Hex Coding'
+@item @emph{Hex Coding}
In this encoding, a wide character is represented by the following five
character sequence:
@@ -1370,7 +1372,7 @@ This scheme is compatible with use of the full Wide_Character set.
@table @asis
-@item `Upper-Half Coding'
+@item @emph{Upper-Half Coding}
The wide character with encoding @code{16#abcd#} where the upper bit is on
(in other words, ‘a’ is in the range 8-F) is represented as two bytes,
@@ -1385,7 +1387,7 @@ external coding.
@table @asis
-@item `Shift JIS Coding'
+@item @emph{Shift JIS Coding}
A wide character is represented by a two-character sequence,
@code{16#ab#} and
@@ -1401,7 +1403,7 @@ used with this encoding method.
@table @asis
-@item `EUC Coding'
+@item @emph{EUC Coding}
A wide character is represented by a two-character sequence
@code{16#ab#} and
@@ -1410,7 +1412,7 @@ character code is the corresponding JIS character according to the EUC
encoding algorithm. Only characters defined in the JIS code set table
can be used with this encoding method.
-@item `UTF-8 Coding'
+@item @emph{UTF-8 Coding}
A wide character is represented using
UCS Transformation Format 8 (UTF-8) as defined in Annex R of ISO
@@ -1431,7 +1433,7 @@ other wide characters are represented as sequences of upper-half
6-byte sequences, and in the following section on wide wide
characters, the use of these sequences is documented).
-@item `Brackets Coding'
+@item @emph{Brackets Coding}
In this encoding, a wide character is represented by the following eight
character sequence:
@@ -1472,7 +1474,7 @@ possible encoding schemes:
@table @asis
-@item `UTF-8 Coding'
+@item @emph{UTF-8 Coding}
A wide character is represented using
UCS Transformation Format 8 (UTF-8) as defined in Annex R of ISO
@@ -1492,7 +1494,7 @@ is a four, five, or six byte sequence:
where the @code{xxx} bits correspond to the left-padded bits of the
32-bit character value.
-@item `Brackets Coding'
+@item @emph{Brackets Coding}
In this encoding, a wide wide character is represented by the following ten or
twelve byte character sequence:
@@ -1983,7 +1985,7 @@ Display Copyright and version, then exit disregarding all other options.
If @code{--version} was not used, display usage, then exit disregarding
all other options.
-@item @code{--subdirs=`dir'}
+@item @code{--subdirs=@emph{dir}}
Real object, library or exec directories are subdirectories <dir> of the
specified ones.
@@ -2002,7 +2004,7 @@ Start another section of directories/patterns.
@table @asis
-@item @code{-c`filename'}
+@item @code{-c@emph{filename}}
Create a configuration pragmas file @code{filename} (instead of the default
@code{gnat.adc}).
@@ -2019,7 +2021,7 @@ specified, no switch @code{-P} may be specified (see below).
@table @asis
-@item @code{-d`dir'}
+@item @code{-d@emph{dir}}
Look for source files in directory @code{dir}. There may be zero, one or more
spaces between @code{-d} and @code{dir}.
@@ -2047,7 +2049,7 @@ specified with switch @code{-d} must exist and be readable.
@table @asis
-@item @code{-D`filename'}
+@item @code{-D@emph{filename}}
Look for source files in all directories listed in text file @code{filename}.
There may be zero, one or more spaces between @code{-D}
@@ -2064,7 +2066,7 @@ Follow symbolic links when processing project files.
@geindex -f (gnatname)
-@item @code{-f`pattern'}
+@item @code{-f@emph{pattern}}
Foreign patterns. Using this switch, it is possible to add sources of languages
other than Ada to the list of sources of a project file.
@@ -2087,7 +2089,7 @@ Output usage (help) information. The output is written to @code{stdout}.
@geindex -P (gnatname)
-@item @code{-P`proj'}
+@item @code{-P@emph{proj}}
Create or update project file @code{proj}. There may be zero, one or more space
between @code{-P} and @code{proj}. @code{proj} may include directory
@@ -2124,7 +2126,7 @@ the Naming Patterns, an indication is given that there is no match.
@geindex -x (gnatname)
-@item @code{-x`pattern'}
+@item @code{-x@emph{pattern}}
Excluded patterns. Using this switch, it is possible to exclude some files
that would match the name patterns. For example,
@@ -2214,7 +2216,7 @@ and GNAT, which use the prefixes
respectively.
@end itemize
-The @code{-gnatk`nn'}
+The @code{-gnatk@emph{nn}}
switch of the compiler activates a ‘krunching’
circuit that limits file names to nn characters (where nn is a decimal
integer).
@@ -2623,10 +2625,10 @@ Causes @code{gnatchop} to operate in compilation mode, in which
configuration pragmas are handled according to strict RM rules. See
previous section for a full description of this mode.
-@item @code{-gnat`xxx'}
+@item @code{-gnat@emph{xxx}}
-This passes the given @code{-gnat`xxx'} switch to @code{gnat} which is
-used to parse the given file. Not all `xxx' options make sense,
+This passes the given @code{-gnat@emph{xxx}} switch to @code{gnat} which is
+used to parse the given file. Not all @emph{xxx} options make sense,
but for example, the use of @code{-gnati2} allows @code{gnatchop} to
process a source file that uses Latin-2 coding for identifiers.
@@ -2641,7 +2643,7 @@ output file showing usage information.
@table @asis
-@item @code{-k`mm'}
+@item @code{-k@emph{mm}}
Limit generated file names to the specified number @code{mm}
of characters.
@@ -2744,7 +2746,7 @@ units to be skipped.
@table @asis
-@item @code{--GCC=`xxxx'}
+@item @code{--GCC=@emph{xxxx}}
Specify the path of the GNAT parser to be used. When this switch is used,
no attempt is made to add the prefix to the GNAT parser executable.
@@ -2917,7 +2919,7 @@ the type of restriction.
Restrictions that require partition-wide consistency (like
@code{No_Tasking}) are
recognized wherever they appear
-and can be freely inherited, e.g. from a `with'ed unit to the `with'ing
+and can be freely inherited, e.g. from a @emph{with}ed unit to the @emph{with}ing
unit. This makes sense since the binder will in any case insist on seeing
consistent use, so any unit not conforming to any restrictions that are
anywhere in the partition will be rejected, and you might as well find
@@ -2958,7 +2960,7 @@ configuration pragmas, or more conveniently by direct editing of the
Besides @code{gnat.adc}, additional files containing configuration
pragmas may be applied to the current compilation using the switch
-@code{-gnatec=`path'} where @code{path} must designate an existing file that
+@code{-gnatec=@emph{path}} where @code{path} must designate an existing file that
contains only configuration pragmas. These configuration pragmas are
in addition to those found in @code{gnat.adc} (provided @code{gnat.adc}
is present and switch @code{-gnatA} is not used).
@@ -3073,10 +3075,10 @@ additional source files as follows:
@itemize *
@item
-If a file being compiled `with's a unit @code{X}, the object file
+If a file being compiled @emph{with}s a unit @code{X}, the object file
depends on the file containing the spec of unit @code{X}. This includes
-files that are `with'ed implicitly either because they are parents
-of `with'ed child units or they are run-time units required by the
+files that are @emph{with}ed implicitly either because they are parents
+of @emph{with}ed child units or they are run-time units required by the
language constructs used in a particular unit.
@item
@@ -3130,7 +3132,7 @@ The object file for a parent unit depends on all its subunit body files.
The previous two rules meant that for purposes of computing dependencies and
recompilation, a body and all its subunits are treated as an indivisible whole.
-These rules are applied transitively: if unit @code{A} `with's
+These rules are applied transitively: if unit @code{A} @emph{with}s
unit @code{B}, whose elaboration calls an inlined procedure in package
@code{C}, the object file for unit @code{A} will depend on the body of
@code{C}, in file @code{c.adb}.
@@ -3192,7 +3194,7 @@ checking.
Categorization information (e.g., use of pragma @code{Pure}).
@item
-Information on all `with'ed units, including presence of
+Information on all @emph{with}ed units, including presence of
@code{Elaborate} or @code{Elaborate_All} pragmas.
@item
@@ -3262,8 +3264,8 @@ object files for the Ada units of the program.
This section describes how to build and use libraries with GNAT, and also shows
how to recompile the GNAT run-time library. You should be familiar with the
-Project Manager facility (see the `GNAT_Project_Manager' chapter of the
-`GPRbuild User’s Guide') before reading this chapter.
+Project Manager facility (see the @emph{GNAT_Project_Manager} chapter of the
+@emph{GPRbuild User’s Guide}) before reading this chapter.
@menu
* Introduction to Libraries in GNAT::
@@ -3312,14 +3314,14 @@ documentation purposes. Alternatively, it may expose only the units needed by
an external user to make use of the library. That is to say, the specs
reflecting the library services along with all the units needed to compile
those specs, which can include generic bodies or any body implementing an
-inlined routine. In the case of `stand-alone libraries' those exposed
-units are called `interface units' (@ref{6b,,Stand-alone Ada Libraries}).
+inlined routine. In the case of @emph{stand-alone libraries} those exposed
+units are called @emph{interface units} (@ref{6b,,Stand-alone Ada Libraries}).
All compilation units comprising an application, including those in a library,
need to be elaborated in an order partially defined by Ada’s semantics. GNAT
computes the elaboration order from the @code{ALI} files and this is why they
constitute a mandatory part of GNAT libraries.
-`Stand-alone libraries' are the exception to this rule because a specific
+@emph{Stand-alone libraries} are the exception to this rule because a specific
library elaboration routine is produced independently of the application(s)
using the library.
@@ -3341,9 +3343,9 @@ using the library.
The easiest way to build a library is to use the Project Manager,
-which supports a special type of project called a `Library Project'
-(see the `Library Projects' section in the `GNAT Project Manager'
-chapter of the `GPRbuild User’s Guide').
+which supports a special type of project called a @emph{Library Project}
+(see the @emph{Library Projects} section in the @emph{GNAT Project Manager}
+chapter of the @emph{GPRbuild User’s Guide}).
A project is considered a library project, when two project-level attributes
are defined in it: @code{Library_Name} and @code{Library_Dir}. In order to
@@ -3464,9 +3466,9 @@ $ rm *.o
$ chmod -w *.ali
@end example
-Please note that the library must have a name of the form @code{lib`xxx'.a}
-or @code{lib`xxx'.so} (or @code{lib`xxx'.dll} on Windows) in order to
-be accessed by the directive @code{-l`xxx'} at link time.
+Please note that the library must have a name of the form @code{lib@emph{xxx}.a}
+or @code{lib@emph{xxx}.so} (or @code{lib@emph{xxx}.dll} on Windows) in order to
+be accessed by the directive @code{-l@emph{xxx}} at link time.
@node Installing a library,Using a library,Building a library,General Ada Libraries
@anchor{gnat_ugn/the_gnat_compilation_model id39}@anchor{71}@anchor{gnat_ugn/the_gnat_compilation_model installing-a-library}@anchor{72}
@@ -3478,8 +3480,8 @@ be accessed by the directive @code{-l`xxx'} at link time.
@geindex GPR_PROJECT_PATH
If you use project files, library installation is part of the library build
-process (see the `Installing a Library with Project Files' section of the
-`GNAT Project Manager' chapter of the `GPRbuild User’s Guide').
+process (see the @emph{Installing a Library with Project Files} section of the
+@emph{GNAT Project Manager} chapter of the @emph{GPRbuild User’s Guide}).
When project files are not an option, it is also possible, but not recommended,
to install the library so that the sources needed to use the library are on the
@@ -3532,7 +3534,7 @@ any part of it.
Once again, the project facility greatly simplifies the use of
libraries. In this context, using a library is just a matter of adding a
-`with' clause in the user project. For instance, to make use of the
+@emph{with} clause in the user project. For instance, to make use of the
library @code{My_Lib} shown in examples in earlier sections, you can
write:
@@ -3545,7 +3547,7 @@ end My_Proj;
Even if you have a third-party, non-Ada library, you can still use GNAT’s
Project Manager facility to provide a wrapper for it. For example, the
-following project, when `with'ed by your main project, will link with the
+following project, when @emph{with}ed by your main project, will link with the
third-party library @code{liba.a}:
@example
@@ -3675,12 +3677,12 @@ main routine is not written in Ada.
GNAT’s Project facility provides a simple way of building and installing
-stand-alone libraries; see the `Stand-alone Library Projects' section
-in the `GNAT Project Manager' chapter of the `GPRbuild User’s Guide'.
+stand-alone libraries; see the @emph{Stand-alone Library Projects} section
+in the @emph{GNAT Project Manager} chapter of the @emph{GPRbuild User’s Guide}.
To be a Stand-alone Library Project, in addition to the two attributes
that make a project a Library Project (@code{Library_Name} and
-@code{Library_Dir}; see the `Library Projects' section in the
-`GNAT Project Manager' chapter of the `GPRbuild User’s Guide'),
+@code{Library_Dir}; see the @emph{Library Projects} section in the
+@emph{GNAT Project Manager} chapter of the @emph{GPRbuild User’s Guide}),
the attribute @code{Library_Interface} must be defined. For example:
@example
@@ -4070,7 +4072,7 @@ end Config;
The @code{Config} package exists in multiple forms for the various targets,
with an appropriate script selecting the version of @code{Config} needed.
-Then any other unit requiring conditional compilation can do a `with'
+Then any other unit requiring conditional compilation can do a @emph{with}
of @code{Config} to make the constants visible.
@node Debugging - A Special Case,Conditionalizing Declarations,Use of Boolean Constants,Modeling Conditional Compilation in Ada
@@ -4461,7 +4463,7 @@ For further discussion of conditional compilation in general, see
@subsubsection Preprocessing Symbols
-Preprocessing symbols are defined in `definition files' and referenced in the
+Preprocessing symbols are defined in @emph{definition files} and referenced in the
sources to be preprocessed. A preprocessing symbol is an identifier, following
normal Ada (case-insensitive) rules for its syntax, with the restriction that
all characters need to be in the ASCII set (no accented letters).
@@ -4486,7 +4488,7 @@ where
@table @asis
-@item `switches'
+@item @emph{switches}
is an optional sequence of switches as described in the next section.
@end table
@@ -4495,7 +4497,7 @@ is an optional sequence of switches as described in the next section.
@table @asis
-@item `infile'
+@item @emph{infile}
is the full name of the input file, which is an Ada source
file containing preprocessor directives.
@@ -4505,7 +4507,7 @@ file containing preprocessor directives.
@table @asis
-@item `outfile'
+@item @emph{outfile}
is the full name of the output file, which is an Ada source
in standard Ada form. When used with GNAT, this file name will
@@ -4596,7 +4598,7 @@ this context since comments are ignored by the compiler in any case).
@table @asis
-@item @code{-D`symbol'[=`value']}
+@item @code{-D@emph{symbol}[=@emph{value}]}
Defines a new preprocessing symbol with the specified value. If no value is given
on the command line, then symbol is considered to be @code{True}. This switch
@@ -4846,7 +4848,7 @@ As noted above, a file to be preprocessed consists of Ada source code
in which preprocessing lines have been inserted. However,
instead of using @code{gnatprep} to explicitly preprocess a file as a separate
step before compilation, you can carry out the preprocessing implicitly
-as part of compilation. Such `integrated preprocessing', which is the common
+as part of compilation. Such @emph{integrated preprocessing}, which is the common
style with C, is performed when either or both of the following switches
are passed to the compiler:
@@ -4856,7 +4858,7 @@ are passed to the compiler:
@itemize *
@item
-@code{-gnatep}, which specifies the `preprocessor data file'.
+@code{-gnatep}, which specifies the @emph{preprocessor data file}.
This file dictates how the source files will be preprocessed (e.g., which
symbol definition files apply to which sources).
@@ -4885,7 +4887,7 @@ When using project files:
@item
the builder switch @code{-x} should be used if any Ada source is
compiled with @code{gnatep=}, so that the compiler finds the
-`preprocessor data file'.
+@emph{preprocessor data file}.
@item
the preprocessing data file and the symbol definition files should be
@@ -4907,7 +4909,7 @@ that relate to integrated preprocessing.
@table @asis
-@item @code{-gnatep=`preprocessor_data_file'}
+@item @code{-gnatep=@emph{preprocessor_data_file}}
This switch specifies the file name (without directory
information) of the preprocessor data file. Either place this file
@@ -4927,12 +4929,12 @@ end Prj;
@end example
@end quotation
-A preprocessor data file is a text file that contains `preprocessor
-control lines'. A preprocessor control line directs the preprocessing of
+A preprocessor data file is a text file that contains @emph{preprocessor
+control lines}. A preprocessor control line directs the preprocessing of
either a particular source file, or, analogous to @code{others} in Ada,
all sources not specified elsewhere in the preprocessor data file.
A preprocessor control line
-can optionally identify a `definition file' that assigns values to
+can optionally identify a @emph{definition file} that assigns values to
preprocessor symbols, as well as a list of switches that relate to
preprocessing.
Empty lines and comments (using Ada syntax) are also permitted, with no
@@ -5023,7 +5025,7 @@ Causes both preprocessor lines and the lines deleted
by preprocessing to be retained as comments marked
with the special string ‘@cite{–!}’.
-@item @code{-D`symbol'=`new_value'}
+@item @code{-D@emph{symbol}=@emph{new_value}}
Define or redefine @code{symbol} to have @code{new_value} as its value.
The permitted form for @code{symbol} is either an Ada identifier, or any Ada reserved word
@@ -5052,7 +5054,7 @@ a @code{#if} or @code{#elsif} test will be treated as an error.
@table @asis
-@item @code{-gnateD`symbol'[=`new_value']}
+@item @code{-gnateD@emph{symbol}[=@emph{new_value}]}
Define or redefine @code{symbol} to have @code{new_value} as its value. If no value
is supplied, then the value of @code{symbol} is @code{True}.
@@ -6537,7 +6539,7 @@ If you want to generate a single Ada file and not the transitive closure, you
can use instead the @code{-fdump-ada-spec-slim} switch.
You can optionally specify a parent unit, of which all generated units will
-be children, using @code{-fada-spec-parent=`unit'}.
+be children, using @code{-fada-spec-parent=@emph{unit}}.
The simple @code{gcc}-based command works only for C headers. For C++ headers
you need to use either the @code{g++} command or the combination @code{gcc -x c++}.
@@ -6578,7 +6580,7 @@ $ gcc -c -fdump-ada-spec readline1.h
Generating bindings for C++ headers is done using the same options, always
-with the `g++' compiler. Note that generating Ada spec from C++ headers is a
+with the @emph{g++} compiler. Note that generating Ada spec from C++ headers is a
much more complex job and support for C++ headers is much more limited that
support for C headers. As a result, you will need to modify the resulting
bindings by hand more extensively when using C++ headers.
@@ -6586,7 +6588,7 @@ bindings by hand more extensively when using C++ headers.
In this mode, C++ classes will be mapped to Ada tagged types, constructors
will be mapped using the @code{CPP_Constructor} pragma, and when possible,
multiple inheritance of abstract classes will be mapped to Ada interfaces
-(see the `Interfacing to C++' section in the @cite{GNAT Reference Manual}
+(see the @emph{Interfacing to C++} section in the @cite{GNAT Reference Manual}
for additional information on interfacing to C++).
For example, given the following C++ header file:
@@ -6705,7 +6707,7 @@ only.
@table @asis
-@item @code{-fada-spec-parent=`unit'}
+@item @code{-fada-spec-parent=@emph{unit}}
Specifies that all files generated by @code{-fdump-ada-spec} are
to be child units of the specified parent unit.
@@ -6856,7 +6858,7 @@ used for Ada 83.
The GNAT model of compilation is close to the C and C++ models. You can
think of Ada specs as corresponding to header files in C. As in C, you
don’t need to compile specs; they are compiled when they are used. The
-Ada `with' is similar in effect to the @code{#include} of a C
+Ada @emph{with} is similar in effect to the @code{#include} of a C
header.
One notable difference is that, in Ada, you may compile specs separately
@@ -6906,7 +6908,7 @@ previously compiled. In particular:
@itemize *
@item
-When a unit is `with'ed, the unit seen by the compiler corresponds
+When a unit is @emph{with}ed, the unit seen by the compiler corresponds
to the version of the unit most recently compiled into the library.
@item
@@ -6925,7 +6927,7 @@ files can affect the results of a compilation. In particular:
@itemize *
@item
-When a unit is `with'ed, the unit seen by the compiler corresponds
+When a unit is @emph{with}ed, the unit seen by the compiler corresponds
to the source version of the unit that is currently accessible to the
compiler.
@@ -7118,8 +7120,8 @@ dependencies, they will always be tracked exactly correctly by
@code{gnatmake}.
Note that for advanced forms of project structure, we recommend creating
-a project file as explained in the `GNAT_Project_Manager' chapter in the
-`GPRbuild User’s Guide', and using the
+a project file as explained in the @emph{GNAT_Project_Manager} chapter in the
+@emph{GPRbuild User’s Guide}, and using the
@code{gprbuild} tool which supports building with project files and works similarly
to @code{gnatmake}.
@@ -7201,7 +7203,7 @@ all other options.
@table @asis
-@item @code{-P`project'}
+@item @code{-P@emph{project}}
Build GNAT project file @code{project} using GPRbuild. When this switch is
present, all other command-line switches are treated as GPRbuild switches
@@ -7216,7 +7218,7 @@ and not @code{gnatmake} switches.
@table @asis
-@item @code{--GCC=`compiler_name'}
+@item @code{--GCC=@emph{compiler_name}}
Program used for compiling. The default is @code{gcc}. You need to use
quotes around @code{compiler_name} if @code{compiler_name} contains
@@ -7239,7 +7241,7 @@ all the additional switches are also taken into account. Thus,
@table @asis
-@item @code{--GNATBIND=`binder_name'}
+@item @code{--GNATBIND=@emph{binder_name}}
Program used for binding. The default is @code{gnatbind}. You need to
use quotes around @code{binder_name} if @code{binder_name} contains spaces
@@ -7257,7 +7259,7 @@ itself must not include any embedded spaces.
@table @asis
-@item @code{--GNATLINK=`linker_name'}
+@item @code{--GNATLINK=@emph{linker_name}}
Program used for linking. The default is @code{gnatlink}. You need to
use quotes around @code{linker_name} if @code{linker_name} contains spaces
@@ -7274,7 +7276,7 @@ itself must not include any embedded spaces.
When linking an executable, create a map file. The name of the map file
has the same name as the executable with extension “.map”.
-@item @code{--create-map-file=`mapfile'}
+@item @code{--create-map-file=@emph{mapfile}}
When linking an executable, create a map file with the specified name.
@end table
@@ -7286,7 +7288,7 @@ When linking an executable, create a map file with the specified name.
@item @code{--create-missing-dirs}
-When using project files (@code{-P`project'}), automatically create
+When using project files (@code{-P@emph{project}}), automatically create
missing object directories, library directories and exec
directories.
@@ -7295,7 +7297,7 @@ directories.
Disallow simultaneous compilations in the same object directory when
project files are used.
-@item @code{--subdirs=`subdir'}
+@item @code{--subdirs=@emph{subdir}}
Actual object directory of each project file is the subdirectory subdir of the
object directory specified or defaulted in the project file.
@@ -7306,7 +7308,7 @@ By default, shared library projects are not allowed to import static library
projects. When this switch is used on the command line, this restriction is
relaxed.
-@item @code{--source-info=`source info file'}
+@item @code{--source-info=@emph{source info file}}
Specify a source info file. This switch is active only when project files
are used. If the source info file is specified as a relative path, then it is
@@ -7417,7 +7419,7 @@ will add any newly accessed sources to the mapping file.
@table @asis
-@item @code{-C=`file'}
+@item @code{-C=@emph{file}}
Use a specific mapping file. The file, specified as a path name (absolute or
relative) by this switch, should already exist, otherwise the switch is
@@ -7449,7 +7451,7 @@ the compiler. These lines are displayed even in quiet output mode.
@table @asis
-@item @code{-D `dir'}
+@item @code{-D @emph{dir}}
Put all object files and ALI file in directory @code{dir}.
If the @code{-D} switch is not used, all object files
@@ -7463,7 +7465,7 @@ This switch cannot be used when using a project file.
@table @asis
-@item @code{-eI`nnn'}
+@item @code{-eI@emph{nnn}}
Indicates that the main source is a multi-unit source and the rank of the unit
in the source file is nnn. nnn needs to be a positive number and a valid
@@ -7575,7 +7577,7 @@ object and ALI files in the directory where it found the dummy file.
@table @asis
-@item @code{-j`n'}
+@item @code{-j@emph{n}}
Use @code{n} processes to carry out the (re)compilations. On a multiprocessor
machine compilations will occur in parallel. If @code{n} is 0, then the
@@ -7667,7 +7669,7 @@ is typically what you want. If you also specify
the @code{-a} switch,
dependencies of the GNAT internal files are also listed. Note that
dependencies of the objects in external Ada libraries (see
-switch @code{-aL`dir'} in the following list)
+switch @code{-aL@emph{dir}} in the following list)
are never reported.
@end table
@@ -7690,7 +7692,7 @@ file, will eventually result in recompiling all required units.
@table @asis
-@item @code{-o `exec_name'}
+@item @code{-o @emph{exec_name}}
Output executable name. The name of the final executable program will be
@code{exec_name}. If the @code{-o} switch is omitted the default
@@ -7808,7 +7810,7 @@ Verbosity level Medium. Potentially display fewer lines than in verbosity High.
Verbosity level High. Equivalent to -v.
-@item @code{-vP`x'}
+@item @code{-vP@emph{x}}
Indicate the verbosity of the parsing of GNAT project files.
See @ref{d1,,Switches Related to Project Files}.
@@ -7830,7 +7832,7 @@ be those specified on the command line. Even when
@code{-x} is used, mains specified on the
command line need to be sources of a project file.
-@item @code{-X`name'=`value'}
+@item @code{-X@emph{name}=@emph{value}}
Indicate that external variable @code{name} has the value @code{value}.
The Project Manager will use this value for occurrences of
@@ -7865,7 +7867,7 @@ is passed to @code{gcc} (e.g., @code{-O}, @code{-gnato,} etc.)
@table @asis
-@item @code{-aI`dir'}
+@item @code{-aI@emph{dir}}
When looking for source files also look in directory @code{dir}.
The order in which source files search is undertaken is
@@ -7877,7 +7879,7 @@ described in @ref{73,,Search Paths and the Run-Time Library (RTL)}.
@table @asis
-@item @code{-aL`dir'}
+@item @code{-aL@emph{dir}}
Consider @code{dir} as being an externally provided Ada library.
Instructs @code{gnatmake} to skip compilation units whose @code{.ALI}
@@ -7885,7 +7887,7 @@ files have been located in directory @code{dir}. This allows you to have
missing bodies for the units in @code{dir} and to ignore out of date bodies
for the same units. You still need to specify
the location of the specs for these units by using the switches
-@code{-aI`dir'} or @code{-I`dir'}.
+@code{-aI@emph{dir}} or @code{-I@emph{dir}}.
Note: this switch is provided for compatibility with previous versions
of @code{gnatmake}. The easier method of causing standard libraries
to be excluded from consideration is to write-protect the corresponding
@@ -7897,7 +7899,7 @@ ALI files.
@table @asis
-@item @code{-aO`dir'}
+@item @code{-aO@emph{dir}}
When searching for library and object files, look in directory
@code{dir}. The order in which library files are searched is described in
@@ -7912,15 +7914,15 @@ When searching for library and object files, look in directory
@table @asis
-@item @code{-A`dir'}
+@item @code{-A@emph{dir}}
-Equivalent to @code{-aL`dir'} @code{-aI`dir'}.
+Equivalent to @code{-aL@emph{dir}} @code{-aI@emph{dir}}.
@geindex -I (gnatmake)
-@item @code{-I`dir'}
+@item @code{-I@emph{dir}}
-Equivalent to @code{-aO`dir' -aI`dir'}.
+Equivalent to @code{-aO@emph{dir} -aI@emph{dir}}.
@end table
@geindex -I- (gnatmake)
@@ -7946,11 +7948,11 @@ where @code{gnatmake} was invoked.
@table @asis
-@item @code{-L`dir'}
+@item @code{-L@emph{dir}}
Add directory @code{dir} to the list of directories in which the linker
will search for libraries. This is equivalent to
-@code{-largs} @code{-L`dir'}.
+@code{-largs} @code{-L@emph{dir}}.
Furthermore, under Windows, the sources pointed to by the libraries path
set in the registry are not searched for.
@end table
@@ -7980,7 +7982,7 @@ Do not look for library files in the system default directory.
@table @asis
-@item @code{--RTS=`rts-path'}
+@item @code{--RTS=@emph{rts-path}}
Specifies the default location of the run-time library. GNAT looks for the
run-time
@@ -7992,13 +7994,13 @@ in the following directories, and stops as soon as a valid run-time is found
@itemize *
@item
-`<current directory>/$rts_path'
+@emph{<current directory>/$rts_path}
@item
-`<default-search-dir>/$rts_path'
+@emph{<default-search-dir>/$rts_path}
@item
-`<default-search-dir>/rts-$rts_path'
+@emph{<default-search-dir>/rts-$rts_path}
@item
The selected path is handled like a normal RTS path.
@@ -8022,7 +8024,7 @@ designated component of GNAT.
@table @asis
-@item @code{-cargs `switches'}
+@item @code{-cargs @emph{switches}}
Compiler switches. Here @code{switches} is a list of switches
that are valid switches for @code{gcc}. They will be passed on to
@@ -8034,7 +8036,7 @@ all compile steps performed by @code{gnatmake}.
@table @asis
-@item @code{-bargs `switches'}
+@item @code{-bargs @emph{switches}}
Binder switches. Here @code{switches} is a list of switches
that are valid switches for @code{gnatbind}. They will be passed on to
@@ -8046,7 +8048,7 @@ all bind steps performed by @code{gnatmake}.
@table @asis
-@item @code{-largs `switches'}
+@item @code{-largs @emph{switches}}
Linker switches. Here @code{switches} is a list of switches
that are valid switches for @code{gnatlink}. They will be passed on to
@@ -8058,7 +8060,7 @@ all link steps performed by @code{gnatmake}.
@table @asis
-@item @code{-margs `switches'}
+@item @code{-margs @emph{switches}}
Make switches. The switches are directly interpreted by @code{gnatmake},
regardless of any previous occurrence of @code{-cargs}, @code{-bargs}
@@ -8110,9 +8112,9 @@ unless @code{-a} is also specified.
@item
@code{gnatmake} has been designed to make the use of Ada libraries
particularly convenient. Assume you have an Ada library organized
-as follows: `obj-dir' contains the objects and ALI files for
+as follows: @emph{obj-dir} contains the objects and ALI files for
of your Ada compilation units,
-whereas `include-dir' contains the
+whereas @emph{include-dir} contains the
specs of these units, but no bodies. Then to compile a unit
stored in @code{main.adb}, which uses this Ada library you would just type:
@@ -8146,7 +8148,7 @@ it may be useful to have some basic understanding of the @code{gnatmake}
approach and in particular to understand how it uses the results of
previous compilations without incorrectly depending on them.
-First a definition: an object file is considered `up to date' if the
+First a definition: an object file is considered @emph{up to date} if the
corresponding ALI file exists and if all the source files listed in the
dependency section of this ALI file have time stamps matching those in
the ALI file. This means that neither the source file itself nor any
@@ -8256,7 +8258,7 @@ the body file (@code{.adb}) for a library level package
or generic package that has a body
@end itemize
-You need `not' compile the following files
+You need @emph{not} compile the following files
@itemize *
@@ -8481,7 +8483,7 @@ file directly.
@item
When you compile a unit, the source files for the specs of all units
-that it `with's, all its subunits, and the bodies of any generics it
+that it @emph{with}s, all its subunits, and the bodies of any generics it
instantiates must be available (reachable by the search-paths mechanism
described above), or you will receive a fatal error message.
@end itemize
@@ -8563,7 +8565,7 @@ compilation units.
@table @asis
-@item @code{-b `target'}
+@item @code{-b @emph{target}}
Compile your program to run on @code{target}, which is the name of a
system configuration. You must have a GNAT cross-compiler built if
@@ -8575,7 +8577,7 @@ system configuration. You must have a GNAT cross-compiler built if
@table @asis
-@item @code{-B`dir'}
+@item @code{-B@emph{dir}}
Load compiler executables (for example, @code{gnat1}, the Ada compiler)
from @code{dir} instead of the default location. Only use this switch
@@ -8661,7 +8663,7 @@ emitted in the debug information.
@table @asis
-@item @code{-flto[=`n']}
+@item @code{-flto[=@emph{n}]}
Enables Link Time Optimization. This switch must be used in conjunction
with the @code{-Ox} switches (but not with the @code{-gnatn} switch
@@ -9052,7 +9054,7 @@ ALI files.
@table @asis
-@item @code{-gnatec=`path'}
+@item @code{-gnatec=@emph{path}}
Specify a configuration pragma file
(the equal sign is optional)
@@ -9086,7 +9088,7 @@ Disable atomic synchronization
@table @asis
-@item @code{-gnateDsymbol[=`value']}
+@item @code{-gnateDsymbol[=@emph{value}]}
Defines a symbol, associated with @code{value}, for preprocessing.
(@ref{91,,Integrated Preprocessing}).
@@ -9170,7 +9172,7 @@ used to be 64 in earlier versions of the compiler.
@table @asis
-@item @code{-gnatei`nnn'}
+@item @code{-gnatei@emph{nnn}}
Set maximum number of instantiations during compilation of a single unit to
@code{nnn}. This may be useful in increasing the default maximum of 8000 for
@@ -9182,7 +9184,7 @@ the rare case when a single unit legitimately exceeds this limit.
@table @asis
-@item @code{-gnateI`nnn'}
+@item @code{-gnateI@emph{nnn}}
Indicates that the source is a multi-unit source and that the index of the
unit to compile is @code{nnn}. @code{nnn} needs to be a positive number and need
@@ -9221,7 +9223,7 @@ This switch turns off the info messages about implicit elaboration pragmas.
@table @asis
-@item @code{-gnatem=`path'}
+@item @code{-gnatem=@emph{path}}
Specify a mapping file
(the equal sign is optional)
@@ -9233,7 +9235,7 @@ Specify a mapping file
@table @asis
-@item @code{-gnatep=`file'}
+@item @code{-gnatep=@emph{file}}
Specify a preprocessing data file
(the equal sign is optional)
@@ -9270,7 +9272,7 @@ Synonym of @code{-fdump-scos}, kept for backwards compatibility.
@table @asis
-@item @code{-gnatet=`path'}
+@item @code{-gnatet=@emph{path}}
Generate target dependent information. The format of the output file is
described in the section about switch @code{-gnateT}.
@@ -9281,7 +9283,7 @@ described in the section about switch @code{-gnateT}.
@table @asis
-@item @code{-gnateT=`path'}
+@item @code{-gnateT=@emph{path}}
Read target dependent information, such as endianness or sizes and alignments
of base type. If this switch is passed, the default target dependent
@@ -9537,7 +9539,7 @@ For further details see @ref{f,,Elaboration Order Handling in GNAT}.
@table @asis
-@item @code{-gnati`c'}
+@item @code{-gnati@emph{c}}
Identifier character set (@code{c} = 1/2/3/4/5/9/p/8/f/n/w).
For details of the possible selections for @code{c},
@@ -9570,7 +9572,7 @@ code is likely to malfunction at run time.
@table @asis
-@item @code{-gnatj`nn'}
+@item @code{-gnatj@emph{nn}}
Reformat error messages to fit on @code{nn} character lines
@end table
@@ -9631,7 +9633,7 @@ details see @ref{f,,Elaboration Order Handling in GNAT}.
@table @asis
-@item @code{-gnatk=`n'}
+@item @code{-gnatk=@emph{n}}
Limit file names to @code{n} (1-999) characters (@code{k} = krunch).
@end table
@@ -9663,7 +9665,7 @@ source output.
@table @asis
-@item @code{-gnatm=`n'}
+@item @code{-gnatm=@emph{n}}
Limit number of detected error or warning messages to @code{n}
where @code{n} is in the range 1..999999. The default setting if
@@ -9744,7 +9746,7 @@ Interpretation
@item
-`1'
+@emph{1}
@tab
@@ -9752,7 +9754,7 @@ All intermediate overflows checked against base type (@code{STRICT})
@item
-`2'
+@emph{2}
@tab
@@ -9760,7 +9762,7 @@ Minimize intermediate overflows (@code{MINIMIZED})
@item
-`3'
+@emph{3}
@tab
@@ -9883,7 +9885,7 @@ Print package Standard.
@table @asis
-@item @code{-gnatT`nnn'}
+@item @code{-gnatT@emph{nnn}}
All compiler tables start at @code{nnn} times usual starting size.
@end table
@@ -9933,7 +9935,7 @@ Control level of validity checking (@ref{e9,,Validity Checking}).
@table @asis
-@item @code{-gnatw`xxx'}
+@item @code{-gnatw@emph{xxx}}
Warning mode where
@code{xxx} is a string of option letters that denotes
@@ -9946,7 +9948,7 @@ are enabled or disabled (@ref{ed,,Warning Message Control}).
@table @asis
-@item @code{-gnatW`e'}
+@item @code{-gnatW@emph{e}}
Wide character encoding method
(@code{e}=n/h/u/s/e/8).
@@ -9997,7 +9999,7 @@ Enable built-in style checks (@ref{ee,,Style Checking}).
@table @asis
-@item @code{-gnatz`m'}
+@item @code{-gnatz@emph{m}}
Distribution stub generation and compilation
(@code{m}=r/c for receiver/caller stubs).
@@ -10008,7 +10010,7 @@ Distribution stub generation and compilation
@table @asis
-@item @code{-I`dir'}
+@item @code{-I@emph{dir}}
@geindex RTL
@@ -10036,7 +10038,7 @@ files in the directory containing the source file named in the command line
@table @asis
-@item @code{-o `file'}
+@item @code{-o @emph{file}}
This switch is used in @code{gcc} to redirect the generated object file
and its associated ALI file. Beware of this switch with GNAT, because it may
@@ -10071,7 +10073,7 @@ Library (RTL) ALI files.
@table @asis
-@item @code{-O[`n']}
+@item @code{-O[@emph{n}]}
@code{n} controls the optimization level:
@@ -10079,7 +10081,7 @@ Library (RTL) ALI files.
@multitable {xxxxxxxxx} {xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx}
@item
-`n'
+@emph{n}
@tab
@@ -10087,7 +10089,7 @@ Effect
@item
-`0'
+@emph{0}
@tab
@@ -10095,7 +10097,7 @@ No optimization, the default setting if no @code{-O} appears
@item
-`1'
+@emph{1}
@tab
@@ -10105,7 +10107,7 @@ time.
@item
-`2'
+@emph{2}
@tab
@@ -10114,7 +10116,7 @@ the cost of substantially increased compilation time.
@item
-`3'
+@emph{3}
@tab
@@ -10123,7 +10125,7 @@ subprograms in the same unit.
@item
-`s'
+@emph{s}
@tab
@@ -10151,7 +10153,7 @@ exit status.
@table @asis
-@item @code{--RTS=`rts-path'}
+@item @code{--RTS=@emph{rts-path}}
Specifies the default location of the run-time library. Same meaning as the
equivalent @code{gnatmake} flag (@ref{d0,,Switches for gnatmake}).
@@ -10200,7 +10202,7 @@ compiler you are executing.
@table @asis
-@item @code{-V `ver'}
+@item @code{-V @emph{ver}}
Execute @code{ver} version of the compiler. This is the @code{gcc}
version, not the GNAT version.
@@ -10399,7 +10401,7 @@ warning messages generated.
@table @asis
-@item @code{-gnatl=`fname'}
+@item @code{-gnatl=@emph{fname}}
This has the same effect as @code{-gnatl} except that the output is
written to a file instead of to standard output. If the given name
@@ -10443,7 +10445,7 @@ format message or full listing (which as usual is written to
@table @asis
-@item @code{-gnatm=`n'}
+@item @code{-gnatm=@emph{n}}
The @code{m} stands for maximum.
@code{n} is a decimal integer in the
@@ -10705,7 +10707,7 @@ Wrong length on string assignment
Violations of style rules if style checking is enabled
@item
-Unused `with' clauses
+Unused @emph{with} clauses
@item
@code{Bit_Order} usage that does not have any effect
@@ -10720,7 +10722,7 @@ Dereference of possibly null value
Declaration that is likely to cause storage error
@item
-Internal GNAT unit `with'ed by application unit
+Internal GNAT unit @emph{with}ed by application unit
@item
Values known to be out of range at compile time
@@ -10774,7 +10776,7 @@ of the pragma in the @cite{GNAT_Reference_manual}).
@item @code{-gnatwa}
-`Activate most optional warnings.'
+@emph{Activate most optional warnings.}
This switch activates most optional warning messages. See the remaining list
in this section for details on optional warning messages that can be
@@ -10855,7 +10857,7 @@ All other optional warnings are turned on.
@item @code{-gnatwA}
-`Suppress all optional errors.'
+@emph{Suppress all optional errors.}
This switch suppresses all optional warning messages, see remaining list
in this section for details on optional warning messages that can be
@@ -10877,7 +10879,7 @@ the warnings for implicit dereferencing.
@item @code{-gnatw.a}
-`Activate warnings on failing assertions.'
+@emph{Activate warnings on failing assertions.}
@geindex Assert failures
@@ -10894,7 +10896,7 @@ generated.
@item @code{-gnatw.A}
-`Suppress warnings on failing assertions.'
+@emph{Suppress warnings on failing assertions.}
@geindex Assert failures
@@ -10909,7 +10911,7 @@ compile time that the assertion will fail.
@item @code{-gnatw_a}
-`Activate warnings on anonymous allocators.'
+@emph{Activate warnings on anonymous allocators.}
@geindex Anonymous allocators
@@ -10926,7 +10928,7 @@ RM 3.10.2 (14).
@item @code{-gnatw_A}
-`Suppress warnings on anonymous allocators.'
+@emph{Suppress warnings on anonymous allocators.}
@geindex Anonymous allocators
@@ -10940,7 +10942,7 @@ This switch suppresses warnings for anonymous access type allocators.
@item @code{-gnatwb}
-`Activate warnings on bad fixed values.'
+@emph{Activate warnings on bad fixed values.}
@geindex Bad fixed values
@@ -10964,7 +10966,7 @@ are not generated.
@item @code{-gnatwB}
-`Suppress warnings on bad fixed values.'
+@emph{Suppress warnings on bad fixed values.}
This switch suppresses warnings for static fixed-point expressions whose
value is not an exact multiple of Small.
@@ -10977,7 +10979,7 @@ value is not an exact multiple of Small.
@item @code{-gnatw.b}
-`Activate warnings on biased representation.'
+@emph{Activate warnings on biased representation.}
@geindex Biased representation
@@ -10994,7 +10996,7 @@ to represent 10/11). The default is that such warnings are generated.
@item @code{-gnatw.B}
-`Suppress warnings on biased representation.'
+@emph{Suppress warnings on biased representation.}
This switch suppresses warnings for representation clauses that force the use
of biased representation.
@@ -11007,7 +11009,7 @@ of biased representation.
@item @code{-gnatwc}
-`Activate warnings on conditionals.'
+@emph{Activate warnings on conditionals.}
@geindex Conditionals
@geindex constant
@@ -11044,7 +11046,7 @@ This warning can also be turned on using @code{-gnatwa}.
@item @code{-gnatwC}
-`Suppress warnings on conditionals.'
+@emph{Suppress warnings on conditionals.}
This switch suppresses warnings for conditional expressions used in
tests that are known to be True or False at compile time.
@@ -11057,7 +11059,7 @@ tests that are known to be True or False at compile time.
@item @code{-gnatw.c}
-`Activate warnings on missing component clauses.'
+@emph{Activate warnings on missing component clauses.}
@geindex Component clause
@geindex missing
@@ -11075,7 +11077,7 @@ component for which no component clause is present.
@item @code{-gnatw.C}
-`Suppress warnings on missing component clauses.'
+@emph{Suppress warnings on missing component clauses.}
This switch suppresses warnings for record components that are
missing a component clause in the situation described above.
@@ -11088,7 +11090,7 @@ missing a component clause in the situation described above.
@item @code{-gnatw_c}
-`Activate warnings on unknown condition in Compile_Time_Warning.'
+@emph{Activate warnings on unknown condition in Compile_Time_Warning.}
@geindex Compile_Time_Warning
@@ -11107,7 +11109,7 @@ The default is that such warnings are generated.
@item @code{-gnatw_C}
-`Suppress warnings on unknown condition in Compile_Time_Warning.'
+@emph{Suppress warnings on unknown condition in Compile_Time_Warning.}
This switch suppresses warnings on a pragma Compile_Time_Warning
or Compile_Time_Error whose condition has a value that is not
@@ -11121,7 +11123,7 @@ known at compile time.
@item @code{-gnatwd}
-`Activate warnings on implicit dereferencing.'
+@emph{Activate warnings on implicit dereferencing.}
If this switch is set, then the use of a prefix of an access type
in an indexed component, slice, or selected component without an
@@ -11139,7 +11141,7 @@ warnings are not generated.
@item @code{-gnatwD}
-`Suppress warnings on implicit dereferencing.'
+@emph{Suppress warnings on implicit dereferencing.}
@geindex Implicit dereferencing
@@ -11157,7 +11159,7 @@ indexed components, slices, and selected components.
@item @code{-gnatw.d}
-`Activate tagging of warning and info messages.'
+@emph{Activate tagging of warning and info messages.}
If this switch is set, then warning messages are tagged, with one of the
following strings:
@@ -11168,35 +11170,35 @@ following strings:
@itemize -
@item
-`[-gnatw?]'
+@emph{[-gnatw?]}
Used to tag warnings controlled by the switch @code{-gnatwx} where x
is a letter a-z.
@item
-`[-gnatw.?]'
+@emph{[-gnatw.?]}
Used to tag warnings controlled by the switch @code{-gnatw.x} where x
is a letter a-z.
@item
-`[-gnatel]'
+@emph{[-gnatel]}
Used to tag elaboration information (info) messages generated when the
static model of elaboration is used and the @code{-gnatel} switch is set.
@item
-`[restriction warning]'
+@emph{[restriction warning]}
Used to tag warning messages for restriction violations, activated by use
of the pragma @code{Restriction_Warnings}.
@item
-`[warning-as-error]'
+@emph{[warning-as-error]}
Used to tag warning messages that have been converted to error messages by
use of the pragma Warning_As_Error. Note that such warnings are prefixed by
-the string “error: ” rather than “warning: “.
+the string “error: “ rather than “warning: “.
@item
-`[enabled by default]'
+@emph{[enabled by default]}
Used to tag all other warnings that are always given by default, unless
-warnings are completely suppressed using pragma `Warnings(Off)' or
+warnings are completely suppressed using pragma @emph{Warnings(Off)} or
the switch @code{-gnatws}.
@end itemize
@end quotation
@@ -11209,7 +11211,7 @@ the switch @code{-gnatws}.
@item @code{-gnatw.D}
-`Deactivate tagging of warning and info messages messages.'
+@emph{Deactivate tagging of warning and info messages messages.}
If this switch is set, then warning messages return to the default
mode in which warnings and info messages are not tagged as described above for
@@ -11226,7 +11228,7 @@ mode in which warnings and info messages are not tagged as described above for
@item @code{-gnatwe}
-`Treat warnings and style checks as errors.'
+@emph{Treat warnings and style checks as errors.}
This switch causes warning messages and style check messages to be
treated as errors.
@@ -11244,7 +11246,7 @@ are not treated as errors if this switch is present.
@item @code{-gnatw.e}
-`Activate every optional warning.'
+@emph{Activate every optional warning.}
@geindex Warnings
@geindex activate every optional warning
@@ -11268,7 +11270,7 @@ been specifically designed according to specialized coding rules.
@item @code{-gnatwE}
-`Treat all run-time exception warnings as errors.'
+@emph{Treat all run-time exception warnings as errors.}
This switch causes warning messages regarding errors that will be raised
during run-time execution to be treated as errors.
@@ -11281,7 +11283,7 @@ during run-time execution to be treated as errors.
@item @code{-gnatwf}
-`Activate warnings on unreferenced formals.'
+@emph{Activate warnings on unreferenced formals.}
@geindex Formals
@geindex unreferenced
@@ -11299,7 +11301,7 @@ default is that these warnings are not generated.
@item @code{-gnatwF}
-`Suppress warnings on unreferenced formals.'
+@emph{Suppress warnings on unreferenced formals.}
This switch suppresses warnings for unreferenced formal
parameters. Note that the
@@ -11315,7 +11317,7 @@ formals.
@item @code{-gnatwg}
-`Activate warnings on unrecognized pragmas.'
+@emph{Activate warnings on unrecognized pragmas.}
@geindex Pragmas
@geindex unrecognized
@@ -11334,7 +11336,7 @@ Manual requirement that such warnings appear).
@item @code{-gnatwG}
-`Suppress warnings on unrecognized pragmas.'
+@emph{Suppress warnings on unrecognized pragmas.}
This switch suppresses warnings for unrecognized pragmas.
@end table
@@ -11346,7 +11348,7 @@ This switch suppresses warnings for unrecognized pragmas.
@item @code{-gnatw.g}
-`Warnings used for GNAT sources.'
+@emph{Warnings used for GNAT sources.}
This switch sets the warning categories that are used by the standard
GNAT style. Currently this is equivalent to
@@ -11361,7 +11363,7 @@ but more warnings may be added in the future without advanced notice.
@item @code{-gnatwh}
-`Activate warnings on hiding.'
+@emph{Activate warnings on hiding.}
@geindex Hiding of Declarations
@@ -11378,7 +11380,7 @@ code. The default is that warnings on hiding are not generated.
@item @code{-gnatwH}
-`Suppress warnings on hiding.'
+@emph{Suppress warnings on hiding.}
This switch suppresses warnings on hiding declarations.
@end table
@@ -11390,7 +11392,7 @@ This switch suppresses warnings on hiding declarations.
@item @code{-gnatw.h}
-`Activate warnings on holes/gaps in records.'
+@emph{Activate warnings on holes/gaps in records.}
@geindex Record Representation (gaps)
@@ -11412,7 +11414,7 @@ fill fields.
@item @code{-gnatw.H}
-`Suppress warnings on holes/gaps in records.'
+@emph{Suppress warnings on holes/gaps in records.}
This switch suppresses warnings on component clauses in record
representation clauses that leave holes (haps) in the record layout.
@@ -11425,16 +11427,16 @@ representation clauses that leave holes (haps) in the record layout.
@item @code{-gnatwi}
-`Activate warnings on implementation units.'
+@emph{Activate warnings on implementation units.}
-This switch activates warnings for a `with' of an internal GNAT
+This switch activates warnings for a @emph{with} of an internal GNAT
implementation unit, defined as any unit from the @code{Ada},
@code{Interfaces}, @code{GNAT},
or @code{System}
hierarchies that is not
documented in either the Ada Reference Manual or the GNAT
Programmer’s Reference Manual. Such units are intended only
-for internal implementation purposes and should not be `with'ed
+for internal implementation purposes and should not be @emph{with}ed
by user programs. The default is that such warnings are generated
@end table
@@ -11445,9 +11447,9 @@ by user programs. The default is that such warnings are generated
@item @code{-gnatwI}
-`Disable warnings on implementation units.'
+@emph{Disable warnings on implementation units.}
-This switch disables warnings for a `with' of an internal GNAT
+This switch disables warnings for a @emph{with} of an internal GNAT
implementation unit.
@end table
@@ -11458,7 +11460,7 @@ implementation unit.
@item @code{-gnatw.i}
-`Activate warnings on overlapping actuals.'
+@emph{Activate warnings on overlapping actuals.}
This switch enables a warning on statically detectable overlapping actuals in
a subprogram call, when one of the actuals is an in-out parameter, and the
@@ -11472,7 +11474,7 @@ types of the actuals are not by-copy types. This warning is off by default.
@item @code{-gnatw.I}
-`Disable warnings on overlapping actuals.'
+@emph{Disable warnings on overlapping actuals.}
This switch disables warnings on overlapping actuals in a call.
@end table
@@ -11484,7 +11486,7 @@ This switch disables warnings on overlapping actuals in a call.
@item @code{-gnatwj}
-`Activate warnings on obsolescent features (Annex J).'
+@emph{Activate warnings on obsolescent features (Annex J).}
@geindex Features
@geindex obsolescent
@@ -11520,7 +11522,7 @@ Second, the restriction does flag uses of package @code{ASCII}.
@item @code{-gnatwJ}
-`Suppress warnings on obsolescent features (Annex J).'
+@emph{Suppress warnings on obsolescent features (Annex J).}
This switch disables warnings on use of obsolescent features.
@end table
@@ -11532,7 +11534,7 @@ This switch disables warnings on use of obsolescent features.
@item @code{-gnatw.j}
-`Activate warnings on late declarations of tagged type primitives.'
+@emph{Activate warnings on late declarations of tagged type primitives.}
This switch activates warnings on visible primitives added to a
tagged type after deriving a private extension from it.
@@ -11545,7 +11547,7 @@ tagged type after deriving a private extension from it.
@item @code{-gnatw.J}
-`Suppress warnings on late declarations of tagged type primitives.'
+@emph{Suppress warnings on late declarations of tagged type primitives.}
This switch suppresses warnings on visible primitives added to a
tagged type after deriving a private extension from it.
@@ -11558,7 +11560,7 @@ tagged type after deriving a private extension from it.
@item @code{-gnatwk}
-`Activate warnings on variables that could be constants.'
+@emph{Activate warnings on variables that could be constants.}
This switch activates warnings for variables that are initialized but
never modified, and then could be declared constants. The default is that
@@ -11572,7 +11574,7 @@ such warnings are not given.
@item @code{-gnatwK}
-`Suppress warnings on variables that could be constants.'
+@emph{Suppress warnings on variables that could be constants.}
This switch disables warnings on variables that could be declared constants.
@end table
@@ -11584,7 +11586,7 @@ This switch disables warnings on variables that could be declared constants.
@item @code{-gnatw.k}
-`Activate warnings on redefinition of names in standard.'
+@emph{Activate warnings on redefinition of names in standard.}
This switch activates warnings for declarations that declare a name that
is defined in package Standard. Such declarations can be confusing,
@@ -11601,7 +11603,7 @@ not included in this check.
@item @code{-gnatw.K}
-`Suppress warnings on redefinition of names in standard.'
+@emph{Suppress warnings on redefinition of names in standard.}
This switch disables warnings for declarations that declare a name that
is defined in package Standard.
@@ -11614,7 +11616,7 @@ is defined in package Standard.
@item @code{-gnatwl}
-`Activate warnings for elaboration pragmas.'
+@emph{Activate warnings for elaboration pragmas.}
@geindex Elaboration
@geindex warnings
@@ -11636,7 +11638,7 @@ are not generated.
@item @code{-gnatwL}
-`Suppress warnings for elaboration pragmas.'
+@emph{Suppress warnings for elaboration pragmas.}
This switch suppresses warnings for possible elaboration problems.
@end table
@@ -11648,7 +11650,7 @@ This switch suppresses warnings for possible elaboration problems.
@item @code{-gnatw.l}
-`List inherited aspects.'
+@emph{List inherited aspects.}
This switch causes the compiler to list inherited invariants,
preconditions, and postconditions from Type_Invariant’Class, Invariant’Class,
@@ -11662,7 +11664,7 @@ Pre’Class, and Post’Class aspects. Also list inherited subtype predicates.
@item @code{-gnatw.L}
-`Suppress listing of inherited aspects.'
+@emph{Suppress listing of inherited aspects.}
This switch suppresses listing of inherited aspects.
@end table
@@ -11674,7 +11676,7 @@ This switch suppresses listing of inherited aspects.
@item @code{-gnatwm}
-`Activate warnings on modified but unreferenced variables.'
+@emph{Activate warnings on modified but unreferenced variables.}
This switch activates warnings for variables that are assigned (using
an initialization value or with one or more assignment statements) but
@@ -11691,7 +11693,7 @@ The default is that these warnings are not given.
@item @code{-gnatwM}
-`Disable warnings on modified but unreferenced variables.'
+@emph{Disable warnings on modified but unreferenced variables.}
This switch disables warnings for variables that are assigned or
initialized, but never read.
@@ -11704,7 +11706,7 @@ initialized, but never read.
@item @code{-gnatw.m}
-`Activate warnings on suspicious modulus values.'
+@emph{Activate warnings on suspicious modulus values.}
This switch activates warnings for modulus values that seem suspicious.
The cases caught are where the size is the same as the modulus (e.g.
@@ -11724,7 +11726,7 @@ integers after wrap-around. The default is that these warnings are given.
@item @code{-gnatw.M}
-`Disable warnings on suspicious modulus values.'
+@emph{Disable warnings on suspicious modulus values.}
This switch disables warnings for suspicious modulus values.
@end table
@@ -11736,7 +11738,7 @@ This switch disables warnings for suspicious modulus values.
@item @code{-gnatwn}
-`Set normal warnings mode.'
+@emph{Set normal warnings mode.}
This switch sets normal warning mode, in which enabled warnings are
issued and treated as warnings rather than errors. This is the default
@@ -11757,7 +11759,7 @@ use of @code{-gnatg}.
@item @code{-gnatw.n}
-`Activate warnings on atomic synchronization.'
+@emph{Activate warnings on atomic synchronization.}
This switch actives warnings when an access to an atomic variable
requires the generation of atomic synchronization code. These
@@ -11771,7 +11773,7 @@ warnings are off by default.
@item @code{-gnatw.N}
-`Suppress warnings on atomic synchronization.'
+@emph{Suppress warnings on atomic synchronization.}
@geindex Atomic Synchronization
@geindex warnings
@@ -11790,7 +11792,7 @@ requires the generation of atomic synchronization code.
@item @code{-gnatwo}
-`Activate warnings on address clause overlays.'
+@emph{Activate warnings on address clause overlays.}
This switch activates warnings for possibly unintended initialization
effects of defining address clauses that cause one variable to overlap
@@ -11804,7 +11806,7 @@ another. The default is that such warnings are generated.
@item @code{-gnatwO}
-`Suppress warnings on address clause overlays.'
+@emph{Suppress warnings on address clause overlays.}
This switch suppresses warnings on possibly unintended initialization
effects of defining address clauses that cause one variable to overlap
@@ -11818,7 +11820,7 @@ another.
@item @code{-gnatw.o}
-`Activate warnings on modified but unreferenced out parameters.'
+@emph{Activate warnings on modified but unreferenced out parameters.}
This switch activates warnings for variables that are modified by using
them as actuals for a call to a procedure with an out mode formal, where
@@ -11838,7 +11840,7 @@ The default is that these warnings are not given.
@item @code{-gnatw.O}
-`Disable warnings on modified but unreferenced out parameters.'
+@emph{Disable warnings on modified but unreferenced out parameters.}
This switch suppresses warnings for variables that are modified by using
them as actuals for a call to a procedure with an out mode formal, where
@@ -11855,7 +11857,7 @@ the resulting assigned value is never read.
@item @code{-gnatwp}
-`Activate warnings on ineffective pragma Inlines.'
+@emph{Activate warnings on ineffective pragma Inlines.}
This switch activates warnings for failure of front end inlining
(activated by @code{-gnatN}) to inline a particular call. There are
@@ -11873,7 +11875,7 @@ separately, using the gcc switch -Winline.
@item @code{-gnatwP}
-`Suppress warnings on ineffective pragma Inlines.'
+@emph{Suppress warnings on ineffective pragma Inlines.}
This switch suppresses warnings on ineffective pragma Inlines. If the
inlining mechanism cannot inline a call, it will simply ignore the
@@ -11890,7 +11892,7 @@ request silently.
@item @code{-gnatw.p}
-`Activate warnings on parameter ordering.'
+@emph{Activate warnings on parameter ordering.}
This switch activates warnings for cases of suspicious parameter
ordering when the list of arguments are all simple identifiers that
@@ -11908,7 +11910,7 @@ default is that such warnings are not given.
@item @code{-gnatw.P}
-`Suppress warnings on parameter ordering.'
+@emph{Suppress warnings on parameter ordering.}
This switch suppresses warnings on cases of suspicious parameter
ordering.
@@ -11921,7 +11923,7 @@ ordering.
@item @code{-gnatw_p}
-`Activate warnings for pedantic checks.'
+@emph{Activate warnings for pedantic checks.}
This switch activates warnings for the failure of certain pedantic checks.
The only case currently supported is a check that the subtype_marks given
@@ -11937,7 +11939,7 @@ is that such warnings are not given.
@item @code{-gnatw_P}
-`Suppress warnings for pedantic checks.'
+@emph{Suppress warnings for pedantic checks.}
This switch suppresses warnings on violations of pedantic checks.
@end table
@@ -11952,7 +11954,7 @@ This switch suppresses warnings on violations of pedantic checks.
@item @code{-gnatwq}
-`Activate warnings on questionable missing parentheses.'
+@emph{Activate warnings on questionable missing parentheses.}
This switch activates warnings for cases where parentheses are not used and
the result is potential ambiguity from a readers point of view. For example
@@ -11971,7 +11973,7 @@ is that these warnings are given.
@item @code{-gnatwQ}
-`Suppress warnings on questionable missing parentheses.'
+@emph{Suppress warnings on questionable missing parentheses.}
This switch suppresses warnings for cases where the association is not
clear and the use of parentheses is preferred.
@@ -11987,7 +11989,7 @@ clear and the use of parentheses is preferred.
@item @code{-gnatw.q}
-`Activate warnings on questionable layout of record types.'
+@emph{Activate warnings on questionable layout of record types.}
This switch activates warnings for cases where the default layout of
a record type, that is to say the layout of its components in textual
@@ -12041,7 +12043,7 @@ The default is that these warnings are not given.
@item @code{-gnatw.Q}
-`Suppress warnings on questionable layout of record types.'
+@emph{Suppress warnings on questionable layout of record types.}
This switch suppresses warnings for cases where the default layout of
a record type would very likely cause inefficiencies.
@@ -12054,7 +12056,7 @@ a record type would very likely cause inefficiencies.
@item @code{-gnatw_q}
-`Activate warnings for ignored equality operators.'
+@emph{Activate warnings for ignored equality operators.}
This switch activates warnings for a user-defined “=” function that does
not compose (i.e. is ignored for a predefined “=” for a composite type
@@ -12074,7 +12076,7 @@ The default is that these warnings are not given.
@item @code{-gnatw_Q}
-`Suppress warnings for ignored equality operators.'
+@emph{Suppress warnings for ignored equality operators.}
@end table
@geindex -gnatwr (gcc)
@@ -12084,7 +12086,7 @@ The default is that these warnings are not given.
@item @code{-gnatwr}
-`Activate warnings on redundant constructs.'
+@emph{Activate warnings on redundant constructs.}
This switch activates warnings for redundant constructs. The following
is the current list of constructs regarded as redundant:
@@ -12132,7 +12134,7 @@ The default is that warnings for redundant constructs are not given.
@item @code{-gnatwR}
-`Suppress warnings on redundant constructs.'
+@emph{Suppress warnings on redundant constructs.}
This switch suppresses warnings for redundant constructs.
@end table
@@ -12144,7 +12146,7 @@ This switch suppresses warnings for redundant constructs.
@item @code{-gnatw.r}
-`Activate warnings for object renaming function.'
+@emph{Activate warnings for object renaming function.}
This switch activates warnings for an object renaming that renames a
function call, which is equivalent to a constant declaration (as
@@ -12159,7 +12161,7 @@ warnings are given.
@item @code{-gnatw.R}
-`Suppress warnings for object renaming function.'
+@emph{Suppress warnings for object renaming function.}
This switch suppresses warnings for object renaming function.
@end table
@@ -12171,7 +12173,7 @@ This switch suppresses warnings for object renaming function.
@item @code{-gnatw_r}
-`Activate warnings for out-of-order record representation clauses.'
+@emph{Activate warnings for out-of-order record representation clauses.}
This switch activates warnings for record representation clauses,
if the order of component declarations, component clauses,
@@ -12186,7 +12188,7 @@ The default is that these warnings are not given.
@item @code{-gnatw_R}
-`Suppress warnings for out-of-order record representation clauses.'
+@emph{Suppress warnings for out-of-order record representation clauses.}
@end table
@geindex -gnatws (gcc)
@@ -12196,7 +12198,7 @@ The default is that these warnings are not given.
@item @code{-gnatws}
-`Suppress all warnings.'
+@emph{Suppress all warnings.}
This switch completely suppresses the
output of all warning messages from the GNAT front end, including
@@ -12221,7 +12223,7 @@ handling of style check messages.
@item @code{-gnatw.s}
-`Activate warnings on overridden size clauses.'
+@emph{Activate warnings on overridden size clauses.}
This switch activates warnings on component clauses in record
representation clauses where the length given overrides that
@@ -12238,7 +12240,7 @@ component type.
@item @code{-gnatw.S}
-`Suppress warnings on overridden size clauses.'
+@emph{Suppress warnings on overridden size clauses.}
This switch suppresses warnings on component clauses in record
representation clauses that override size clauses, and similar
@@ -12254,7 +12256,7 @@ warnings when an array component size overrides a size clause.
@item @code{-gnatw_s}
-`Activate warnings on ineffective predicate tests.'
+@emph{Activate warnings on ineffective predicate tests.}
This switch activates warnings on Static_Predicate aspect
specifications that test for values that do not belong to
@@ -12268,7 +12270,7 @@ the parent subtype. Not all such ineffective tests are detected.
@item @code{-gnatw_S}
-`Suppress warnings on ineffective predicate tests.'
+@emph{Suppress warnings on ineffective predicate tests.}
This switch suppresses warnings on Static_Predicate aspect
specifications that test for values that do not belong to
@@ -12288,7 +12290,7 @@ the parent subtype.
@item @code{-gnatwt}
-`Activate warnings for tracking of deleted conditional code.'
+@emph{Activate warnings for tracking of deleted conditional code.}
This switch activates warnings for tracking of code in conditionals (IF and
CASE statements) that is detected to be dead code which cannot be executed, and
@@ -12303,7 +12305,7 @@ useful for detecting deactivated code in certified applications.
@item @code{-gnatwT}
-`Suppress warnings for tracking of deleted conditional code.'
+@emph{Suppress warnings for tracking of deleted conditional code.}
This switch suppresses warnings for tracking of deleted conditional code.
@end table
@@ -12315,7 +12317,7 @@ This switch suppresses warnings for tracking of deleted conditional code.
@item @code{-gnatw.t}
-`Activate warnings on suspicious contracts.'
+@emph{Activate warnings on suspicious contracts.}
This switch activates warnings on suspicious contracts. This includes
warnings on suspicious postconditions (whether a pragma @code{Postcondition} or a
@@ -12337,7 +12339,7 @@ warnings are generated.
@item @code{-gnatw.T}
-`Suppress warnings on suspicious contracts.'
+@emph{Suppress warnings on suspicious contracts.}
This switch suppresses warnings on suspicious contracts.
@end table
@@ -12349,22 +12351,22 @@ This switch suppresses warnings on suspicious contracts.
@item @code{-gnatwu}
-`Activate warnings on unused entities.'
+@emph{Activate warnings on unused entities.}
This switch activates warnings to be generated for entities that
-are declared but not referenced, and for units that are `with'ed
+are declared but not referenced, and for units that are @emph{with}ed
and not
referenced. In the case of packages, a warning is also generated if
no entities in the package are referenced. This means that if a with’ed
package is referenced but the only references are in @code{use}
clauses or @code{renames}
declarations, a warning is still generated. A warning is also generated
-for a generic package that is `with'ed but never instantiated.
+for a generic package that is @emph{with}ed but never instantiated.
In the case where a package or subprogram body is compiled, and there
-is a `with' on the corresponding spec
+is a @emph{with} on the corresponding spec
that is only referenced in the body,
a warning is also generated, noting that the
-`with' can be moved to the body. The default is that
+@emph{with} can be moved to the body. The default is that
such warnings are not generated.
This switch also activates warnings on unreferenced formals
(it includes the effect of @code{-gnatwf}).
@@ -12377,7 +12379,7 @@ This switch also activates warnings on unreferenced formals
@item @code{-gnatwU}
-`Suppress warnings on unused entities.'
+@emph{Suppress warnings on unused entities.}
This switch suppresses warnings for unused entities and packages.
It also turns off warnings on unreferenced formals (and thus includes
@@ -12391,13 +12393,13 @@ the effect of @code{-gnatwF}).
@item @code{-gnatw.u}
-`Activate warnings on unordered enumeration types.'
+@emph{Activate warnings on unordered enumeration types.}
This switch causes enumeration types to be considered as conceptually
unordered, unless an explicit pragma @code{Ordered} is given for the type.
The effect is to generate warnings in clients that use explicit comparisons
or subranges, since these constructs both treat objects of the type as
-ordered. (A `client' is defined as a unit that is other than the unit in
+ordered. (A @emph{client} is defined as a unit that is other than the unit in
which the type is declared, or its body or subunits.) Please refer to
the description of pragma @code{Ordered} in the
@cite{GNAT Reference Manual} for further details.
@@ -12411,7 +12413,7 @@ The default is that such warnings are not generated.
@item @code{-gnatw.U}
-`Deactivate warnings on unordered enumeration types.'
+@emph{Deactivate warnings on unordered enumeration types.}
This switch causes all enumeration types to be considered as ordered, so
that no warnings are given for comparisons or subranges for any type.
@@ -12426,7 +12428,7 @@ that no warnings are given for comparisons or subranges for any type.
@item @code{-gnatwv}
-`Activate warnings on unassigned variables.'
+@emph{Activate warnings on unassigned variables.}
This switch activates warnings for access to variables which
may not be properly initialized. The default is that
@@ -12447,7 +12449,7 @@ unless the relevant type fully initializes all components.
@item @code{-gnatwV}
-`Suppress warnings on unassigned variables.'
+@emph{Suppress warnings on unassigned variables.}
This switch suppresses warnings for access to variables which
may not be properly initialized.
@@ -12462,7 +12464,7 @@ may not be properly initialized.
@item @code{-gnatw.v}
-`Activate info messages for non-default bit order.'
+@emph{Activate info messages for non-default bit order.}
This switch activates messages (labeled “info”, they are not warnings,
just informational messages) about the effects of non-default bit-order
@@ -12479,7 +12481,7 @@ exact consequences of using this feature.
@item @code{-gnatw.V}
-`Suppress info messages for non-default bit order.'
+@emph{Suppress info messages for non-default bit order.}
This switch suppresses information messages for the effects of specifying
non-default bit order on record components with component clauses.
@@ -12494,7 +12496,7 @@ non-default bit order on record components with component clauses.
@item @code{-gnatww}
-`Activate warnings on wrong low bound assumption.'
+@emph{Activate warnings on wrong low bound assumption.}
This switch activates warnings for indexing an unconstrained string parameter
with a literal or S’Length. This is a case where the code is assuming that the
@@ -12509,7 +12511,7 @@ passed). The default is that such warnings are generated.
@item @code{-gnatwW}
-`Suppress warnings on wrong low bound assumption.'
+@emph{Suppress warnings on wrong low bound assumption.}
This switch suppresses warnings for indexing an unconstrained string parameter
with a literal or S’Length. Note that this warning can also be suppressed
@@ -12532,7 +12534,7 @@ procedure K (S : String) is
@item @code{-gnatw.w}
-`Activate warnings on Warnings Off pragmas.'
+@emph{Activate warnings on Warnings Off pragmas.}
This switch activates warnings for use of @code{pragma Warnings (Off, entity)}
where either the pragma is entirely useless (because it suppresses no
@@ -12551,7 +12553,7 @@ The default is that these warnings are not given.
@item @code{-gnatw.W}
-`Suppress warnings on unnecessary Warnings Off pragmas.'
+@emph{Suppress warnings on unnecessary Warnings Off pragmas.}
This switch suppresses warnings for use of @code{pragma Warnings (Off, ...)}.
@end table
@@ -12565,7 +12567,7 @@ This switch suppresses warnings for use of @code{pragma Warnings (Off, ...)}.
@item @code{-gnatwx}
-`Activate warnings on Export/Import pragmas.'
+@emph{Activate warnings on Export/Import pragmas.}
This switch activates warnings on Export/Import pragmas when
the compiler detects a possible conflict between the Ada and
@@ -12583,7 +12585,7 @@ generated.
@item @code{-gnatwX}
-`Suppress warnings on Export/Import pragmas.'
+@emph{Suppress warnings on Export/Import pragmas.}
This switch suppresses warnings on Export/Import pragmas.
The sense of this is that you are telling the compiler that
@@ -12598,7 +12600,7 @@ should not complain at you.
@item @code{-gnatw.x}
-`Activate warnings for No_Exception_Propagation mode.'
+@emph{Activate warnings for No_Exception_Propagation mode.}
This switch activates warnings for exception usage when pragma Restrictions
(No_Exception_Propagation) is in effect. Warnings are given for implicit or
@@ -12608,7 +12610,7 @@ these warnings are given for units that contain exception handlers.
@item @code{-gnatw.X}
-`Disable warnings for No_Exception_Propagation mode.'
+@emph{Disable warnings for No_Exception_Propagation mode.}
This switch disables warnings for exception usage when pragma Restrictions
(No_Exception_Propagation) is in effect.
@@ -12623,7 +12625,7 @@ This switch disables warnings for exception usage when pragma Restrictions
@item @code{-gnatwy}
-`Activate warnings for Ada compatibility issues.'
+@emph{Activate warnings for Ada compatibility issues.}
For the most part, newer versions of Ada are upwards compatible
with older versions. For example, Ada 2005 programs will almost
@@ -12645,7 +12647,7 @@ was called Ada 0Y, hence the choice of character.
@item @code{-gnatwY}
-`Disable warnings for Ada compatibility issues.'
+@emph{Disable warnings for Ada compatibility issues.}
This switch suppresses the warnings intended to help in identifying
incompatibilities between Ada language versions.
@@ -12660,7 +12662,7 @@ incompatibilities between Ada language versions.
@item @code{-gnatw.y}
-`Activate information messages for why package spec needs body.'
+@emph{Activate information messages for why package spec needs body.}
There are a number of cases in which a package spec needs a body.
For example, the use of pragma Elaborate_Body, or the declaration
@@ -12680,7 +12682,7 @@ body. The default is that such information messages are not output.
@item @code{-gnatw.Y}
-`Disable information messages for why package spec needs body.'
+@emph{Disable information messages for why package spec needs body.}
This switch suppresses the output of information messages showing why
a package specification needs a body.
@@ -12695,7 +12697,7 @@ a package specification needs a body.
@item @code{-gnatwz}
-`Activate warnings on unchecked conversions.'
+@emph{Activate warnings on unchecked conversions.}
This switch activates warnings for unchecked conversions
where the types are known at compile time to have different
@@ -12710,7 +12712,7 @@ generated for subprogram pointers with different conventions.
@item @code{-gnatwZ}
-`Suppress warnings on unchecked conversions.'
+@emph{Suppress warnings on unchecked conversions.}
This switch suppresses warnings for unchecked conversions
where the types are known at compile time to have different
@@ -12726,7 +12728,7 @@ sizes or conventions.
@item @code{-gnatw.z}
-`Activate warnings for size not a multiple of alignment.'
+@emph{Activate warnings for size not a multiple of alignment.}
This switch activates warnings for cases of array and record types
with specified @code{Size} and @code{Alignment} attributes where the
@@ -12744,7 +12746,7 @@ is that such warnings are generated.
@item @code{-gnatw.Z}
-`Suppress warnings for size not a multiple of alignment.'
+@emph{Suppress warnings for size not a multiple of alignment.}
This switch suppresses warnings for cases of array and record types
with specified @code{Size} and @code{Alignment} attributes where the
@@ -12784,7 +12786,7 @@ used in conjunction with an optimization level greater than zero.
@table @asis
-@item @code{-Wstack-usage=`len'}
+@item @code{-Wstack-usage=@emph{len}}
Warn if the stack usage of a subprogram might be larger than @code{len} bytes.
See @ref{e8,,Static Stack Usage Analysis} for details.
@@ -13125,7 +13127,7 @@ combination with optimization, since this can confuse the optimizer.
If performance is a consideration, leading to the need to optimize,
then the validity checking options should not be used.
-The other @code{-gnatV`x'} switches below allow finer-grained
+The other @code{-gnatV@emph{x}} switches below allow finer-grained
control; you can enable whichever validity checks you desire. However,
for most debugging purposes, @code{-gnatVa} is sufficient, and the
default @code{-gnatVd} (i.e. standard Ada behavior) is usually
@@ -13138,7 +13140,7 @@ the compiler can generate more efficient code, since the range
of values is better known at compile time. However, an uninitialized
variable can cause wild jumps and memory corruption in this mode.
-The @code{-gnatV`x'} switch allows control over the validity
+The @code{-gnatV@emph{x}} switch allows control over the validity
checking mode as described below.
The @code{x} argument is a string of letters that
indicate validity checks that are performed or not performed in addition
@@ -13151,7 +13153,7 @@ to the default checks required by Ada as described above.
@item @code{-gnatVa}
-`All validity checks.'
+@emph{All validity checks.}
All validity checks are turned on.
That is, @code{-gnatVa} is
@@ -13165,7 +13167,7 @@ equivalent to @code{gnatVcdefimoprst}.
@item @code{-gnatVc}
-`Validity checks for copies.'
+@emph{Validity checks for copies.}
The right-hand side of assignments, and the (explicit) initializing values
of object declarations are validity checked.
@@ -13178,7 +13180,7 @@ of object declarations are validity checked.
@item @code{-gnatVd}
-`Default (RM) validity checks.'
+@emph{Default (RM) validity checks.}
Some validity checks are required by Ada (see RM 13.9.1 (9-11)); these
(and only these) validity checks are enabled by default.
@@ -13204,7 +13206,7 @@ overwriting may occur.
@item @code{-gnatVe}
-`Validity checks for scalar components.'
+@emph{Validity checks for scalar components.}
In the absence of this switch, assignments to scalar components of
enclosing record or array objects are not validity checked, even if
@@ -13220,7 +13222,7 @@ This switch has no effect if the @code{-gnatVc} switch is not specified.
@item @code{-gnatVf}
-`Validity checks for floating-point values.'
+@emph{Validity checks for floating-point values.}
Specifying this switch enables validity checking for floating-point
values in the same contexts where validity checking is enabled for
@@ -13247,7 +13249,7 @@ options. For example, @code{-gnatVif} or @code{-gnatVfi}
@item @code{-gnatVi}
-`Validity checks for `@w{`}in`@w{`} mode parameters.'
+@emph{Validity checks for `@w{`}in`@w{`} mode parameters.}
Arguments for parameters of mode @code{in} are validity checked in function
and procedure calls at the point of call.
@@ -13260,7 +13262,7 @@ and procedure calls at the point of call.
@item @code{-gnatVm}
-`Validity checks for `@w{`}in out`@w{`} mode parameters.'
+@emph{Validity checks for `@w{`}in out`@w{`} mode parameters.}
Arguments for parameters of mode @code{in out} are validity checked in
procedure calls at the point of call. The @code{'m'} here stands for
@@ -13278,7 +13280,7 @@ will be subject to validity checking.
@item @code{-gnatVn}
-`No validity checks.'
+@emph{No validity checks.}
This switch turns off all validity checking, including the default checking
for case statements and left hand side subscripts. Note that the use of
@@ -13294,7 +13296,7 @@ is used, it cancels any other @code{-gnatV} previously issued.
@item @code{-gnatVo}
-`Validity checks for operator and attribute operands.'
+@emph{Validity checks for operator and attribute operands.}
Scalar arguments for predefined operators and for attributes are
validity checked.
@@ -13313,7 +13315,7 @@ also made on explicit ranges using @code{..} (e.g., slices, loops etc).
@item @code{-gnatVp}
-`Validity checks for parameters.'
+@emph{Validity checks for parameters.}
This controls the treatment of formal parameters within a subprogram (as
opposed to @code{-gnatVi} and @code{-gnatVm}, which control validity
@@ -13333,7 +13335,7 @@ the two call-related options is specified, then this switch has no effect.
@item @code{-gnatVr}
-`Validity checks for function returns.'
+@emph{Validity checks for function returns.}
The expression in simple @code{return} statements in functions is validity
checked.
@@ -13346,7 +13348,7 @@ checked.
@item @code{-gnatVs}
-`Validity checks for subscripts.'
+@emph{Validity checks for subscripts.}
All subscript expressions are checked for validity, whatever context
they occur in (in default mode some subscripts are not validity checked;
@@ -13361,7 +13363,7 @@ a read of a component of an array).
@item @code{-gnatVt}
-`Validity checks for tests.'
+@emph{Validity checks for tests.}
Expressions used as conditions in @code{if}, @code{while} or @code{exit}
statements are checked, as well as guard expressions in entry calls.
@@ -13426,7 +13428,7 @@ checks to be performed. The following checks are defined:
@item @code{-gnaty0}
-`Specify indentation level.'
+@emph{Specify indentation level.}
If a digit from 1-9 appears
in the string after @code{-gnaty}
@@ -13465,7 +13467,7 @@ non-blank line.
@item @code{-gnatya}
-`Check attribute casing.'
+@emph{Check attribute casing.}
Attribute names, including the case of keywords such as @code{digits}
used as attributes names, must be written in mixed case, that is, the
@@ -13480,7 +13482,7 @@ All other letters must be lowercase.
@item @code{-gnatyA}
-`Use of array index numbers in array attributes.'
+@emph{Use of array index numbers in array attributes.}
When using the array attributes First, Last, Range,
or Length, the index number must be omitted for one-dimensional arrays
@@ -13494,7 +13496,7 @@ and is required for multi-dimensional arrays.
@item @code{-gnatyb}
-`Blanks not allowed at statement end.'
+@emph{Blanks not allowed at statement end.}
Trailing blanks are not allowed at the end of statements. The purpose of this
rule, together with h (no horizontal tabs), is to enforce a canonical format
@@ -13508,7 +13510,7 @@ for the use of blanks to separate source tokens.
@item @code{-gnatyB}
-`Check Boolean operators.'
+@emph{Check Boolean operators.}
The use of AND/OR operators is not permitted except in the cases of modular
operands, array operands, and simple stand-alone boolean variables or
@@ -13523,7 +13525,7 @@ required.
@item @code{-gnatyc}
-`Check comments, double space.'
+@emph{Check comments, double space.}
Comments must meet the following set of rules:
@@ -13585,7 +13587,7 @@ example:
@item @code{-gnatyC}
-`Check comments, single space.'
+@emph{Check comments, single space.}
This is identical to @code{c} except that only one space
is required following the @code{--} of a comment instead of two.
@@ -13598,7 +13600,7 @@ is required following the @code{--} of a comment instead of two.
@item @code{-gnatyd}
-`Check no DOS line terminators present.'
+@emph{Check no DOS line terminators present.}
All lines must be terminated by a single ASCII.LF
character (in particular the DOS line terminator sequence CR/LF is not
@@ -13612,7 +13614,7 @@ allowed).
@item @code{-gnatyD}
-`Check declared identifiers in mixed case.'
+@emph{Check declared identifiers in mixed case.}
Declared identifiers must be in mixed case, as in
This_Is_An_Identifier. Use -gnatyr in addition to ensure
@@ -13626,7 +13628,7 @@ that references match declarations.
@item @code{-gnatye}
-`Check end/exit labels.'
+@emph{Check end/exit labels.}
Optional labels on @code{end} statements ending subprograms and on
@code{exit} statements exiting named loops, are required to be present.
@@ -13639,7 +13641,7 @@ Optional labels on @code{end} statements ending subprograms and on
@item @code{-gnatyf}
-`No form feeds or vertical tabs.'
+@emph{No form feeds or vertical tabs.}
Neither form feeds nor vertical tab characters are permitted
in the source text.
@@ -13652,7 +13654,7 @@ in the source text.
@item @code{-gnatyg}
-`GNAT style mode.'
+@emph{GNAT style mode.}
The set of style check switches is set to match that used by the GNAT sources.
This may be useful when developing code that is eventually intended to be
@@ -13668,7 +13670,7 @@ set in the future without advance notice.
@item @code{-gnatyh}
-`No horizontal tabs.'
+@emph{No horizontal tabs.}
Horizontal tab characters are not permitted in the source text.
Together with the b (no blanks at end of line) check, this
@@ -13683,7 +13685,7 @@ source tokens.
@item @code{-gnatyi}
-`Check if-then layout.'
+@emph{Check if-then layout.}
The keyword @code{then} must appear either on the same
line as corresponding @code{if}, or on a line on its own, lined
@@ -13697,7 +13699,7 @@ up under the @code{if}.
@item @code{-gnatyI}
-`check mode IN keywords.'
+@emph{check mode IN keywords.}
Mode @code{in} (the default mode) is not
allowed to be given explicitly. @code{in out} is fine,
@@ -13711,7 +13713,7 @@ but not @code{in} on its own.
@item @code{-gnatyk}
-`Check keyword casing.'
+@emph{Check keyword casing.}
All keywords must be in lower case (with the exception of keywords
such as @code{digits} used as attribute names to which this check
@@ -13726,7 +13728,7 @@ this rule even if multiple casing issues exist on a same line.
@item @code{-gnatyl}
-`Check layout.'
+@emph{Check layout.}
Layout of statement and declaration constructs must follow the
recommendations in the Ada Reference Manual, as indicated by the
@@ -13802,11 +13804,11 @@ Clear :
@item @code{-gnatyL}
-`Set maximum nesting level.'
+@emph{Set maximum nesting level.}
The maximum level of nesting of constructs (including subprograms, loops,
blocks, packages, and conditionals) may not exceed the given value
-`nnn'. A value of zero disconnects this style check.
+@emph{nnn}. A value of zero disconnects this style check.
@end table
@geindex -gnatym (gcc)
@@ -13816,7 +13818,7 @@ blocks, packages, and conditionals) may not exceed the given value
@item @code{-gnatym}
-`Check maximum line length.'
+@emph{Check maximum line length.}
The length of source lines must not exceed 79 characters, including
any trailing blanks. The value of 79 allows convenient display on an
@@ -13834,10 +13836,10 @@ a single character (however many bytes are needed in the encoding).
@item @code{-gnatyM}
-`Set maximum line length.'
+@emph{Set maximum line length.}
The length of lines must not exceed the
-given value `nnn'. The maximum value that can be specified is 32767.
+given value @emph{nnn}. The maximum value that can be specified is 32767.
If neither style option for setting the line length is used, then the
default is 255. This also controls the maximum length of lexical elements,
where the only restriction is that they must fit on a single line.
@@ -13850,7 +13852,7 @@ where the only restriction is that they must fit on a single line.
@item @code{-gnatyn}
-`Check casing of entities in Standard.'
+@emph{Check casing of entities in Standard.}
Any identifier from Standard must be cased
to match the presentation in the Ada Reference Manual (for example,
@@ -13864,7 +13866,7 @@ to match the presentation in the Ada Reference Manual (for example,
@item @code{-gnatyN}
-`Turn off all style checks.'
+@emph{Turn off all style checks.}
All style check options are turned off.
@end table
@@ -13876,7 +13878,7 @@ All style check options are turned off.
@item @code{-gnatyo}
-`Check order of subprogram bodies.'
+@emph{Check order of subprogram bodies.}
All subprogram bodies in a given scope
(e.g., a package body) must be in alphabetical order. The ordering
@@ -13893,7 +13895,7 @@ before Junk10).
@item @code{-gnatyO}
-`Check that overriding subprograms are explicitly marked as such.'
+@emph{Check that overriding subprograms are explicitly marked as such.}
This applies to all subprograms of a derived type that override a primitive
operation of the type, for both tagged and untagged types. In particular,
@@ -13910,7 +13912,7 @@ as an equality operator).
@item @code{-gnatyp}
-`Check pragma casing.'
+@emph{Check pragma casing.}
Pragma names must be written in mixed case, that is, the
initial letter and any letter following an underscore must be uppercase.
@@ -13925,7 +13927,7 @@ allowed as an alternative for Spark_Mode.
@item @code{-gnatyr}
-`Check references.'
+@emph{Check references.}
All identifier references must be cased in the same way as the
corresponding declaration. No specific casing style is imposed on
@@ -13940,7 +13942,7 @@ with declarations.
@item @code{-gnatys}
-`Check separate specs.'
+@emph{Check separate specs.}
Separate declarations (‘specs’) are required for subprograms (a
body is not allowed to serve as its own declaration). The only
@@ -13956,7 +13958,7 @@ the most frequent form of main program procedures.
@item @code{-gnatyS}
-`Check no statements after then/else.'
+@emph{Check no statements after then/else.}
No statements are allowed
on the same line as a @code{then} or @code{else} keyword following the
@@ -13971,7 +13973,7 @@ affected, and a special exception allows a pragma to appear after @code{else}.
@item @code{-gnatyt}
-`Check token spacing.'
+@emph{Check token spacing.}
The following token spacing rules are enforced:
@@ -14036,7 +14038,7 @@ a @code{not} token and a following @code{in} token.
@item @code{-gnatyu}
-`Check unnecessary blank lines.'
+@emph{Check unnecessary blank lines.}
Unnecessary blank lines are not allowed. A blank line is considered
unnecessary if it appears at the end of the file, or if more than
@@ -14050,7 +14052,7 @@ one blank line occurs in sequence.
@item @code{-gnatyx}
-`Check extra parentheses.'
+@emph{Check extra parentheses.}
Unnecessary extra levels of parentheses (C-style) are not allowed
around conditions (or selection expressions) in @code{if}, @code{while},
@@ -14064,7 +14066,7 @@ around conditions (or selection expressions) in @code{if}, @code{while},
@item @code{-gnatyy}
-`Set all standard style check options.'
+@emph{Set all standard style check options.}
This is equivalent to @code{gnaty3aAbcefhiklmnprst}, that is all checking
options enabled with the exception of @code{-gnatyB}, @code{-gnatyd},
@@ -14079,7 +14081,7 @@ options enabled with the exception of @code{-gnatyB}, @code{-gnatyd},
@item @code{-gnatyz}
-`Check extra parentheses (operator precedence).'
+@emph{Check extra parentheses (operator precedence).}
Extra levels of parentheses that are not required by operator precedence
rules are flagged. See also @code{-gnatyx}.
@@ -14092,15 +14094,15 @@ rules are flagged. See also @code{-gnatyx}.
@item @code{-gnaty-}
-`Remove style check options.'
+@emph{Remove style check options.}
This causes any subsequent options in the string to act as canceling the
corresponding style check option. To cancel maximum nesting level control,
use the @code{L} parameter without any integer value after that, because any
-digit following `-' in the parameter string of the @code{-gnaty}
+digit following @emph{-} in the parameter string of the @code{-gnaty}
option will be treated as canceling the indentation check. The same is true
for the @code{M} parameter. @code{y} and @code{N} parameters are not
-allowed after `-'.
+allowed after @emph{-}.
@end table
@geindex -gnaty+ (gcc)
@@ -14110,7 +14112,7 @@ allowed after `-'.
@item @code{-gnaty+}
-`Enable style check options.'
+@emph{Enable style check options.}
This causes any subsequent options in the string to enable the corresponding
style check option. That is, it cancels the effect of a previous -,
@@ -14267,20 +14269,20 @@ controls the mode, using the codes
@table @asis
-@item `1 = STRICT'
+@item @emph{1 = STRICT}
In STRICT mode, intermediate operations are always done using the
base type, and overflow checking ensures that the result is within
the base type range.
-@item `2 = MINIMIZED'
+@item @emph{2 = MINIMIZED}
In MINIMIZED mode, overflows in intermediate operations are avoided
where possible by using a larger integer type for the computation
(typically @code{Long_Long_Integer}). Overflow checking ensures that
the result fits in this larger integer type.
-@item `3 = ELIMINATED'
+@item @emph{3 = ELIMINATED}
In ELIMINATED mode, overflows in intermediate operations are avoided
by using multi-precision arithmetic. In this case, overflow checking
@@ -14407,7 +14409,7 @@ $
Otherwise, the output is simply the error messages, if any. No object file or
ALI file is generated by a syntax-only compilation. Also, no units other
than the one specified are accessed. For example, if a unit @code{X}
-`with's a unit @code{Y}, compiling unit @code{X} in syntax
+@emph{with}s a unit @code{Y}, compiling unit @code{X} in syntax
check only mode does not access the source file containing unit
@code{Y}.
@@ -14516,7 +14518,7 @@ with optional bodies), it is not necessary to specify the
exceptions, Ada 95 and Ada 2005 are upwardly compatible with Ada 83. Thus
a correct Ada 83 program is usually also a correct program
in these later versions of the language standard. For further information
-please refer to the `Compatibility and Porting Guide' chapter in the
+please refer to the @emph{Compatibility and Porting Guide} chapter in the
@cite{GNAT Reference Manual}.
@end table
@@ -14643,7 +14645,7 @@ extensions enabled by this switch, see the GNAT reference manual
@table @asis
-@item @code{-gnati`c'}
+@item @code{-gnati@emph{c}}
Normally GNAT recognizes the Latin-1 character set in source program
identifiers, as described in the Ada Reference Manual.
@@ -14655,7 +14657,7 @@ single character indicating the character set, as follows:
@multitable {xxxxxxxxxxxx} {xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx}
@item
-`1'
+@emph{1}
@tab
@@ -14663,7 +14665,7 @@ ISO 8859-1 (Latin-1) identifiers
@item
-`2'
+@emph{2}
@tab
@@ -14671,7 +14673,7 @@ ISO 8859-2 (Latin-2) letters allowed in identifiers
@item
-`3'
+@emph{3}
@tab
@@ -14679,7 +14681,7 @@ ISO 8859-3 (Latin-3) letters allowed in identifiers
@item
-`4'
+@emph{4}
@tab
@@ -14687,7 +14689,7 @@ ISO 8859-4 (Latin-4) letters allowed in identifiers
@item
-`5'
+@emph{5}
@tab
@@ -14695,7 +14697,7 @@ ISO 8859-5 (Cyrillic) letters allowed in identifiers
@item
-`9'
+@emph{9}
@tab
@@ -14703,7 +14705,7 @@ ISO 8859-15 (Latin-9) letters allowed in identifiers
@item
-`p'
+@emph{p}
@tab
@@ -14711,7 +14713,7 @@ IBM PC letters (code page 437) allowed in identifiers
@item
-`8'
+@emph{8}
@tab
@@ -14719,7 +14721,7 @@ IBM PC letters (code page 850) allowed in identifiers
@item
-`f'
+@emph{f}
@tab
@@ -14727,7 +14729,7 @@ Full upper-half codes allowed in identifiers
@item
-`n'
+@emph{n}
@tab
@@ -14735,7 +14737,7 @@ No upper-half codes allowed in identifiers
@item
-`w'
+@emph{w}
@tab
@@ -14754,7 +14756,7 @@ implementation of these character sets.
@table @asis
-@item @code{-gnatW`e'}
+@item @code{-gnatW@emph{e}}
Specify the method of encoding for wide characters.
@code{e} is one of the following:
@@ -14763,7 +14765,7 @@ Specify the method of encoding for wide characters.
@multitable {xxxxxxxxxxxx} {xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx}
@item
-`h'
+@emph{h}
@tab
@@ -14771,7 +14773,7 @@ Hex encoding (brackets coding also recognized)
@item
-`u'
+@emph{u}
@tab
@@ -14779,7 +14781,7 @@ Upper half encoding (brackets encoding also recognized)
@item
-`s'
+@emph{s}
@tab
@@ -14787,7 +14789,7 @@ Shift/JIS encoding (brackets encoding also recognized)
@item
-`e'
+@emph{e}
@tab
@@ -14795,7 +14797,7 @@ EUC encoding (brackets encoding also recognized)
@item
-`8'
+@emph{8}
@tab
@@ -14803,7 +14805,7 @@ UTF-8 encoding (brackets encoding also recognized)
@item
-`b'
+@emph{b}
@tab
@@ -14870,7 +14872,7 @@ This is a common mode for many programs with foreign language comments.
@table @asis
-@item @code{-gnatk`n'}
+@item @code{-gnatk@emph{n}}
Activates file name ‘krunching’. @code{n}, a decimal integer in the range
1-999, indicates the maximum allowable length of a file name (not
@@ -14969,7 +14971,7 @@ react to a compilation failure. Those exit status are:
@multitable {xxxxxxxxxxxx} {xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx}
@item
-`5'
+@emph{5}
@tab
@@ -14977,7 +14979,7 @@ There was an error in at least one source file.
@item
-`3'
+@emph{3}
@tab
@@ -14985,7 +14987,7 @@ At least one source file did not generate an object file.
@item
-`2'
+@emph{2}
@tab
@@ -14993,7 +14995,7 @@ The compiler died unexpectedly (internal error for example).
@item
-`0'
+@emph{0}
@tab
@@ -15018,7 +15020,7 @@ An object file has been generated for every source file.
@table @asis
-@item @code{-gnatd`x'}
+@item @code{-gnatd@emph{x}}
Activate internal debugging switches. @code{x} is a letter or digit, or
string of letters or digits, which specifies the type of debugging
@@ -15033,7 +15035,7 @@ file @code{debug.adb}.
@table @asis
-@item @code{-gnatG[=`nn']}
+@item @code{-gnatG[=@emph{nn}]}
This switch causes the compiler to generate auxiliary output containing
a pseudo-source listing of the generated expanded code. Like most Ada
@@ -15069,47 +15071,47 @@ in the expanded source (as comment lines with the original line number).
@table @asis
-@item @code{new @var{xxx} [storage_pool = @var{yyy}]}
+@item @code{new @emph{xxx} [storage_pool = @emph{yyy}]}
Shows the storage pool being used for an allocator.
-@item @code{at end @var{procedure-name};}
+@item @code{at end @emph{procedure-name};}
Shows the finalization (cleanup) procedure for a scope.
-@item @code{(if @var{expr} then @var{expr} else @var{expr})}
+@item @code{(if @emph{expr} then @emph{expr} else @emph{expr})}
Conditional expression equivalent to the @code{x?y:z} construction in C.
-@item @code{@var{target}^(@var{source})}
+@item @code{@emph{target}^(@emph{source})}
A conversion with floating-point truncation instead of rounding.
-@item @code{@var{target}?(@var{source})}
+@item @code{@emph{target}?(@emph{source})}
A conversion that bypasses normal Ada semantic checking. In particular
enumeration types and fixed-point types are treated simply as integers.
-@item @code{@var{target}?^(@var{source})}
+@item @code{@emph{target}?^(@emph{source})}
Combines the above two cases.
@end table
-@code{@var{x} #/ @var{y}}
+@code{@emph{x} #/ @emph{y}}
-@code{@var{x} #mod @var{y}}
+@code{@emph{x} #mod @emph{y}}
-@code{@var{x} # @var{y}}
+@code{@emph{x} # @emph{y}}
@table @asis
-@item @code{@var{x} #rem @var{y}}
+@item @code{@emph{x} #rem @emph{y}}
A division or multiplication of fixed-point values which are treated as
integers without any kind of scaling.
-@item @code{free @var{expr} [storage_pool = @var{xxx}]}
+@item @code{free @emph{expr} [storage_pool = @emph{xxx}]}
Shows the storage pool associated with a @code{free} statement.
@@ -15118,30 +15120,30 @@ Shows the storage pool associated with a @code{free} statement.
Used to list an equivalent declaration for an internally generated
type that is referenced elsewhere in the listing.
-@item @code{freeze @var{type-name} [@var{actions}]}
+@item @code{freeze @emph{type-name} [@emph{actions}]}
Shows the point at which @code{type-name} is frozen, with possible
associated actions to be performed at the freeze point.
-@item @code{reference @var{itype}}
+@item @code{reference @emph{itype}}
Reference (and hence definition) to internal type @code{itype}.
-@item @code{@var{function-name}! (@var{arg}, @var{arg}, @var{arg})}
+@item @code{@emph{function-name}! (@emph{arg}, @emph{arg}, @emph{arg})}
Intrinsic function call.
-@item @code{@var{label-name} : label}
+@item @code{@emph{label-name} : label}
Declaration of label @code{labelname}.
-@item @code{#$ @var{subprogram-name}}
+@item @code{#$ @emph{subprogram-name}}
An implicit call to a run-time support routine
(to meet the requirement of H.3.1(9) in a
convenient manner).
-@item @code{@var{expr} && @var{expr} && @var{expr} ... && @var{expr}}
+@item @code{@emph{expr} && @emph{expr} && @emph{expr} ... && @emph{expr}}
A multiple concatenation (same effect as @code{expr} & @code{expr} &
@code{expr}, but handled more efficiently).
@@ -15150,15 +15152,15 @@ A multiple concatenation (same effect as @code{expr} & @code{expr} &
Raise the @code{Constraint_Error} exception.
-@item @code{@var{expression}'reference}
+@item @code{@emph{expression}'reference}
A pointer to the result of evaluating @{expression@}.
-@item @code{@var{target-type}!(@var{source-expression})}
+@item @code{@emph{target-type}!(@emph{source-expression})}
An unchecked conversion of @code{source-expression} to @code{target-type}.
-@item @code{[@var{numerator}/@var{denominator}]}
+@item @code{[@emph{numerator}/@emph{denominator}]}
Used to represent internal real literals (that) have no exact
representation in base 2-16 (for example, the result of compile time
@@ -15434,7 +15436,7 @@ through the compilation and binding steps.
@table @asis
-@item @code{-gnatem=`path'}
+@item @code{-gnatem=@emph{path}}
A mapping file is a way to communicate to the compiler two mappings:
from unit names to file names (without any directory information) and from
@@ -15517,7 +15519,7 @@ Linker switches can be specified after @code{-largs} builder switch.
@table @asis
-@item @code{-fuse-ld=`name'}
+@item @code{-fuse-ld=@emph{name}}
Linker to be used. The default is @code{bfd} for @code{ld.bfd}; @code{gold}
(for @code{ld.gold}) and @code{mold} (for @code{ld.mold}) are more
@@ -15728,7 +15730,7 @@ Specify directory to be searched for source file.
@table @asis
-@item @code{-A[=`filename']}
+@item @code{-A[=@emph{filename}]}
Output ALI list (to standard output or to the named file).
@end table
@@ -15758,7 +15760,7 @@ Check only, no generation of binder output file.
@table @asis
-@item @code{-d`nn'[k|m]}
+@item @code{-d@emph{nn}[k|m]}
This switch can be used to change the default task stack size value
to a specified size @code{nn}, which is expressed in bytes by default, or
@@ -15779,7 +15781,7 @@ When they do not already have such a pragma.
@table @asis
-@item @code{-D`nn'[k|m]}
+@item @code{-D@emph{nn}[k|m]}
Set the default secondary stack size to @code{nn}. The suffix indicates whether
the size is in bytes (no suffix), kilobytes (@code{k} suffix) or megabytes
@@ -15855,7 +15857,7 @@ Currently the same as @code{-Ea}.
@table @asis
-@item @code{-f`elab-order'}
+@item @code{-f@emph{elab-order}}
Force elaboration order. For further details see @ref{113,,Elaboration Control}
and @ref{f,,Elaboration Order Handling in GNAT}.
@@ -15959,25 +15961,25 @@ Output chosen elaboration order.
@geindex -L (gnatbind)
-@item @code{-L`xxx'}
+@item @code{-L@emph{xxx}}
Bind the units for library building. In this case the @code{adainit} and
@code{adafinal} procedures (@ref{7e,,Binding with Non-Ada Main Programs})
-are renamed to @code{@var{xxx}init} and
-@code{@var{xxx}final}.
+are renamed to @code{@emph{xxx}init} and
+@code{@emph{xxx}final}.
Implies -n.
(@ref{2a,,GNAT and Libraries}, for more details.)
@geindex -M (gnatbind)
-@item @code{-M`xyz'}
+@item @code{-M@emph{xyz}}
Rename generated main program from main to xyz. This option is
supported on cross environments only.
@geindex -m (gnatbind)
-@item @code{-m`n'}
+@item @code{-m@emph{n}}
Limit number of detected errors or warnings to @code{n}, where @code{n} is
in the range 1..999999. The default value if no switch is
@@ -15994,7 +15996,7 @@ sign is optional.
Generate a binder file suitable for space-constrained applications. When
active, binder-generated objects not required for program operation are no
-longer generated. `Warning:' this option comes with the following
+longer generated. @strong{Warning:} this option comes with the following
limitations:
@@ -16030,14 +16032,14 @@ Do not look for library files in the system default directory.
@geindex --RTS (gnatbind)
-@item @code{--RTS=`rts-path'}
+@item @code{--RTS=@emph{rts-path}}
Specifies the default location of the run-time library. Same meaning as the
equivalent @code{gnatmake} flag (@ref{d0,,Switches for gnatmake}).
@geindex -o (gnatbind)
-@item @code{-o `file'}
+@item @code{-o @emph{file}}
Name the output file @code{file} (default is @code{b~`xxx}.adb`).
Note that if this option is used, then linking must be done manually,
@@ -16045,7 +16047,7 @@ gnatlink cannot be used.
@geindex -O (gnatbind)
-@item @code{-O[=`filename']}
+@item @code{-O[=@emph{filename}]}
Output object list (to standard output or to the named file).
@@ -16067,7 +16069,7 @@ Generate binder file suitable for CodePeer.
@table @asis
-@item @code{-Q`nnn'}
+@item @code{-Q@emph{nnn}}
Generate @code{nnn} additional default-sized secondary stacks.
@@ -16079,8 +16081,8 @@ by rebinding the application.
While the binder sizes this pool to match the number of such tasks defined in
the application, the pool size may need to be increased with the @code{-Q}
switch to accommodate foreign threads registered with the Light run-time. For
-more information, please see the `The Primary and Secondary Stack' chapter in
-the `GNAT User’s Guide Supplement for Cross Platforms'.
+more information, please see the @emph{The Primary and Secondary Stack} chapter in
+the @emph{GNAT User’s Guide Supplement for Cross Platforms}.
@geindex -R (gnatbind)
@@ -16103,7 +16105,7 @@ Require all source files to be present.
@geindex -S (gnatbind)
-@item @code{-S`xxx'}
+@item @code{-S@emph{xxx}}
Specifies the value to be used when detecting uninitialized scalar
objects with pragma Initialize_Scalars.
@@ -16157,8 +16159,8 @@ then a 32-bit scalar value will be set to the bit pattern @code{16#BFBFBFBF#}.
In addition, you can specify @code{-Sev} to indicate that the value is
to be set at run time. In this case, the program will look for an environment
-variable of the form @code{GNAT_INIT_SCALARS=@var{yy}}, where @code{yy} is one
-of @code{in/lo/hi/@var{xx}} with the same meanings as above.
+variable of the form @code{GNAT_INIT_SCALARS=@emph{yy}}, where @code{yy} is one
+of @code{in/lo/hi/@emph{xx}} with the same meanings as above.
If no environment variable is found, or if it does not have a valid value,
then the default is @code{in} (invalid values).
@end table
@@ -16186,7 +16188,7 @@ Tolerate time stamp and other consistency errors.
@geindex -T (gnatbind)
-@item @code{-T`n'}
+@item @code{-T@emph{n}}
Set the time slice value to @code{n} milliseconds. If the system supports
the specification of a specific time slice value, then the indicated value
@@ -16202,7 +16204,7 @@ scheduling policy to @code{FIFO_Within_Priorities}.
@geindex -u (gnatbind)
-@item @code{-u`n'}
+@item @code{-u@emph{n}}
Enable dynamic stack usage, with @code{n} results stored and displayed
at program termination. A result is generated when a task
@@ -16219,7 +16221,7 @@ Verbose mode. Write error messages, header, summary output to
@geindex -V (gnatbind)
-@item @code{-V`key'=`value'}
+@item @code{-V@emph{key}=@emph{value}}
Store the given association of @code{key} to @code{value} in the bind environment.
Values stored this way can be retrieved at run time using
@@ -16227,13 +16229,13 @@ Values stored this way can be retrieved at run time using
@geindex -w (gnatbind)
-@item @code{-w`x'}
+@item @code{-w@emph{x}}
Warning mode; @code{x} = s/e for suppress/treat as error.
@geindex -Wx (gnatbind)
-@item @code{-Wx`e'}
+@item @code{-Wx@emph{e}}
Override default wide character encoding for standard Text_IO files.
@@ -16256,7 +16258,7 @@ at streaming 128-bit integer types with it.
@geindex -Xnnn (gnatbind)
-@item @code{-X`nnn'}
+@item @code{-X@emph{nnn}}
Set default exit status value, normally 0 for POSIX compliance.
@@ -16315,7 +16317,7 @@ file is an error.
@geindex -Wx (gnatbind)
-@item @code{-Wx`e'}
+@item @code{-Wx@emph{e}}
Override default wide character encoding for standard Text_IO files.
Normally the default wide character encoding method used for standard
@@ -16374,14 +16376,14 @@ specified. This is relevant only when used with the
@geindex -m (gnatbind)
-@item @code{-m`n'}
+@item @code{-m@emph{n}}
Limits the number of error messages to @code{n}, a decimal integer in the
range 1-999. The binder terminates immediately if this limit is reached.
@geindex -M (gnatbind)
-@item @code{-M`xxx'}
+@item @code{-M@emph{xxx}}
Renames the generated main program from @code{main} to @code{xxx}.
This is useful in the case of some cross-building environments, where
@@ -16464,7 +16466,7 @@ order. For further details see @ref{f,,Elaboration Order Handling in GNAT}.
@table @asis
-@item @code{-f`elab-order'}
+@item @code{-f@emph{elab-order}}
Force elaboration order.
@@ -16599,7 +16601,7 @@ directory names for the run-time units depend on the system configuration.
@geindex -o (gnatbind)
-@item @code{-o `file'}
+@item @code{-o @emph{file}}
Set name of output file to @code{file} instead of the normal
@code{b~`mainprog}.adb` default. Note that @code{file} denote the Ada
@@ -16719,7 +16721,7 @@ is given, more than one ALI file may appear on
the command line for @code{gnatbind}. The normal @code{closure}
calculation is performed for each of the specified units. Calculating
the closure means finding out the set of units involved by tracing
-`with' references. The reason it is necessary to be able to
+@emph{with} references. The reason it is necessary to be able to
specify more than one ALI file is that a given program may invoke two or
more quite separate groups of Ada units.
@@ -16790,9 +16792,9 @@ char **gnat_argv;
are declared in one of the GNAT library routines. These variables must
be set from the actual @code{argc} and @code{argv} values passed to the
-main program. With no `n' present, @code{gnatbind}
+main program. With no @emph{n} present, @code{gnatbind}
generates the C main program to automatically set these variables.
-If the `n' switch is used, there is no automatic way to
+If the @emph{n} switch is used, there is no automatic way to
set these variables. If they are not set, the procedures in
@code{Ada.Command_Line} will not be available, and any attempt to use
them will raise @code{Constraint_Error}. If command line access is
@@ -16874,9 +16876,9 @@ instead if you want to specify
source paths only, and @code{-aO}
if you want to specify library paths
only. This means that for the binder
-@code{-I`dir'} is equivalent to
-@code{-aI`dir'}
-@code{-aO``dir'}.
+@code{-I@emph{dir}} is equivalent to
+@code{-aI@emph{dir}}
+@code{-aO`@emph{dir}}.
The binder generates the bind file (a C language source file) in the
current working directory.
@@ -17127,7 +17129,7 @@ it compiles the binder file, and that the system linker run in verbose mode.
@table @asis
-@item @code{-o `exec-name'}
+@item @code{-o @emph{exec-name}}
@code{exec-name} specifies an alternate name for the generated
executable program. If this switch is omitted, the executable has the same
@@ -17140,7 +17142,7 @@ an executable called @code{try}.
@table @asis
-@item @code{-B`dir'}
+@item @code{-B@emph{dir}}
Load compiler executables (for example, @code{gnat1}, the Ada compiler)
from @code{dir} instead of the default location. Only use this switch
@@ -17166,7 +17168,7 @@ has the same name as the executable with extension “.map”.
@table @asis
-@item @code{-M=`mapfile'}
+@item @code{-M=@emph{mapfile}}
When linking an executable, create a map file. The name of the map file is
@code{mapfile}.
@@ -17177,7 +17179,7 @@ When linking an executable, create a map file. The name of the map file is
@table @asis
-@item @code{--GCC=`compiler_name'}
+@item @code{--GCC=@emph{compiler_name}}
Program used for compiling the binder file. The default is
@code{gcc}. You need to use quotes around @code{compiler_name} if
@@ -17204,7 +17206,7 @@ into account. Thus,
@table @asis
-@item @code{--LINK=`name'}
+@item @code{--LINK=@emph{name}}
@code{name} is the name of the linker to be invoked. This is especially
useful in mixed language programs since languages such as C++ require
@@ -17612,7 +17614,7 @@ Display copyright and version, then exit disregarding all other options.
If @code{--version} was not used, display usage, then exit disregarding
all other options.
-@item @code{--subdirs=`subdir'}
+@item @code{--subdirs=@emph{subdir}}
Actual object directory of each project file is the subdirectory subdir of the
object directory specified or defaulted in the project file.
@@ -17641,7 +17643,7 @@ files, interface copy files, binder generated files and executable files.
@table @asis
-@item @code{-D `dir'}
+@item @code{-D @emph{dir}}
Indicate that ALI and object files should normally be found in directory @code{dir}.
@end table
@@ -17685,7 +17687,7 @@ that would have been deleted if this switch was not specified.
@table @asis
-@item @code{-P`project'}
+@item @code{-P@emph{project}}
Use project file @code{project}. Only one such switch can be used.
When cleaning a project file, the files produced by the compilation of the
@@ -17734,7 +17736,7 @@ Verbose mode.
@table @asis
-@item @code{-vP`x'}
+@item @code{-vP@emph{x}}
Indicates the verbosity of the parsing of GNAT project files.
@ref{d1,,Switches Related to Project Files}.
@@ -17745,7 +17747,7 @@ Indicates the verbosity of the parsing of GNAT project files.
@table @asis
-@item @code{-X`name'=`value'}
+@item @code{-X@emph{name}=@emph{value}}
Indicates that external variable @code{name} has the value @code{value}.
The Project Manager will use this value for occurrences of
@@ -17758,7 +17760,7 @@ See @ref{d1,,Switches Related to Project Files}.
@table @asis
-@item @code{-aO`dir'}
+@item @code{-aO@emph{dir}}
When searching for ALI and object files, look in directory @code{dir}.
@end table
@@ -17768,9 +17770,9 @@ When searching for ALI and object files, look in directory @code{dir}.
@table @asis
-@item @code{-I`dir'}
+@item @code{-I@emph{dir}}
-Equivalent to @code{-aO`dir'}.
+Equivalent to @code{-aO@emph{dir}}.
@end table
@geindex -I- (gnatclean)
@@ -17859,12 +17861,12 @@ qualifier which can be:
@table @asis
-@item `OK (unchanged)'
+@item @emph{OK (unchanged)}
The version of the source file used for the compilation of the
specified unit corresponds exactly to the actual source file.
-@item `MOK (slightly modified)'
+@item @emph{MOK (slightly modified)}
The version of the source file used for the compilation of the
specified unit differs from the actual source file but not enough to
@@ -17872,16 +17874,16 @@ require recompilation. If you use gnatmake with the option
@code{-m} (minimal recompilation), a file marked
MOK will not be recompiled.
-@item `DIF (modified)'
+@item @emph{DIF (modified)}
No version of the source found on the path corresponds to the source
used to build this object.
-@item `??? (file not found)'
+@item @emph{??? (file not found)}
No source file was found for this unit.
-@item `HID (hidden, unchanged version not first on PATH)'
+@item @emph{HID (hidden, unchanged version not first on PATH)}
The version of the source that corresponds exactly to the source used
for compilation has been found on the path but it is hidden by another
@@ -17982,7 +17984,7 @@ Only output information about compilation units.
@table @asis
-@item @code{-files=`file'}
+@item @code{-files=@emph{file}}
Take as arguments the files listed in text file @code{file}.
Text file @code{file} may contain empty lines that are ignored.
@@ -18001,7 +18003,7 @@ Several such switches may be specified simultaneously.
@table @asis
-@item @code{-aO`dir'}, @code{-aI`dir'}, @code{-I`dir'}, @code{-I-}, @code{-nostdinc}
+@item @code{-aO@emph{dir}}, @code{-aI@emph{dir}}, @code{-I@emph{dir}}, @code{-I-}, @code{-nostdinc}
Source path manipulation. Same meaning as the equivalent @code{gnatmake}
flags (@ref{d0,,Switches for gnatmake}).
@@ -18012,7 +18014,7 @@ flags (@ref{d0,,Switches for gnatmake}).
@table @asis
-@item @code{-aP`dir'}
+@item @code{-aP@emph{dir}}
Add @code{dir} at the beginning of the project search dir.
@end table
@@ -18022,7 +18024,7 @@ Add @code{dir} at the beginning of the project search dir.
@table @asis
-@item @code{--RTS=`rts-path'}
+@item @code{--RTS=@emph{rts-path}}
Specifies the default location of the runtime library. Same meaning as the
equivalent @code{gnatmake} flag (@ref{d0,,Switches for gnatmake}).
@@ -18044,29 +18046,29 @@ characteristics such as:
@itemize *
@item
-`Preelaborable': The unit is preelaborable in the Ada sense.
+@emph{Preelaborable}: The unit is preelaborable in the Ada sense.
@item
-`No_Elab_Code': No elaboration code has been produced by the compiler for this unit.
+@emph{No_Elab_Code}: No elaboration code has been produced by the compiler for this unit.
@item
-`Pure': The unit is pure in the Ada sense.
+@emph{Pure}: The unit is pure in the Ada sense.
@item
-`Elaborate_Body': The unit contains a pragma Elaborate_Body.
+@emph{Elaborate_Body}: The unit contains a pragma Elaborate_Body.
@item
-`Remote_Types': The unit contains a pragma Remote_Types.
+@emph{Remote_Types}: The unit contains a pragma Remote_Types.
@item
-`Shared_Passive': The unit contains a pragma Shared_Passive.
+@emph{Shared_Passive}: The unit contains a pragma Shared_Passive.
@item
-`Predefined': This unit is part of the predefined environment and cannot be modified
+@emph{Predefined}: This unit is part of the predefined environment and cannot be modified
by the user.
@item
-`Remote_Call_Interface': The unit contains a pragma Remote_Call_Interface.
+@emph{Remote_Call_Interface}: The unit contains a pragma Remote_Call_Interface.
@end itemize
@end table
@@ -18345,7 +18347,7 @@ describes some of the additional commands that can be given to @code{GDB}.
@code{GDB} contains a large repertoire of commands.
See @cite{Debugging with GDB} for extensive documentation on the use
of these commands, together with examples of their use. Furthermore,
-the command `help' invoked from within GDB activates a simple help
+the command @emph{help} invoked from within GDB activates a simple help
facility which summarizes the available commands and their options.
In this section we summarize a few of the most commonly
used commands to give an idea of what @code{GDB} is about. You should create
@@ -18360,9 +18362,9 @@ following section.
@table @asis
-@item @code{set args @var{arguments}}
+@item @code{set args @emph{arguments}}
-The `arguments' list above is a list of arguments to be passed to
+The @emph{arguments} list above is a list of arguments to be passed to
the program on a subsequent run command, just as though the arguments
had been entered on a normal invocation of the program. The @code{set args}
command is not needed if the program does not require arguments.
@@ -18385,11 +18387,11 @@ restart.
@table @asis
-@item @code{breakpoint @var{location}}
+@item @code{breakpoint @emph{location}}
The breakpoint command sets a breakpoint, that is to say a point at which
execution will halt and @code{GDB} will await further
-commands. `location' is
+commands. @emph{location} is
either a line number within a file, given in the format @code{file:linenumber},
or it is the name of a subprogram. If you request that a breakpoint be set on
a subprogram that is overloaded, a prompt will ask you to specify on which of
@@ -18404,7 +18406,7 @@ printing the line of code before which the program is halted.
@table @asis
-@item @code{catch exception @var{name}}
+@item @code{catch exception @emph{name}}
This command causes the program execution to stop whenever exception
@code{name} is raised. If @code{name} is omitted, then the execution is
@@ -18415,7 +18417,7 @@ suspended when any exception is raised.
@table @asis
-@item @code{print @var{expression}}
+@item @code{print @emph{expression}}
This will print the value of the given expression. Most simple
Ada expression formats are properly handled by @code{GDB}, so the expression
@@ -18504,7 +18506,7 @@ examined to the frame of its callee (the reverse of the previous command),
@table @asis
-@item @code{frame @var{n}}
+@item @code{frame @emph{n}}
Inspect the frame with the given number. The value 0 denotes the frame
of the current breakpoint, that is to say the top of the call stack.
@@ -18644,7 +18646,7 @@ the elements in the desired format.
@node Using the next Command in a Function,Stopping When Ada Exceptions Are Raised,Calling User-Defined Subprograms,Running and Debugging Ada Programs
@anchor{gnat_ugn/gnat_and_program_execution id8}@anchor{15a}@anchor{gnat_ugn/gnat_and_program_execution using-the-next-command-in-a-function}@anchor{15b}
-@subsection Using the `next' Command in a Function
+@subsection Using the @emph{next} Command in a Function
When you use the @code{next} command in a function, the current source
@@ -18692,10 +18694,10 @@ raises any exception.
@table @asis
-@item @code{catch exception @var{name}}
+@item @code{catch exception @emph{name}}
Set a catchpoint that stops execution whenever (any task in the) program
-raises the exception `name'.
+raises the exception @emph{name}.
@end table
@item
@@ -18712,11 +18714,11 @@ raises an exception for which there is no handler.
@table @asis
-@item @code{info exceptions}, @code{info exceptions @var{regexp}}
+@item @code{info exceptions}, @code{info exceptions @emph{regexp}}
The @code{info exceptions} command permits the user to examine all defined
-exceptions within Ada programs. With a regular expression, `regexp', as
-argument, prints out only those exceptions whose name matches `regexp'.
+exceptions within Ada programs. With a regular expression, @emph{regexp}, as
+argument, prints out only those exceptions whose name matches @emph{regexp}.
@end table
@end itemize
@@ -18761,25 +18763,25 @@ to refer to tasks in the following commands.
@itemize *
@item
-@code{break} `linespec' @code{task} `taskid', @code{break} `linespec' @code{task} `taskid' @code{if} …
+@code{break} @emph{linespec} @code{task} @emph{taskid}, @code{break} @emph{linespec} @code{task} @emph{taskid} @code{if} …
@quotation
These commands are like the @code{break ... thread ...}.
-`linespec' specifies source lines.
+@emph{linespec} specifies source lines.
-Use the qualifier @code{task @var{taskid}} with a breakpoint command
+Use the qualifier @code{task @emph{taskid}} with a breakpoint command
to specify that you only want @code{GDB} to stop the program when a
-particular Ada task reaches this breakpoint. `taskid' is one of the
+particular Ada task reaches this breakpoint. @emph{taskid} is one of the
numeric task identifiers assigned by @code{GDB}, shown in the first
column of the @code{info tasks} display.
-If you do not specify @code{task @var{taskid}} when you set a
-breakpoint, the breakpoint applies to `all' tasks of your
+If you do not specify @code{task @emph{taskid}} when you set a
+breakpoint, the breakpoint applies to @emph{all} tasks of your
program.
You can use the @code{task} qualifier on conditional breakpoints as
-well; in this case, place @code{task @var{taskid}} before the
+well; in this case, place @code{task @emph{taskid}} before the
breakpoint condition (before the @code{if}).
@end quotation
@end itemize
@@ -18790,11 +18792,11 @@ breakpoint condition (before the @code{if}).
@itemize *
@item
-@code{task @var{taskno}}
+@code{task @emph{taskno}}
@quotation
-This command allows switching to the task referred by `taskno'. In
+This command allows switching to the task referred by @emph{taskno}. In
particular, this allows browsing of the backtrace of the specified
task. It is advisable to switch back to the original task before
continuing execution otherwise the scheduling of the program may be
@@ -18920,7 +18922,7 @@ It is also possible to use gdbserver to attach to an already running
program, in which case the execution of that program is simply suspended
until the connection between the debugger and gdbserver is established.
-For more information on how to use gdbserver, see the `Using the gdbserver Program'
+For more information on how to use gdbserver, see the @emph{Using the gdbserver Program}
section in @cite{Debugging with GDB}.
GNAT provides support for gdbserver on x86-linux, x86-windows and x86_64-linux.
@@ -19107,7 +19109,7 @@ are replaced with run-time calls.
Traceback is a mechanism to display the sequence of subprogram calls that
leads to a specified execution point in a program. Often (but not always)
the execution point is an instruction at which an exception has been raised.
-This mechanism is also known as `stack unwinding' because it obtains
+This mechanism is also known as @emph{stack unwinding} because it obtains
its information by scanning the run-time stack and recovering the activation
records of all active subprograms. Stack unwinding is one of the most
important tools for program debugging.
@@ -19834,7 +19836,7 @@ The following is the subset of those switches that is most relevant:
@table @asis
-@item @code{--demangle[=@var{style}]}, @code{--no-demangle}
+@item @code{--demangle[=@emph{style}]}, @code{--no-demangle}
These options control whether symbol names should be demangled when
printing output. The default is to demangle C++ symbols. The
@@ -19850,9 +19852,9 @@ compiler, in particular Ada symbols generated by GNAT can be demangled using
@table @asis
-@item @code{-e @var{function_name}}
+@item @code{-e @emph{function_name}}
-The @code{-e @var{function}} option tells @code{gprof} not to print
+The @code{-e @emph{function}} option tells @code{gprof} not to print
information about the function @code{function_name} (and its
children…) in the call graph. The function will still be listed
as a child of any functions that call it, but its index number will be
@@ -19866,9 +19868,9 @@ option.
@table @asis
-@item @code{-E @var{function_name}}
+@item @code{-E @emph{function_name}}
-The @code{-E @var{function}} option works like the @code{-e} option, but
+The @code{-E @emph{function}} option works like the @code{-e} option, but
execution time spent in the function (and children who were not called from
anywhere else), will not be used to compute the percentages-of-time for
the call graph. More than one @code{-E} option may be given; only one
@@ -19880,9 +19882,9 @@ the call graph. More than one @code{-E} option may be given; only one
@table @asis
-@item @code{-f @var{function_name}}
+@item @code{-f @emph{function_name}}
-The @code{-f @var{function}} option causes @code{gprof} to limit the
+The @code{-f @emph{function}} option causes @code{gprof} to limit the
call graph to the function @code{function_name} and its children (and
their children…). More than one @code{-f} option may be given;
only one @code{function_name} may be indicated with each @code{-f}
@@ -19894,9 +19896,9 @@ option.
@table @asis
-@item @code{-F @var{function_name}}
+@item @code{-F @emph{function_name}}
-The @code{-F @var{function}} option works like the @code{-f} option, but
+The @code{-F @emph{function}} option works like the @code{-f} option, but
only time spent in the function and its children (and their
children…) will be used to determine total-time and
percentages-of-time for the call graph. More than one @code{-F} option
@@ -20195,7 +20197,7 @@ You should experiment to find the best level for your application.
Since the precise set of optimizations done at each level will vary from
release to release (and sometime from target to target), it is best to think
of the optimization settings in general terms.
-See the `Options That Control Optimization' section in
+See the @emph{Options That Control Optimization} section in
@cite{Using the GNU Compiler Collection (GCC)}
for details about
the @code{-O} settings and a number of @code{-f} options that
@@ -20204,7 +20206,7 @@ individually enable or disable specific optimizations.
Unlike some other compilation systems, @code{gcc} has
been tested extensively at all optimization levels. There are some bugs
which appear only with optimization turned on, but there have also been
-bugs which show up only in `unoptimized' code. Selecting a lower
+bugs which show up only in @emph{unoptimized} code. Selecting a lower
level of optimization does not improve the reliability of the code
generator, which in practice is highly reliable at all optimization
levels.
@@ -20253,7 +20255,7 @@ These are the most common cases:
@itemize *
@item
-`The ‘hopping Program Counter’:' Repeated @code{step} or @code{next}
+@emph{The ‘hopping Program Counter’:} Repeated @code{step} or @code{next}
commands show
the PC bouncing back and forth in the code. This may result from any of
the following optimizations:
@@ -20262,16 +20264,16 @@ the following optimizations:
@itemize -
@item
-`Common subexpression elimination:' using a single instance of code for a
+@emph{Common subexpression elimination:} using a single instance of code for a
quantity that the source computes several times. As a result you
may not be able to stop on what looks like a statement.
@item
-`Invariant code motion:' moving an expression that does not change within a
+@emph{Invariant code motion:} moving an expression that does not change within a
loop, to the beginning of the loop.
@item
-`Instruction scheduling:' moving instructions so as to
+@emph{Instruction scheduling:} moving instructions so as to
overlap loads and stores (typically) with other code, or in
general to move computations of values closer to their uses. Often
this causes you to pass an assignment statement without the assignment
@@ -20282,16 +20284,16 @@ expected side-effects.
@end itemize
@item
-`The ‘big leap’:' More commonly known as `cross-jumping', in which
+@emph{The ‘big leap’:} More commonly known as @emph{cross-jumping}, in which
two identical pieces of code are merged and the program counter suddenly
jumps to a statement that is not supposed to be executed, simply because
it (and the code following) translates to the same thing as the code
-that `was' supposed to be executed. This effect is typically seen in
+that @emph{was} supposed to be executed. This effect is typically seen in
sequences that end in a jump, such as a @code{goto}, a @code{return}, or
a @code{break} in a C @code{switch} statement.
@item
-`The ‘roving variable’:' The symptom is an unexpected value in a variable.
+@emph{The ‘roving variable’:} The symptom is an unexpected value in a variable.
There are various reasons for this effect:
@@ -20327,7 +20329,7 @@ calling subprogram to verify that the value observed is explainable from other
values (one must apply the procedure recursively to those
other values); or re-running the code and stopping a little earlier
(perhaps before the call) and stepping to better see how the variable obtained
-the value in question; or continuing to step `from' the point of the
+the value in question; or continuing to step @emph{from} the point of the
strange value to see if code motion had simply moved the variable’s
assignments later.
@end itemize
@@ -20372,7 +20374,7 @@ within it; the subprogram is small and optimization level @code{-O2} is
specified; optimization level @code{-O3} is specified.
@end itemize
-Calls to subprograms in `with'ed units are normally not inlined.
+Calls to subprograms in @emph{with}ed units are normally not inlined.
To achieve actual inlining (that is, replacement of the call by the code
in the body of the subprogram), the following conditions must all be true:
@@ -20694,7 +20696,7 @@ to work. Examples of switches in this category are @code{-funroll-loops}
and the various target-specific @code{-m} options (in particular, it has
been observed that @code{-march=xxx} can significantly improve performance
on appropriate machines). For full details of these switches, see
-the `Submodel Options' section in the `Hardware Models and Configurations'
+the @emph{Submodel Options} section in the @emph{Hardware Models and Configurations}
chapter of @cite{Using the GNU Compiler Collection (GCC)}.
@node Optimization and Strict Aliasing,Aliased Variables and Optimization,Other Optimization Switches,Performance Considerations
@@ -21137,7 +21139,7 @@ If @code{Text_IO} must be used, note that by default output to the standard
output and standard error files is unbuffered (this provides better
behavior when output statements are used for debugging, or if the
progress of a program is observed by tracking the output, e.g. by
-using the Unix `tail -f' command to watch redirected output).
+using the Unix @emph{tail -f} command to watch redirected output).
If you are generating large volumes of output with @code{Text_IO} and
performance is an important factor, use a designated file instead
@@ -21448,7 +21450,7 @@ The three modes are:
@itemize *
@item
-`Use base type for intermediate operations' (@code{STRICT})
+@emph{Use base type for intermediate operations} (@code{STRICT})
In this mode, all intermediate results for predefined arithmetic
operators are computed using the base type, and the result must
@@ -21458,7 +21460,7 @@ enabled) or the execution is erroneous (if overflow checks are suppressed).
This is the normal default mode.
@item
-`Most intermediate overflows avoided' (@code{MINIMIZED})
+@emph{Most intermediate overflows avoided} (@code{MINIMIZED})
In this mode, the compiler attempts to avoid intermediate overflows by
using a larger integer type, typically @code{Long_Long_Integer},
@@ -21491,12 +21493,12 @@ out of the range of @code{Long_Long_Integer} even though the final result
is in range and the precondition is True (from a mathematical point
of view). In such a case, operating in this mode, an overflow occurs
for the intermediate computation (which is why this mode
-says `most' intermediate overflows are avoided). In this case,
+says @emph{most} intermediate overflows are avoided). In this case,
an exception is raised if overflow checks are enabled, and the
execution is erroneous if overflow checks are suppressed.
@item
-`All intermediate overflows avoided' (@code{ELIMINATED})
+@emph{All intermediate overflows avoided} (@code{ELIMINATED})
In this mode, the compiler avoids all intermediate overflows
by using arbitrary precision arithmetic as required. In this
@@ -21761,8 +21763,8 @@ version 7.0.1 of GNAT onwards.
The GNAT-specific aspect @code{Dimension_System}
allows you to define a system of units; the aspect @code{Dimension}
then allows the user to declare dimensioned quantities within a given system.
-(These aspects are described in the `Implementation Defined Aspects'
-chapter of the `GNAT Reference Manual').
+(These aspects are described in the @emph{Implementation Defined Aspects}
+chapter of the @emph{GNAT Reference Manual}).
The major advantage of this model is that it does not require the declaration of
multiple operators for all possible combinations of types: it is only necessary
@@ -21959,9 +21961,9 @@ Final velocity: 98.10 m.s**(-1)
@geindex Dimensioned subtype
@end quotation
-The type @code{Mks_Type} is said to be a `dimensionable type' since it has a
+The type @code{Mks_Type} is said to be a @emph{dimensionable type} since it has a
@code{Dimension_System} aspect, and the subtypes @code{Length}, @code{Mass}, etc.,
-are said to be `dimensioned subtypes' since each one has a @code{Dimension}
+are said to be @emph{dimensioned subtypes} since each one has a @code{Dimension}
aspect.
@quotation
@@ -21975,8 +21977,8 @@ aspect.
The @code{Dimension} aspect of a dimensioned subtype @code{S} defines a mapping
from the base type’s Unit_Names to integer (or, more generally, rational)
-values. This mapping is the `dimension vector' (also referred to as the
-`dimensionality') for that subtype, denoted by @code{DV(S)}, and thus for each
+values. This mapping is the @emph{dimension vector} (also referred to as the
+@emph{dimensionality}) for that subtype, denoted by @code{DV(S)}, and thus for each
object of that subtype. Intuitively, the value specified for each
@code{Unit_Name} is the exponent associated with that unit; a zero value
means that the unit is not used. For example:
@@ -22002,34 +22004,34 @@ dimension vectors of its components, with compile-time dimensionality checks
that help prevent mismatches such as using an @code{Acceleration} where a
@code{Length} is required.
-The dimension vector of the result of an arithmetic expression `expr', or
-@code{DV(@var{expr})}, is defined as follows, assuming conventional
+The dimension vector of the result of an arithmetic expression @emph{expr}, or
+@code{DV(@emph{expr})}, is defined as follows, assuming conventional
mathematical definitions for the vector operations that are used:
@itemize *
@item
-If `expr' is of the type `universal_real', or is not of a dimensioned subtype,
-then `expr' is dimensionless; @code{DV(@var{expr})} is the empty vector.
+If @emph{expr} is of the type @emph{universal_real}, or is not of a dimensioned subtype,
+then @emph{expr} is dimensionless; @code{DV(@emph{expr})} is the empty vector.
@item
-@code{DV(@var{op expr})}, where `op' is a unary operator, is @code{DV(@var{expr})}
+@code{DV(@emph{op expr})}, where @emph{op} is a unary operator, is @code{DV(@emph{expr})}
@item
-@code{DV(@var{expr1 op expr2})} where `op' is “+” or “-” is @code{DV(@var{expr1})}
-provided that @code{DV(@var{expr1})} = @code{DV(@var{expr2})}.
+@code{DV(@emph{expr1 op expr2})} where @emph{op} is “+” or “-” is @code{DV(@emph{expr1})}
+provided that @code{DV(@emph{expr1})} = @code{DV(@emph{expr2})}.
If this condition is not met then the construct is illegal.
@item
-@code{DV(@var{expr1} * @var{expr2})} is @code{DV(@var{expr1})} + @code{DV(@var{expr2})},
-and @code{DV(@var{expr1} / @var{expr2})} = @code{DV(@var{expr1})} - @code{DV(@var{expr2})}.
-In this context if one of the `expr's is dimensionless then its empty
+@code{DV(@emph{expr1} * @emph{expr2})} is @code{DV(@emph{expr1})} + @code{DV(@emph{expr2})},
+and @code{DV(@emph{expr1} / @emph{expr2})} = @code{DV(@emph{expr1})} - @code{DV(@emph{expr2})}.
+In this context if one of the @emph{expr}s is dimensionless then its empty
dimension vector is treated as @code{(others => 0)}.
@item
-@code{DV(@var{expr} ** @var{power})} is `power' * @code{DV(@var{expr})},
-provided that `power' is a static rational value. If this condition is not
+@code{DV(@emph{expr} ** @emph{power})} is @emph{power} * @code{DV(@emph{expr})},
+provided that @emph{power} is a static rational value. If this condition is not
met then the construct is illegal.
@end itemize
@@ -22069,17 +22071,17 @@ acc > 10.0
is accepted with a warning. Analogously a conditional expression requires the
same dimension vector for each branch (with no exception for literals).
-The dimension vector of a type conversion @code{T(@var{expr})} is defined
+The dimension vector of a type conversion @code{T(@emph{expr})} is defined
as follows, based on the nature of @code{T}:
@itemize *
@item
-If @code{T} is a dimensioned subtype then @code{DV(T(@var{expr}))} is @code{DV(T)}
-provided that either `expr' is dimensionless or
-@code{DV(T)} = @code{DV(@var{expr})}. The conversion is illegal
-if `expr' is dimensioned and @code{DV(@var{expr})} /= @code{DV(T)}.
+If @code{T} is a dimensioned subtype then @code{DV(T(@emph{expr}))} is @code{DV(T)}
+provided that either @emph{expr} is dimensionless or
+@code{DV(T)} = @code{DV(@emph{expr})}. The conversion is illegal
+if @emph{expr} is dimensioned and @code{DV(@emph{expr})} /= @code{DV(T)}.
Note that vector equality does not require that the corresponding
Unit_Names be the same.
@@ -22091,9 +22093,9 @@ a length in inches (with a suitable conversion factor) but cannot be
converted, for example, to a mass in pounds.
@item
-If @code{T} is the base type for `expr' (and the dimensionless root type of
-the dimension system), then @code{DV(T(@var{expr}))} is @code{DV(expr)}.
-Thus, if `expr' is of a dimensioned subtype of @code{T}, the conversion may
+If @code{T} is the base type for @emph{expr} (and the dimensionless root type of
+the dimension system), then @code{DV(T(@emph{expr}))} is @code{DV(expr)}.
+Thus, if @emph{expr} is of a dimensioned subtype of @code{T}, the conversion may
be regarded as a “view conversion” that preserves dimensionality.
This rule makes it possible to write generic code that can be instantiated
@@ -22105,13 +22107,13 @@ dimensionality.
@item
Otherwise (i.e., @code{T} is neither a dimensioned subtype nor a dimensionable
-base type), @code{DV(T(@var{expr}))} is the empty vector. Thus a dimensioned
+base type), @code{DV(T(@emph{expr}))} is the empty vector. Thus a dimensioned
value can be explicitly converted to a non-dimensioned subtype, which
of course then escapes dimensionality analysis.
@end itemize
-The dimension vector for a type qualification @code{T'(@var{expr})} is the same
-as for the type conversion @code{T(@var{expr})}.
+The dimension vector for a type qualification @code{T'(@emph{expr})} is the same
+as for the type conversion @code{T(@emph{expr})}.
An assignment statement
@@ -22301,16 +22303,16 @@ where:
@itemize *
@item
-`Index' is a number associated with each task.
+@emph{Index} is a number associated with each task.
@item
-`Task Name' is the name of the task analyzed.
+@emph{Task Name} is the name of the task analyzed.
@item
-`Stack Size' is the maximum size for the stack.
+@emph{Stack Size} is the maximum size for the stack.
@item
-`Stack Usage' is the measure done by the stack analyzer.
+@emph{Stack Usage} is the measure done by the stack analyzer.
In order to prevent overflow, the stack
is not entirely analyzed, and it’s not possible to know exactly how
much has actually been used.
@@ -22641,7 +22643,7 @@ For exception handling, either or both of two models are supplied:
@itemize *
@item
-`Zero-Cost Exceptions' (“ZCX”),
+@strong{Zero-Cost Exceptions} (“ZCX”),
which uses binder-generated tables that
are interrogated at run time to locate a handler.
@@ -22650,7 +22652,7 @@ are interrogated at run time to locate a handler.
@geindex SJLJ (setjmp/longjmp Exception Model)
@item
-`setjmp / longjmp' (‘SJLJ’),
+@strong{setjmp / longjmp} (‘SJLJ’),
which uses dynamically-set data to establish
the set of handlers
@end itemize
@@ -22796,7 +22798,7 @@ contain a complete source and binary subdirectory. The detailed description
below explains the differences between the different libraries in terms of
their thread support.
-The default run-time library (when GNAT is installed) is `rts-native'.
+The default run-time library (when GNAT is installed) is @emph{rts-native}.
This default run-time is selected by the means of soft links.
For example on x86-linux:
@@ -22840,7 +22842,7 @@ ADAINCLUDE ADALIB rts-native rts-sjlj
(Upper-case names and dotted/dashed arrows represent soft links)
@end example
-If the `rts-sjlj' library is to be selected on a permanent basis,
+If the @emph{rts-sjlj} library is to be selected on a permanent basis,
these soft links can be modified with the following commands:
@quotation
@@ -23011,11 +23013,11 @@ Independent.
If you are not interested in building PIE binaries, you can simply
turn this feature off by first compiling your code with @code{-fno-pie}
and then by linking with @code{-no-pie} (note the subtle but important
-difference in the names of the options – the linker option does `not'
+difference in the names of the options – the linker option does @strong{not}
have an @cite{f} after the dash!). When using gprbuild, this is
-achieved by updating the `Required_Switches' attribute in package @cite{Compiler}
-and, depending on your type of project, either attribute `Switches'
-or attribute `Library_Options' in package @cite{Linker}.
+achieved by updating the @emph{Required_Switches} attribute in package @cite{Compiler}
+and, depending on your type of project, either attribute @emph{Switches}
+or attribute @emph{Library_Options} in package @cite{Linker}.
On the other hand, if you would like to build PIE binaries and you are
getting the error above, a quick and easy workaround to allow linking
@@ -23545,12 +23547,12 @@ on the stack by the caller from right to left. The callee (and not the
caller) is in charge of cleaning the stack on routine exit. In addition,
the name of a routine with @code{Stdcall} calling convention is mangled by
adding a leading underscore (as for the @code{C} calling convention) and a
-trailing @code{@@@var{nn}}, where @code{nn} is the overall size (in
+trailing @code{@@@emph{nn}}, where @code{nn} is the overall size (in
bytes) of the parameters passed to the routine.
The name to use on the Ada side when importing a C routine with a
@code{Stdcall} calling convention is the name of the C routine. The leading
-underscore and trailing @code{@@@var{nn}} are added automatically by
+underscore and trailing @code{@@@emph{nn}} are added automatically by
the compiler. For instance the Win32 function:
@quotation
@@ -23597,10 +23599,10 @@ pragma Import (Stdcall, Get_Val, Link_Name => "retrieve_val");
then the imported routine is @code{retrieve_val}, that is, there is no
decoration at all. No leading underscore and no Stdcall suffix
-@code{@@@var{nn}}.
+@code{@@@emph{nn}}.
This is especially important as in some special cases a DLL’s entry
-point name lacks a trailing @code{@@@var{nn}} while the exported
+point name lacks a trailing @code{@@@emph{nn}} while the exported
name generated for a call has it.
It is also possible to import variables defined in a DLL by using an
@@ -23901,16 +23903,16 @@ EXPORTS
@table @asis
-@item `LIBRARY name'
+@item @emph{LIBRARY name}
This section, which is optional, gives the name of the DLL.
-@item `DESCRIPTION string'
+@item @emph{DESCRIPTION string}
This section, which is optional, gives a description string that will be
embedded in the import library.
-@item `EXPORTS'
+@item @emph{EXPORTS}
This section gives the list of exported symbols (procedures, functions or
variables). For instance in the case of @code{API.dll} the @code{EXPORTS}
@@ -23923,7 +23925,7 @@ EXPORTS
@end example
@end table
-Note that you must specify the correct suffix (@code{@@@var{nn}})
+Note that you must specify the correct suffix (@code{@@@emph{nn}})
(see @ref{1d6,,Windows Calling Conventions}) for a Stdcall
calling convention function in the exported symbols list.
@@ -23944,11 +23946,11 @@ $ dlltool API.dll -z API.def --export-all-symbols
@end example
Note that if some routines in the DLL have the @code{Stdcall} convention
-(@ref{1d6,,Windows Calling Conventions}) with stripped @code{@@@var{nn}}
+(@ref{1d6,,Windows Calling Conventions}) with stripped @code{@@@emph{nn}}
suffix then you’ll have to edit @code{api.def} to add it, and specify
@code{-k} to @code{gnatdll} when creating the import library.
-Here are some hints to find the right @code{@@@var{nn}} suffix.
+Here are some hints to find the right @code{@@@emph{nn}} suffix.
@itemize -
@@ -24030,8 +24032,8 @@ See the Microsoft documentation for further details about the usage of
@geindex building
There is nothing specific to Windows in the build process.
-See the `Library Projects' section in the `GNAT Project Manager'
-chapter of the `GPRbuild User’s Guide'.
+See the @emph{Library Projects} section in the @emph{GNAT Project Manager}
+chapter of the @emph{GPRbuild User’s Guide}.
Due to a system limitation, it is not possible under Windows to create threads
when inside the @code{DllMain} routine which is used for auto-initialization
@@ -24166,8 +24168,8 @@ Note that a relocatable DLL stripped using the @code{strip}
binutils tool will not be relocatable anymore. To build a DLL without
debug information pass @code{-largs -s} to @code{gnatdll}. This
restriction does not apply to a DLL built using a Library Project.
-See the `Library Projects' section in the `GNAT Project Manager'
-chapter of the `GPRbuild User’s Guide'.
+See the @emph{Library Projects} section in the @emph{GNAT Project Manager}
+chapter of the @emph{GPRbuild User’s Guide}.
@c Limitations_When_Using_Ada_DLLs_from Ada:
@@ -24482,7 +24484,7 @@ You may specify any of the following switches to @code{gnatdll}:
@table @asis
-@item @code{-a[`address']}
+@item @code{-a[@emph{address}]}
Build a non-relocatable DLL at @code{address}. If @code{address} is not
specified the default address @code{0x11000000} will be used. By default,
@@ -24491,20 +24493,20 @@ advise the reader to build relocatable DLL.
@geindex -b (gnatdll)
-@item @code{-b `address'}
+@item @code{-b @emph{address}}
Set the relocatable DLL base address. By default the address is
@code{0x11000000}.
@geindex -bargs (gnatdll)
-@item @code{-bargs `opts'}
+@item @code{-bargs @emph{opts}}
Binder options. Pass @code{opts} to the binder.
@geindex -d (gnatdll)
-@item @code{-d `dllfile'}
+@item @code{-d @emph{dllfile}}
@code{dllfile} is the name of the DLL. This switch must be present for
@code{gnatdll} to do anything. The name of the generated import library is
@@ -24518,7 +24520,7 @@ file used is @code{xyz.def}.
@geindex -e (gnatdll)
-@item @code{-e `deffile'}
+@item @code{-e @emph{deffile}}
@code{deffile} is the name of the definition file.
@@ -24540,7 +24542,7 @@ Help mode. Displays @code{gnatdll} switch usage information.
@geindex -I (gnatdll)
-@item @code{-I`dir'}
+@item @code{-I@emph{dir}}
Direct @code{gnatdll} to search the @code{dir} directory for source and
object files needed to build the DLL.
@@ -24550,16 +24552,16 @@ object files needed to build the DLL.
@item @code{-k}
-Removes the @code{@@@var{nn}} suffix from the import library’s exported
+Removes the @code{@@@emph{nn}} suffix from the import library’s exported
names, but keeps them for the link names. You must specify this
option if you want to use a @code{Stdcall} function in a DLL for which
-the @code{@@@var{nn}} suffix has been removed. This is the case for most
+the @code{@@@emph{nn}} suffix has been removed. This is the case for most
of the Windows NT DLL for example. This option has no effect when
@code{-n} option is specified.
@geindex -l (gnatdll)
-@item @code{-l `file'}
+@item @code{-l @emph{file}}
The list of ALI and object files used to build the DLL are listed in
@code{file}, instead of being given in the command line. Each line in
@@ -24585,7 +24587,7 @@ Verbose mode. Display extra information.
@geindex -largs (gnatdll)
-@item @code{-largs `opts'}
+@item @code{-largs @emph{opts}}
Linker options. Pass @code{opts} to the linker.
@end table
@@ -24719,7 +24721,7 @@ $ dlltool [`switches`]
@table @asis
-@item @code{--base-file `basefile'}
+@item @code{--base-file @emph{basefile}}
Read the base file @code{basefile} generated by the linker. This switch
is used to create a relocatable DLL.
@@ -24730,7 +24732,7 @@ is used to create a relocatable DLL.
@table @asis
-@item @code{--def `deffile'}
+@item @code{--def @emph{deffile}}
Read the definition file.
@end table
@@ -24740,7 +24742,7 @@ Read the definition file.
@table @asis
-@item @code{--dllname `name'}
+@item @code{--dllname @emph{name}}
Gives the name of the DLL. This switch is used to embed the name of the
DLL in the static import library generated by @code{dlltool} with switch
@@ -24754,7 +24756,7 @@ DLL in the static import library generated by @code{dlltool} with switch
@item @code{-k}
-Kill @code{@@@var{nn}} from exported names
+Kill @code{@@@emph{nn}} from exported names
(@ref{1d6,,Windows Calling Conventions}
for a discussion about @code{Stdcall}-style symbols).
@end table
@@ -24774,7 +24776,7 @@ Prints the @code{dlltool} switches with a concise description.
@table @asis
-@item @code{--output-exp `exportfile'}
+@item @code{--output-exp @emph{exportfile}}
Generate an export file @code{exportfile}. The export file contains the
export table (list of symbols in the DLL) and is used to create the DLL.
@@ -24785,7 +24787,7 @@ export table (list of symbols in the DLL) and is used to create the DLL.
@table @asis
-@item @code{--output-lib `libfile'}
+@item @code{--output-lib @emph{libfile}}
Generate a static import library @code{libfile}.
@end table
@@ -24805,7 +24807,7 @@ Verbose mode.
@table @asis
-@item @code{--as `assembler-name'}
+@item @code{--as @emph{assembler-name}}
Use @code{assembler-name} as the assembler. The default is @code{as}.
@end table
@@ -25280,7 +25282,7 @@ $ main
@end example
@item
-Use the Windows `Task Manager' to find the process ID. Let’s say
+Use the Windows @emph{Task Manager} to find the process ID. Let’s say
that the process PID for @code{main.exe} is 208.
@item
@@ -25332,7 +25334,7 @@ approach to debug a program as described in
It is possible to specify the program stack size at link time. On modern
versions of Windows, starting with XP, this is mostly useful to set the size of
the main stack (environment task). The other task stacks are set with pragma
-Storage_Size or with the `gnatbind -d' command.
+Storage_Size or with the @emph{gnatbind -d} command.
Since older versions of Windows (2000, NT4, etc.) do not allow setting the
reserve size of individual tasks, the link-time stack size applies to all
@@ -25581,7 +25583,7 @@ in the Unix group @code{_developer}.
@geindex Binder output (example)
This Appendix displays the source code for the output file
-generated by `gnatbind' for a simple ‘Hello World’ program.
+generated by @emph{gnatbind} for a simple ‘Hello World’ program.
Comments have been added for clarification purposes.
@example
@@ -26360,13 +26362,13 @@ GNAT, either automatically or with explicit programming features.
@section Elaboration Code
-Ada defines the term `execution' as the process by which a construct achieves
-its run-time effect. This process is also referred to as `elaboration' for
-declarations and `evaluation' for expressions.
+Ada defines the term @emph{execution} as the process by which a construct achieves
+its run-time effect. This process is also referred to as @strong{elaboration} for
+declarations and @emph{evaluation} for expressions.
The execution model in Ada allows for certain sections of an Ada program to be
executed prior to execution of the program itself, primarily with the intent of
-initializing data. These sections are referred to as `elaboration code'.
+initializing data. These sections are referred to as @strong{elaboration code}.
Elaboration code is executed as follows:
@@ -26383,7 +26385,7 @@ partition.
@item
The environment task executes all elaboration code (if available) for all
units within that partition. This code is said to be executed at
-`elaboration time'.
+@strong{elaboration time}.
@item
The environment task executes the Ada program (if available) for that
@@ -26396,16 +26398,16 @@ In addition to the Ada terminology, this appendix defines the following terms:
@itemize *
@item
-`Invocation'
+@emph{Invocation}
The act of calling a subprogram, instantiating a generic, or activating a
task.
@item
-`Scenario'
+@emph{Scenario}
A construct that is elaborated or invoked by elaboration code is referred to
-as an `elaboration scenario' or simply a `scenario'. GNAT recognizes the
+as an @emph{elaboration scenario} or simply a @strong{scenario}. GNAT recognizes the
following scenarios:
@@ -26425,10 +26427,10 @@ Instantiations of generic templates
@end itemize
@item
-`Target'
+@emph{Target}
-A construct elaborated by a scenario is referred to as `elaboration target'
-or simply `target'. GNAT recognizes the following targets:
+A construct elaborated by a scenario is referred to as @emph{elaboration target}
+or simply @strong{target}. GNAT recognizes the following targets:
@itemize -
@@ -26456,7 +26458,7 @@ Elaboration code may appear in two distinct contexts:
@itemize *
@item
-`Library level'
+@emph{Library level}
A scenario appears at the library level when it is encapsulated by a package
[body] compilation unit, ignoring any other package [body] declarations in
@@ -26480,7 +26482,7 @@ given above. As a result, the call to @code{Server.Func} will be invoked when
the spec of unit @code{Client} is elaborated.
@item
-`Package body statements'
+@emph{Package body statements}
A scenario appears within the statement sequence of a package body when it is
bounded by the region starting from the @code{begin} keyword of the package body
@@ -26509,7 +26511,7 @@ elaborated.
The sequence by which the elaboration code of all units within a partition is
-executed is referred to as `elaboration order'.
+executed is referred to as @strong{elaboration order}.
Within a single unit, elaboration code is executed in sequential order.
@@ -26573,7 +26575,7 @@ factors:
@itemize *
@item
-`with'ed units
+@emph{with}ed units
@item
parent units
@@ -26626,7 +26628,7 @@ procedure Main is begin null; end Main;
@end quotation
The following elaboration order exhibits a fundamental problem referred to as
-`access-before-elaboration' or simply `ABE'.
+@emph{access-before-elaboration} or simply @strong{ABE}.
@quotation
@@ -26666,7 +26668,7 @@ body of Main
Ada states that a total elaboration order must exist, but it does not define
what this order is. A compiler is thus tasked with choosing a suitable
-elaboration order which satisfies the dependencies imposed by `with' clauses,
+elaboration order which satisfies the dependencies imposed by @emph{with} clauses,
unit categorization, elaboration-control pragmas, and invocations performed in
elaboration code. Ideally an order that avoids ABE problems should be chosen,
however a compiler may not always find such an order due to complications with
@@ -26684,15 +26686,15 @@ provides three lines of defense:
@itemize *
@item
-`Static semantics'
+@emph{Static semantics}
Static semantic rules restrict the possible choice of elaboration order. For
-instance, if unit Client `with's unit Server, then the spec of Server is
+instance, if unit Client @emph{with}s unit Server, then the spec of Server is
always elaborated prior to Client. The same principle applies to child units
- the spec of a parent unit is always elaborated prior to the child unit.
@item
-`Dynamic semantics'
+@emph{Dynamic semantics}
Dynamic checks are performed at run time, to ensure that a target is
elaborated prior to a scenario that invokes it, thus avoiding ABE problems.
@@ -26703,19 +26705,19 @@ restrictions apply:
@itemize -
@item
-`Restrictions on calls'
+@emph{Restrictions on calls}
An entry, operator, or subprogram can be called from elaboration code only
when the corresponding body has been elaborated.
@item
-`Restrictions on instantiations'
+@emph{Restrictions on instantiations}
A generic unit can be instantiated by elaboration code only when the
corresponding body has been elaborated.
@item
-`Restrictions on task activation'
+@emph{Restrictions on task activation}
A task can be activated by elaboration code only when the body of the
associated task type has been elaborated.
@@ -26723,11 +26725,11 @@ associated task type has been elaborated.
The restrictions above can be summarized by the following rule:
-`If a target has a body, then this body must be elaborated prior to the
-scenario that invokes the target.'
+@emph{If a target has a body, then this body must be elaborated prior to the
+scenario that invokes the target.}
@item
-`Elaboration control'
+@emph{Elaboration control}
Pragmas are provided for the programmer to specify the desired elaboration
order.
@@ -26745,7 +26747,7 @@ the desired elaboration order and avoiding ABE problems altogether.
@itemize *
@item
-`Packages without a body'
+@emph{Packages without a body}
A library package which does not require a completing body does not suffer
from ABE problems.
@@ -26772,7 +26774,7 @@ any ABE problems.
@itemize *
@item
-`pragma Pure'
+@emph{pragma Pure}
Pragma @code{Pure} places sufficient restrictions on a unit to guarantee that no
scenario within the unit can result in an ABE problem.
@@ -26784,7 +26786,7 @@ scenario within the unit can result in an ABE problem.
@itemize *
@item
-`pragma Preelaborate'
+@emph{pragma Preelaborate}
Pragma @code{Preelaborate} is slightly less restrictive than pragma @code{Pure},
but still strong enough to prevent ABE problems within a unit.
@@ -26796,7 +26798,7 @@ but still strong enough to prevent ABE problems within a unit.
@itemize *
@item
-`pragma Elaborate_Body'
+@emph{pragma Elaborate_Body}
Pragma @code{Elaborate_Body} requires that the body of a unit is elaborated
immediately after its spec. This restriction guarantees that no client
@@ -26837,7 +26839,7 @@ spec of Client
@end example
because the spec of @code{Server} must be elaborated prior to @code{Client} by
-virtue of the `with' clause, and in addition the body of @code{Server} must be
+virtue of the @emph{with} clause, and in addition the body of @code{Server} must be
elaborated immediately after the spec of @code{Server}.
Removing pragma @code{Elaborate_Body} could result in the following incorrect
@@ -26868,10 +26870,10 @@ depend on.
@itemize *
@item
-`pragma Elaborate (Unit)'
+@emph{pragma Elaborate (Unit)}
Pragma @code{Elaborate} can be placed in the context clauses of a unit, after a
-`with' clause. It guarantees that both the spec and body of its argument will
+@emph{with} clause. It guarantees that both the spec and body of its argument will
be elaborated prior to the unit with the pragma. Note that other unrelated
units may be elaborated in between the spec and the body.
@@ -26926,12 +26928,12 @@ has not been elaborated yet.
@itemize *
@item
-`pragma Elaborate_All (Unit)'
+@emph{pragma Elaborate_All (Unit)}
Pragma @code{Elaborate_All} is placed in the context clauses of a unit, after
-a `with' clause. It guarantees that both the spec and body of its argument
+a @emph{with} clause. It guarantees that both the spec and body of its argument
will be elaborated prior to the unit with the pragma, as well as all units
-`with'ed by the spec and body of the argument, recursively. Note that other
+@emph{with}ed by the spec and body of the argument, recursively. Note that other
unrelated units may be elaborated in between the spec and the body.
@example
@@ -27017,10 +27019,10 @@ elaborated yet.
All pragmas shown above can be summarized by the following rule:
-`If a client unit elaborates a server target directly or indirectly, then if
+@emph{If a client unit elaborates a server target directly or indirectly, then if
the server unit requires a body and does not have pragma Pure, Preelaborate,
or Elaborate_Body, then the client unit should have pragma Elaborate or
-Elaborate_All for the server unit.'
+Elaborate_All for the server unit.}
If the rule outlined above is not followed, then a program may fall in one of
the following states:
@@ -27029,19 +27031,19 @@ the following states:
@itemize *
@item
-`No elaboration order exists'
+@emph{No elaboration order exists}
In this case a compiler must diagnose the situation, and refuse to build an
executable program.
@item
-`One or more incorrect elaboration orders exist'
+@emph{One or more incorrect elaboration orders exist}
In this case a compiler can build an executable program, but
@code{Program_Error} will be raised when the program is run.
@item
-`Several elaboration orders exist, some correct, some incorrect'
+@emph{Several elaboration orders exist, some correct, some incorrect}
In this case the programmer has not controlled the elaboration order. As a
result, a compiler may or may not pick one of the correct orders, and the
@@ -27050,7 +27052,7 @@ worst possible state because the program may fail on another compiler, or
even another version of the same compiler.
@item
-`One or more correct orders exist'
+@emph{One or more correct orders exist}
In this case a compiler can build an executable program, and the program is
run successfully. This state may be guaranteed by following the outlined
@@ -27076,7 +27078,7 @@ elaboration order and to diagnose elaboration problems.
@itemize *
@item
-`Dynamic elaboration model'
+@emph{Dynamic elaboration model}
This is the most permissive of the three elaboration models and emulates the
behavior specified by the Ada Reference Manual. When the dynamic model is in
@@ -27098,7 +27100,7 @@ GNAT performs extensive diagnostics on a unit-by-unit basis for all scenarios
that invoke internal targets. In addition, GNAT generates run-time checks for
all external targets and for all scenarios that may exhibit ABE problems.
-The elaboration order is obtained by honoring all `with' clauses, purity and
+The elaboration order is obtained by honoring all @emph{with} clauses, purity and
preelaborability of units, and elaboration-control pragmas. The dynamic model
attempts to take all invocations in elaboration code into account. If an
invocation leads to a circularity, GNAT ignores the invocation based on the
@@ -27114,7 +27116,7 @@ The dynamic model is enabled with compiler switch @code{-gnatE}.
@itemize *
@item
-`Static elaboration model'
+@emph{Static elaboration model}
This is the middle ground of the three models. When the static model is in
effect, GNAT makes the following assumptions:
@@ -27135,7 +27137,7 @@ GNAT performs extensive diagnostics on a unit-by-unit basis for all scenarios
that invoke internal targets. In addition, GNAT generates run-time checks for
all external targets and for all scenarios that may exhibit ABE problems.
-The elaboration order is obtained by honoring all `with' clauses, purity and
+The elaboration order is obtained by honoring all @emph{with} clauses, purity and
preelaborability of units, presence of elaboration-control pragmas, and all
invocations in elaboration code. An order obtained using the static model is
guaranteed to be ABE problem-free, excluding dispatching calls and
@@ -27150,7 +27152,7 @@ The static model is the default model in GNAT.
@itemize *
@item
-`SPARK elaboration model'
+@emph{SPARK elaboration model}
This is the most conservative of the three models and enforces the SPARK
rules of elaboration as defined in the SPARK Reference Manual, section 7.7.
@@ -27167,7 +27169,7 @@ The SPARK model is enabled with compiler switch @code{-gnatd.v}.
@itemize *
@item
-`Legacy elaboration models'
+@emph{Legacy elaboration models}
In addition to the three elaboration models outlined above, GNAT provides the
following legacy models:
@@ -27203,7 +27205,7 @@ however the following rules must be observed:
@itemize *
@item
-A client unit compiled with the dynamic model can only `with' a server unit
+A client unit compiled with the dynamic model can only @emph{with} a server unit
that meets at least one of the following criteria:
@@ -27253,8 +27255,8 @@ conservative, or a particular scenario may not be invoked due conditional
execution. The warnings can be suppressed selectively with @code{pragma Warnings
(Off)} or globally with compiler switch @code{-gnatwL}.
-A `guaranteed ABE' arises when the body of a target is not elaborated early
-enough, and causes `all' scenarios that directly invoke the target to fail.
+A @emph{guaranteed ABE} arises when the body of a target is not elaborated early
+enough, and causes @emph{all} scenarios that directly invoke the target to fail.
@quotation
@@ -27286,8 +27288,8 @@ the declaration of @code{Val}. This invokes function @code{ABE}, however the bod
@end example
@end quotation
-A `conditional ABE' arises when the body of a target is not elaborated early
-enough, and causes `some' scenarios that directly invoke the target to fail.
+A @emph{conditional ABE} arises when the body of a target is not elaborated early
+enough, and causes @emph{some} scenarios that directly invoke the target to fail.
@quotation
@@ -27376,9 +27378,9 @@ rules.
@section Elaboration Circularities
-An `elaboration circularity' occurs whenever the elaboration of a set of
+An @strong{elaboration circularity} occurs whenever the elaboration of a set of
units enters a deadlocked state, where each unit is waiting for another unit
-to be elaborated. This situation may be the result of improper use of `with'
+to be elaborated. This situation may be the result of improper use of @emph{with}
clauses, elaboration-control pragmas, or invocations in elaboration code.
The following example exhibits an elaboration circularity.
@@ -27486,7 +27488,7 @@ too much modification, especially in the case of complex legacy code.
When faced with an elaboration circularity, the programmer should also consider
the tactics given in the suggestions section of the circularity diagnostic.
-Depending on the units involved in the circularity, their `with' clauses,
+Depending on the units involved in the circularity, their @emph{with} clauses,
purity, preelaborability, presence of elaboration-control pragmas and
invocations at elaboration time, the binder may suggest one or more of the
following tactics to eliminate the circularity:
@@ -27539,7 +27541,7 @@ Prevents a set of units from being elaborated.
@item
The removal of the pragma will not eliminate the semantic effects of the
-pragma. In other words, the argument of the pragma along with its `with'
+pragma. In other words, the argument of the pragma along with its @emph{with}
closure will still be elaborated prior to the unit containing the pragma.
@item
@@ -27783,20 +27785,20 @@ information depending on the elaboration model in effect.
@itemize -
@item
-`Dynamic model'
+@emph{Dynamic model}
GNAT will indicate missing @code{Elaborate} and @code{Elaborate_All} pragmas for
all library-level scenarios within the partition.
@item
-`Static model'
+@emph{Static model}
GNAT will indicate all scenarios invoked during elaboration. In addition,
it will provide detailed traceback when an implicit @code{Elaborate} or
@code{Elaborate_All} pragma is generated.
@item
-`SPARK model'
+@emph{SPARK model}
GNAT will indicate how an elaboration requirement is met by the context of
a unit. This diagnostic requires compiler switch @code{-gnatd.v}.
@@ -28199,7 +28201,7 @@ pre-processor) documentation for further information.
@display
-`Register names'@w{ }
+@emph{Register names}@w{ }
@display
gcc / @code{as}: Prefix with ‘%’; for example @code{%eax}@w{ }
Intel: No extra punctuation; for example @code{eax}@w{ }
@@ -28210,7 +28212,7 @@ Intel: No extra punctuation; for example @code{eax}@w{ }
@display
-`Immediate operand'@w{ }
+@emph{Immediate operand}@w{ }
@display
gcc / @code{as}: Prefix with ‘$’; for example @code{$4}@w{ }
Intel: No extra punctuation; for example @code{4}@w{ }
@@ -28221,7 +28223,7 @@ Intel: No extra punctuation; for example @code{4}@w{ }
@display
-`Address'@w{ }
+@emph{Address}@w{ }
@display
gcc / @code{as}: Prefix with ‘$’; for example @code{$loc}@w{ }
Intel: No extra punctuation; for example @code{loc}@w{ }
@@ -28232,7 +28234,7 @@ Intel: No extra punctuation; for example @code{loc}@w{ }
@display
-`Memory contents'@w{ }
+@emph{Memory contents}@w{ }
@display
gcc / @code{as}: No extra punctuation; for example @code{loc}@w{ }
Intel: Square brackets; for example @code{[loc]}@w{ }
@@ -28243,7 +28245,7 @@ Intel: Square brackets; for example @code{[loc]}@w{ }
@display
-`Register contents'@w{ }
+@emph{Register contents}@w{ }
@display
gcc / @code{as}: Parentheses; for example @code{(%eax)}@w{ }
Intel: Square brackets; for example @code{[eax]}@w{ }
@@ -28254,7 +28256,7 @@ Intel: Square brackets; for example @code{[eax]}@w{ }
@display
-`Hexadecimal numbers'@w{ }
+@emph{Hexadecimal numbers}@w{ }
@display
gcc / @code{as}: Leading ‘0x’ (C language syntax); for example @code{0xA0}@w{ }
Intel: Trailing ‘h’; for example @code{A0h}@w{ }
@@ -28265,7 +28267,7 @@ Intel: Trailing ‘h’; for example @code{A0h}@w{ }
@display
-`Operand size'@w{ }
+@emph{Operand size}@w{ }
@display
gcc / @code{as}: Explicit in op code; for example @code{movw} to move a 16-bit word@w{ }
Intel: Implicit, deduced by assembler; for example @code{mov}@w{ }
@@ -28276,7 +28278,7 @@ Intel: Implicit, deduced by assembler; for example @code{mov}@w{ }
@display
-`Instruction repetition'@w{ }
+@emph{Instruction repetition}@w{ }
@display
gcc / @code{as}: Split into two lines; for example@w{ }
@display
@@ -28291,7 +28293,7 @@ Intel: Keep on one line; for example @code{rep stosl}@w{ }
@display
-`Order of operands'@w{ }
+@emph{Order of operands}@w{ }
@display
gcc / @code{as}: Source first; for example @code{movw $4, %eax}@w{ }
Intel: Destination first; for example @code{mov eax, 4}@w{ }
@@ -28322,7 +28324,7 @@ end Nothing;
@end quotation
@code{Asm} is a procedure declared in package @code{System.Machine_Code};
-here it takes one parameter, a `template string' that must be a static
+here it takes one parameter, a @emph{template string} that must be a static
expression and that will form the generated instruction.
@code{Asm} may be regarded as a compile-time procedure that parses
the template string and additional parameters (none here),
@@ -28605,7 +28607,7 @@ most useful (for the Intel x86 processor) are the following:
@multitable {xxxxxxxx} {xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx}
@item
-`='
+@emph{=}
@tab
@@ -28613,7 +28615,7 @@ output constraint
@item
-`g'
+@emph{g}
@tab
@@ -28621,7 +28623,7 @@ global (i.e., can be stored anywhere)
@item
-`m'
+@emph{m}
@tab
@@ -28629,7 +28631,7 @@ in memory
@item
-`I'
+@emph{I}
@tab
@@ -28637,7 +28639,7 @@ a constant
@item
-`a'
+@emph{a}
@tab
@@ -28645,7 +28647,7 @@ use eax
@item
-`b'
+@emph{b}
@tab
@@ -28653,7 +28655,7 @@ use ebx
@item
-`c'
+@emph{c}
@tab
@@ -28661,7 +28663,7 @@ use ecx
@item
-`d'
+@emph{d}
@tab
@@ -28669,7 +28671,7 @@ use edx
@item
-`S'
+@emph{S}
@tab
@@ -28677,7 +28679,7 @@ use esi
@item
-`D'
+@emph{D}
@tab
@@ -28685,7 +28687,7 @@ use edi
@item
-`r'
+@emph{r}
@tab
@@ -28693,7 +28695,7 @@ use one of eax, ebx, ecx or edx
@item
-`q'
+@emph{q}
@tab
@@ -28708,7 +28710,7 @@ documentation; note that it is possible to combine certain constraints
in one constraint string.
You specify the association of an output variable with an assembler operand
-through the @code{%@var{n}} notation, where `n' is a non-negative
+through the @code{%@emph{n}} notation, where @emph{n} is a non-negative
integer. Thus in
@quotation
@@ -29039,7 +29041,7 @@ Asm ("movl %0, %%ebx" & LF & HT &
@end quotation
The Clobber parameter is a static string expression specifying the
-register(s) you are using. Note that register names are `not' prefixed
+register(s) you are using. Note that register names are @emph{not} prefixed
by a percent sign. Also, if more than one register is used then their names
are separated by commas; e.g., @code{"eax, ebx"}
@@ -29104,7 +29106,7 @@ Copyright 2000, 2001, 2002, 2007, 2008 Free Software Foundation, Inc
Everyone is permitted to copy and distribute verbatim copies of this
license document, but changing it is not allowed.
-`Preamble'
+@strong{Preamble}
The purpose of this License is to make a manual, textbook, or other
functional and useful document “free” in the sense of freedom: to
@@ -29127,23 +29129,23 @@ it can be used for any textual work, regardless of subject matter or
whether it is published as a printed book. We recommend this License
principally for works whose purpose is instruction or reference.
-`1. APPLICABILITY AND DEFINITIONS'
+@strong{1. APPLICABILITY AND DEFINITIONS}
This License applies to any manual or other work, in any medium, that
contains a notice placed by the copyright holder saying it can be
distributed under the terms of this License. Such a notice grants a
world-wide, royalty-free license, unlimited in duration, to use that
-work under the conditions stated herein. The `Document', below,
+work under the conditions stated herein. The @strong{Document}, below,
refers to any such manual or work. Any member of the public is a
-licensee, and is addressed as “`you'”. You accept the license if you
+licensee, and is addressed as “@strong{you}”. You accept the license if you
copy, modify or distribute the work in a way requiring permission
under copyright law.
-A “`Modified Version'” of the Document means any work containing the
+A “@strong{Modified Version}” of the Document means any work containing the
Document or a portion of it, either copied verbatim, or with
modifications and/or translated into another language.
-A “`Secondary Section'” is a named appendix or a front-matter section of
+A “@strong{Secondary Section}” is a named appendix or a front-matter section of
the Document that deals exclusively with the relationship of the
publishers or authors of the Document to the Document’s overall subject
(or to related matters) and contains nothing that could fall directly
@@ -29154,7 +29156,7 @@ connection with the subject or with related matters, or of legal,
commercial, philosophical, ethical or political position regarding
them.
-The “`Invariant Sections'” are certain Secondary Sections whose titles
+The “@strong{Invariant Sections}” are certain Secondary Sections whose titles
are designated, as being those of Invariant Sections, in the notice
that says that the Document is released under this License. If a
section does not fit the above definition of Secondary then it is not
@@ -29162,12 +29164,12 @@ allowed to be designated as Invariant. The Document may contain zero
Invariant Sections. If the Document does not identify any Invariant
Sections then there are none.
-The “`Cover Texts'” are certain short passages of text that are listed,
+The “@strong{Cover Texts}” are certain short passages of text that are listed,
as Front-Cover Texts or Back-Cover Texts, in the notice that says that
the Document is released under this License. A Front-Cover Text may
be at most 5 words, and a Back-Cover Text may be at most 25 words.
-A “`Transparent'” copy of the Document means a machine-readable copy,
+A “@strong{Transparent}” copy of the Document means a machine-readable copy,
represented in a format whose specification is available to the
general public, that is suitable for revising the document
straightforwardly with generic text editors or (for images composed of
@@ -29178,7 +29180,7 @@ to text formatters. A copy made in an otherwise Transparent file
format whose markup, or absence of markup, has been arranged to thwart
or discourage subsequent modification by readers is not Transparent.
An image format is not Transparent if used for any substantial amount
-of text. A copy that is not “Transparent” is called `Opaque'.
+of text. A copy that is not “Transparent” is called @strong{Opaque}.
Examples of suitable formats for Transparent copies include plain
ASCII without markup, Texinfo input format, LaTeX input format, SGML
@@ -29191,22 +29193,22 @@ processing tools are not generally available, and the
machine-generated HTML, PostScript or PDF produced by some word
processors for output purposes only.
-The “`Title Page'” means, for a printed book, the title page itself,
+The “@strong{Title Page}” means, for a printed book, the title page itself,
plus such following pages as are needed to hold, legibly, the material
this License requires to appear in the title page. For works in
formats which do not have any title page as such, “Title Page” means
the text near the most prominent appearance of the work’s title,
preceding the beginning of the body of the text.
-The “`publisher'” means any person or entity that distributes
+The “@strong{publisher}” means any person or entity that distributes
copies of the Document to the public.
-A section “`Entitled XYZ'” means a named subunit of the Document whose
+A section “@strong{Entitled XYZ}” means a named subunit of the Document whose
title either is precisely XYZ or contains XYZ in parentheses following
text that translates XYZ in another language. (Here XYZ stands for a
-specific section name mentioned below, such as “`Acknowledgements'”,
-“`Dedications'”, “`Endorsements'”, or “`History'”.)
-To “`Preserve the Title'”
+specific section name mentioned below, such as “@strong{Acknowledgements}”,
+“@strong{Dedications}”, “@strong{Endorsements}”, or “@strong{History}”.)
+To “@strong{Preserve the Title}”
of such a section when you modify the Document means that it remains a
section “Entitled XYZ” according to this definition.
@@ -29217,7 +29219,7 @@ License, but only as regards disclaiming warranties: any other
implication that these Warranty Disclaimers may have is void and has
no effect on the meaning of this License.
-`2. VERBATIM COPYING'
+@strong{2. VERBATIM COPYING}
You may copy and distribute the Document in any medium, either
commercially or noncommercially, provided that this License, the
@@ -29232,7 +29234,7 @@ number of copies you must also follow the conditions in section 3.
You may also lend copies, under the same conditions stated above, and
you may publicly display copies.
-`3. COPYING IN QUANTITY'
+@strong{3. COPYING IN QUANTITY}
If you publish printed copies (or copies in media that commonly have
printed covers) of the Document, numbering more than 100, and the
@@ -29269,7 +29271,7 @@ It is requested, but not required, that you contact the authors of the
Document well before redistributing any large number of copies, to give
them a chance to provide you with an updated version of the Document.
-`4. MODIFICATIONS'
+@strong{4. MODIFICATIONS}
You may copy and distribute a Modified Version of the Document under
the conditions of sections 2 and 3 above, provided that you release
@@ -29386,7 +29388,7 @@ The author(s) and publisher(s) of the Document do not by this License
give permission to use their names for publicity for or to assert or
imply endorsement of any Modified Version.
-`5. COMBINING DOCUMENTS'
+@strong{5. COMBINING DOCUMENTS}
You may combine the Document with other documents released under this
License, under the terms defined in section 4 above for modified
@@ -29410,7 +29412,7 @@ in the various original documents, forming one section Entitled
and any sections Entitled “Dedications”. You must delete all sections
Entitled “Endorsements”.
-`6. COLLECTIONS OF DOCUMENTS'
+@strong{6. COLLECTIONS OF DOCUMENTS}
You may make a collection consisting of the Document and other documents
released under this License, and replace the individual copies of this
@@ -29423,7 +29425,7 @@ it individually under this License, provided you insert a copy of this
License into the extracted document, and follow this License in all
other respects regarding verbatim copying of that document.
-`7. AGGREGATION WITH INDEPENDENT WORKS'
+@strong{7. AGGREGATION WITH INDEPENDENT WORKS}
A compilation of the Document or its derivatives with other separate
and independent documents or works, in or on a volume of a storage or
@@ -29442,7 +29444,7 @@ electronic equivalent of covers if the Document is in electronic form.
Otherwise they must appear on printed covers that bracket the whole
aggregate.
-`8. TRANSLATION'
+@strong{8. TRANSLATION}
Translation is considered a kind of modification, so you may
distribute translations of the Document under the terms of section 4.
@@ -29462,7 +29464,7 @@ If a section in the Document is Entitled “Acknowledgements”,
its Title (section 1) will typically require changing the actual
title.
-`9. TERMINATION'
+@strong{9. TERMINATION}
You may not copy, modify, sublicense, or distribute the Document
except as expressly provided under this License. Any attempt
@@ -29489,7 +29491,7 @@ this License. If your rights have been terminated and not permanently
reinstated, receipt of a copy of some or all of the same material does
not give you any rights to use it.
-`10. FUTURE REVISIONS OF THIS LICENSE'
+@strong{10. FUTURE REVISIONS OF THIS LICENSE}
The Free Software Foundation may publish new, revised versions
of the GNU Free Documentation License from time to time. Such new
@@ -29510,7 +29512,7 @@ License can be used, that proxy’s public statement of acceptance of a
version permanently authorizes you to choose that version for the
Document.
-`11. RELICENSING'
+@strong{11. RELICENSING}
“Massive Multiauthor Collaboration Site” (or “MMC Site”) means any
World Wide Web server that publishes copyrightable works and also
@@ -29539,7 +29541,7 @@ The operator of an MMC Site may republish an MMC contained in the site
under CC-BY-SA on the same site at any time before August 1, 2009,
provided the MMC is eligible for relicensing.
-`ADDENDUM: How to use this License for your documents'
+@strong{ADDENDUM: How to use this License for your documents}
To use this License in a document you have written, include a copy of
the License in the document and put the following copyright and
@@ -29580,8 +29582,8 @@ to permit their use in free software.
@printindex ge
-@anchor{gnat_ugn/gnat_utility_programs switches-related-to-project-files}@w{ }
@anchor{d1}@w{ }
+@anchor{gnat_ugn/gnat_utility_programs switches-related-to-project-files}@w{ }
@c %**end of body
@bye