and the aspect ``Precondition``. Note that the identifiers for
pragmas Pre_Class and Post_Class are Pre'Class and Post'Class (not
Pre_Class and Post_Class), since these pragmas are intended to be
-identical to the corresponding aspects).
+identical to the corresponding aspects.
If the policy is ``CHECK``, then assertions are enabled, i.e.
the corresponding pragma or aspect is activated.
.. code-block:: ada
- pragma Contract_Cases ((CONTRACT_CASE {, CONTRACT_CASE));
+ pragma Contract_Cases (CONTRACT_CASE {, CONTRACT_CASE});
CONTRACT_CASE ::= CASE_GUARD => CONSEQUENCE
implementations. The only difference between pragma ``Interface``
and pragma ``Import`` is that there is special circuitry to allow
both pragmas to appear for the same subprogram entity (normally it
-is illegal to have multiple ``Import`` pragmas. This is useful in
+is illegal to have multiple ``Import`` pragmas). This is useful in
maintaining Ada 83/Ada 95 compatibility and is compatible with other
Ada 83 compilers.
pragma Obsolescent (
[Message =>] static_string_EXPRESSION
- [,[Version =>] Ada_05]]);
+ [,[Version =>] Ada_05]);
pragma Obsolescent (
[Entity =>] NAME
[,[Message =>] static_string_EXPRESSION
- [,[Version =>] Ada_05]] );
+ [,[Version =>] Ada_05]]);
This pragma can occur immediately following a declaration of an entity,
Use this to override the normal naming convention. It is a configuration
pragma, and so has the usual applicability of configuration pragmas
(i.e., it applies to either an entire partition, or to all units in a
-compilation, or to a single unit, depending on how it is used.
+compilation, or to a single unit, depending on how it is used).
``unit_name`` is mapped to ``file_name_literal``. The identifier for
the second argument is required, and indicates whether this is the file
name for the spec or for the body.
The second form of pragma ``Unreferenced`` is used within a context
clause. In this case the arguments must be unit names of units previously
mentioned in ``with`` clauses (similar to the usage of pragma
-``Elaborate_All``. The effect is to suppress warnings about unreferenced
+``Elaborate_All``). The effect is to suppress warnings about unreferenced
units and unreferenced entities within these units.
For the variable case, warnings are never given for unreferenced variables
If active synchronization is required for access to the variables in the
shared passive package, then as described in the Ada Reference Manual, the
package may contain protected objects used for this purpose. In this case
-a lock file (whose name is :file:`___lock` (three underscores)
+a lock file (whose name is :file:`___lock`, with three underscores)
is created in the shared memory directory.
.. index:: ___lock file (for shared passive packages)
*
If a subtype statically matches the first subtype of a given type, then it has
- by default the same ``Value_Size`` as the first subtype. This is a
+ by default the same ``Value_Size`` as the first subtype. (This is a
consequence of RM 13.1(14): "if two subtypes statically match,
then their subtype-specific aspects are the same".)
byte presented, which is the first (low addressed byte) of the two byte
record is called Master, and the second byte is called Slave.
-The left most (most significant bit is called Control for each byte, and
+The left most (most significant) bit is called Control for each byte, and
the remaining 7 bits are called V1, V2, ... V7, where V7 is the rightmost
(least significant) bit.
This package provides the interface to the low level routines used
by the generated code for allocation and freeing storage for the
-default storage pool (analogous to the C routines malloc and free.
+default storage pool (analogous to the C routines malloc and free).
It also provides a reallocation interface analogous to the C routine
realloc. The body of this unit may be modified to provide alternative
allocation mechanisms for the default pool, and in addition, direct
case:
If ``Ada.Wide_Text_IO.Look_Ahead`` reads a character outside the
-normal lower ASCII set (i.e., a character in the range:
+normal lower ASCII set, i.e. a character in the range:
.. code-block:: ada
case:
If ``Ada.Wide_Wide_Text_IO.Look_Ahead`` reads a character outside the
-normal lower ASCII set (i.e., a character in the range:
+normal lower ASCII set, i.e. a character in the range:
.. code-block:: ada
Check syntax and semantics only (no code generation attempted). When the
compiler is invoked by ``gnatmake``, if the switch :switch:`-gnatc` is
only given to the compiler (after :switch:`-cargs` or in package Compiler of
- the project file, ``gnatmake`` will fail because it will not find the
+ the project file), ``gnatmake`` will fail because it will not find the
object file after compilation. If ``gnatmake`` is called with
:switch:`-gnatc` as a builder switch (before :switch:`-cargs` or in package
Builder of the project file) then ``gnatmake`` will not fail because
where ``name`` is the string name of the type (which can have
- single spaces embedded in the name (e.g. long double), ``digs`` is
+ single spaces embedded in the name, e.g. long double), ``digs`` is
the number of digits for the floating-point type, ``float_rep`` is
the float representation (I for IEEE-754-Binary, which is
the only one supported at this time),
:switch:`-gnatv`
The ``v`` stands for verbose.
The effect of this setting is to write long-format error
- messages to :file:`stdout` (the standard output file.
+ messages to :file:`stdout` (the standard output file).
The same program compiled with the
:switch:`-gnatv` switch would generate:
brief format error messages to :file:`stderr` (the standard error
file) as well as the verbose
format message or full listing (which as usual is written to
- :file:`stdout` (the standard output file).
+ :file:`stdout`, the standard output file).
.. index:: -gnatm (gcc)
.. end of switch description (leave this comment to ease automatic parsing for
-.. GNAT Studio
+.. GNAT Studio)
In the above rules, appearing in column one is always permitted, that is,
counts as meeting either a requirement for a required preceding space,
## Each of these csc is put in its own directory.
## Their name are referenced by the directory names.
## They will be compiled into shared library (although this would also work
- ## with static libraries
+ ## with static libraries)
## - The main program (and possibly other packages that do not belong to any
- ## csc is put in the top level directory (where the Makefile is).
+ ## csc) is put in the top level directory (where the Makefile is).
## toplevel_dir __ first_csc (sources) __ lib (will contain the library)
## \\_ second_csc (sources) __ lib (will contain the library)
## \\_ ...
The use of pragma Restrictions allows you to control which features are
permitted in your program. Apart from the obvious point that if you avoid
relatively expensive features like finalization (enforceable by the use
-of pragma Restrictions (No_Finalization), the use of this pragma does not
+of pragma Restrictions (No_Finalization)), the use of this pragma does not
affect the generated code in most cases.
One notable exception to this rule is that the possibility of task abort
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 *tail -f* command to watch redirected output).
If you are generating large volumes of output with ``Text_IO`` and
performance is an important factor, use a designated file instead
:switch:`-k`
Kill :samp:`@{nn}` from exported names
(:ref:`Windows_Calling_Conventions`
- for a discussion about ``Stdcall``-style symbols.
+ for a discussion about ``Stdcall``-style symbols).
.. index:: --help (dlltool)
and the aspect @code{Precondition}. Note that the identifiers for
pragmas Pre_Class and Post_Class are Pre’Class and Post’Class (not
Pre_Class and Post_Class), since these pragmas are intended to be
-identical to the corresponding aspects).
+identical to the corresponding aspects.
If the policy is @code{CHECK}, then assertions are enabled, i.e.
the corresponding pragma or aspect is activated.
Syntax:
@example
-pragma Contract_Cases ((CONTRACT_CASE @{, CONTRACT_CASE));
+pragma Contract_Cases (CONTRACT_CASE @{, CONTRACT_CASE@});
CONTRACT_CASE ::= CASE_GUARD => CONSEQUENCE
implementations. The only difference between pragma @code{Interface}
and pragma @code{Import} is that there is special circuitry to allow
both pragmas to appear for the same subprogram entity (normally it
-is illegal to have multiple @code{Import} pragmas. This is useful in
+is illegal to have multiple @code{Import} pragmas). This is useful in
maintaining Ada 83/Ada 95 compatibility and is compatible with other
Ada 83 compilers.
pragma Obsolescent (
[Message =>] static_string_EXPRESSION
-[,[Version =>] Ada_05]]);
+[,[Version =>] Ada_05]);
pragma Obsolescent (
[Entity =>] NAME
[,[Message =>] static_string_EXPRESSION
-[,[Version =>] Ada_05]] );
+[,[Version =>] Ada_05]]);
@end example
This pragma can occur immediately following a declaration of an entity,
Use this to override the normal naming convention. It is a configuration
pragma, and so has the usual applicability of configuration pragmas
(i.e., it applies to either an entire partition, or to all units in a
-compilation, or to a single unit, depending on how it is used.
+compilation, or to a single unit, depending on how it is used).
@code{unit_name} is mapped to @code{file_name_literal}. The identifier for
the second argument is required, and indicates whether this is the file
name for the spec or for the body.
The second form of pragma @code{Unreferenced} is used within a context
clause. In this case the arguments must be unit names of units previously
mentioned in @code{with} clauses (similar to the usage of pragma
-@code{Elaborate_All}. The effect is to suppress warnings about unreferenced
+@code{Elaborate_All}). The effect is to suppress warnings about unreferenced
units and unreferenced entities within these units.
For the variable case, warnings are never given for unreferenced variables
@item
If a subtype statically matches the first subtype of a given type, then it has
-by default the same @code{Value_Size} as the first subtype. This is a
+by default the same @code{Value_Size} as the first subtype. (This is a
consequence of RM 13.1(14): “if two subtypes statically match,
then their subtype-specific aspects are the same”.)
byte presented, which is the first (low addressed byte) of the two byte
record is called Master, and the second byte is called Slave.
-The left most (most significant bit is called Control for each byte, and
+The left most (most significant) bit is called Control for each byte, and
the remaining 7 bits are called V1, V2, … V7, where V7 is the rightmost
(least significant) bit.
case:
If @code{Ada.Wide_Text_IO.Look_Ahead} reads a character outside the
-normal lower ASCII set (i.e., a character in the range:
+normal lower ASCII set, i.e. a character in the range:
@example
Wide_Character'Val (16#0080#) .. Wide_Character'Val (16#FFFF#)
case:
If @code{Ada.Wide_Wide_Text_IO.Look_Ahead} reads a character outside the
-normal lower ASCII set (i.e., a character in the range:
+normal lower ASCII set, i.e. a character in the range:
@example
Wide_Wide_Character'Val (16#0080#) .. Wide_Wide_Character'Val (16#10FFFF#)
This package provides the interface to the low level routines used
by the generated code for allocation and freeing storage for the
-default storage pool (analogous to the C routines malloc and free.
+default storage pool (analogous to the C routines malloc and free).
It also provides a reallocation interface analogous to the C routine
realloc. The body of this unit may be modified to provide alternative
allocation mechanisms for the default pool, and in addition, direct
If active synchronization is required for access to the variables in the
shared passive package, then as described in the Ada Reference Manual, the
package may contain protected objects used for this purpose. In this case
-a lock file (whose name is @code{___lock} (three underscores)
+a lock file (whose name is @code{___lock}, with three underscores)
is created in the shared memory directory.
@geindex ___lock file (for shared passive packages)
Check syntax and semantics only (no code generation attempted). When the
compiler is invoked by @code{gnatmake}, if the switch @code{-gnatc} is
only given to the compiler (after @code{-cargs} or in package Compiler of
-the project file, @code{gnatmake} will fail because it will not find the
+the project file), @code{gnatmake} will fail because it will not find the
object file after compilation. If @code{gnatmake} is called with
@code{-gnatc} as a builder switch (before @code{-cargs} or in package
Builder of the project file) then @code{gnatmake} will not fail because
@end example
where @code{name} is the string name of the type (which can have
-single spaces embedded in the name (e.g. long double), @code{digs} is
+single spaces embedded in the name, e.g. long double), @code{digs} is
the number of digits for the floating-point type, @code{float_rep} is
the float representation (I for IEEE-754-Binary, which is
the only one supported at this time),
The @code{v} stands for verbose.
The effect of this setting is to write long-format error
-messages to @code{stdout} (the standard output file.
+messages to @code{stdout} (the standard output file).
The same program compiled with the
@code{-gnatv} switch would generate:
brief format error messages to @code{stderr} (the standard error
file) as well as the verbose
format message or full listing (which as usual is written to
-@code{stdout} (the standard output file).
+@code{stdout}, the standard output file).
@end table
@geindex -gnatm (gcc)
@c end of switch description (leave this comment to ease automatic parsing for
-@c GNAT Studio
+@c GNAT Studio)
In the above rules, appearing in column one is always permitted, that is,
counts as meeting either a requirement for a required preceding space,
## Each of these csc is put in its own directory.
## Their name are referenced by the directory names.
## They will be compiled into shared library (although this would also work
-## with static libraries
+## with static libraries)
## - The main program (and possibly other packages that do not belong to any
-## csc is put in the top level directory (where the Makefile is).
+## csc) is put in the top level directory (where the Makefile is).
## toplevel_dir __ first_csc (sources) __ lib (will contain the library)
## \\_ second_csc (sources) __ lib (will contain the library)
## \\_ ...
The use of pragma Restrictions allows you to control which features are
permitted in your program. Apart from the obvious point that if you avoid
relatively expensive features like finalization (enforceable by the use
-of pragma Restrictions (No_Finalization), the use of this pragma does not
+of pragma Restrictions (No_Finalization)), the use of this pragma does not
affect the generated code in most cases.
One notable exception to this rule is that the possibility of task abort
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 @emph{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
Kill @code{@@@emph{nn}} from exported names
(@ref{1d2,,Windows Calling Conventions}
-for a discussion about @code{Stdcall}-style symbols.
+for a discussion about @code{Stdcall}-style symbols).
@end table
@geindex --help (dlltool)
-- pragma Obsolescent (
-- [Message =>] static_string_EXPRESSION
- -- [,[Version =>] Ada_05]]);
+ -- [,[Version =>] Ada_05]);
-- pragma Obsolescent (
-- [Entity =>] NAME
-- [,[Message =>] static_string_EXPRESSION
- -- [,[Version =>] Ada_05]] );
+ -- [,[Version =>] Ada_05]]);
when Pragma_Obsolescent => Obsolescent : declare
Decl : Node_Id;
git://gcc.gnu.org / gcc.git / commitdiff