adaint.c, [...]: Fix comment typos.
* adaint.c, init.c, tracebak.c: Fix comment typos. * gnat-style.texi, gnat_rm.texi, gnat_ugn.texi: Fix typos. From-SVN: r97950
This commit is contained in:
parent
c5d34bb2d6
commit
bde8313852
|
@ -1,3 +1,8 @@
|
|||
2005-04-10 Kazu Hirata <kazu@cs.umass.edu>
|
||||
|
||||
* adaint.c, init.c, tracebak.c: Fix comment typos.
|
||||
* gnat-style.texi, gnat_rm.texi, gnat_ugn.texi: Fix typos.
|
||||
|
||||
2005-04-07 Laurent GUERBY <laurent@guerby.net>
|
||||
John David Anglin <dave.anglin@nrc-cnrc.gc.ca>
|
||||
|
||||
|
|
|
@ -1308,7 +1308,7 @@ __gnat_set_env_value (char *name, char *value)
|
|||
*next = 0;
|
||||
ile_array[i].len = strlen (curr);
|
||||
|
||||
/* Code 2 from lnmdef.h means its a string. */
|
||||
/* Code 2 from lnmdef.h means it's a string. */
|
||||
ile_array[i].code = 2;
|
||||
ile_array[i].adr = curr;
|
||||
|
||||
|
@ -2204,7 +2204,7 @@ __gnat_to_canonical_dir_spec (char *dirspec, int prefixflag)
|
|||
}
|
||||
|
||||
/* Translate a VMS syntax file specification into Unix syntax.
|
||||
If no indicators of VMS syntax found, check if its an uppercase
|
||||
If no indicators of VMS syntax found, check if it's an uppercase
|
||||
alphanumeric_ name and if so try it out as an environment
|
||||
variable (logical name). If all else fails return the
|
||||
input string. */
|
||||
|
|
|
@ -332,7 +332,7 @@ sufficient, as comments.
|
|||
@node Declarations and Types, Expressions and Names, Lexical Elements,Top
|
||||
@section Declarations and Types
|
||||
@c -------------------------------------------------------------------------
|
||||
@cindex Declarationa and Types
|
||||
@cindex Declarations and Types
|
||||
|
||||
@itemize @bullet
|
||||
@item
|
||||
|
|
|
@ -521,7 +521,7 @@ of project files.
|
|||
@ref{Obsolescent Features} documents implementation dependent features,
|
||||
including pragmas and attributes, which are considered obsolescent, since
|
||||
there are other preferred ways of achieving the same results. These
|
||||
obsolescent forms are retained for backwards compatibilty.
|
||||
obsolescent forms are retained for backwards compatibility.
|
||||
|
||||
@end itemize
|
||||
|
||||
|
@ -12939,7 +12939,7 @@ example see the body of @code{GNAT.Tables}).
|
|||
@node System.Partition_Interface (s-parint.ads)
|
||||
@section @code{System.Partition_Interface} (@file{s-parint.ads})
|
||||
@cindex @code{System.Partition_Interface} (@file{s-parint.ads})
|
||||
@cindex Partition intefacing functions
|
||||
@cindex Partition interfacing functions
|
||||
|
||||
@noindent
|
||||
This package provides facilities for partition interfacing. It
|
||||
|
@ -14603,7 +14603,7 @@ of the @command{gnatls} utility to be used to retrieve information about the
|
|||
predefined path; e.g., @code{"gnatls"}, @code{"powerpc-wrs-vxworks-gnatls"}.
|
||||
|
||||
@item VCS_Kind
|
||||
This is a simple atribute. Is value is a string used to specify the
|
||||
This is a simple attribute. Is value is a string used to specify the
|
||||
Version Control System (VCS) to be used for this project, e.g CVS, RCS
|
||||
ClearCase or Perforce.
|
||||
|
||||
|
|
|
@ -2962,7 +2962,7 @@ in section B.3 of the Ada 95 Reference Manual.
|
|||
|
||||
@findex C varargs function
|
||||
@cindex Intefacing to C varargs function
|
||||
@cindex varargs function intefacs
|
||||
@cindex varargs function interfaces
|
||||
@item C varargs function
|
||||
In C, @code{varargs} allows a function to take a variable number of
|
||||
arguments. There is no direct equivalent in this to Ada. One
|
||||
|
@ -4721,7 +4721,7 @@ such warnings are not generated.
|
|||
|
||||
In addition to the above cases, warnings are also generated for
|
||||
GNAT features that have been provided in past versions but which
|
||||
have been superceded (typically by features in the new Ada standard).
|
||||
have been superseded (typically by features in the new Ada standard).
|
||||
For example, @code{pragma Ravenscar} will be flagged since its
|
||||
function is replaced by @code{pragma Profile(Ravenscar)}.
|
||||
|
||||
|
@ -9295,7 +9295,7 @@ the compiler optimizer can "know" that the value @code{Int1V.all} is constant
|
|||
for all iterations of the loop and avoid the extra memory reference
|
||||
required to dereference it each time through the loop.
|
||||
|
||||
This kind of optimziation, called strict aliasing analysis, is
|
||||
This kind of optimization, called strict aliasing analysis, is
|
||||
triggered by specifying an optimization level of @option{-O2} or
|
||||
higher and allows @code{GNAT} to generate more efficient code
|
||||
when access values are involved.
|
||||
|
@ -12583,7 +12583,7 @@ Additionally, you may define the library-related attributes
|
|||
|
||||
The @code{Library_Name} attribute has a string value. There is no restriction
|
||||
on the name of a library. It is the responsability of the developer to
|
||||
choose a name that will be accepted by the platform. It is recommanded to
|
||||
choose a name that will be accepted by the platform. It is recommended to
|
||||
choose names that could be Ada identifiers; such names are almost guaranteed
|
||||
to be acceptable on all platforms.
|
||||
|
||||
|
@ -15453,7 +15453,7 @@ for this subword
|
|||
|
||||
@item
|
||||
if the whole name does not contain any ``_'' inside, and if for this name
|
||||
the dictionaty contains two entries - one of the form @var{identifier},
|
||||
the dictionary contains two entries - one of the form @var{identifier},
|
||||
and another - of the form *@var{simple_identifier}*, then the first one
|
||||
is applied to define the casing of this name
|
||||
|
||||
|
@ -16000,7 +16000,7 @@ an explicit list of files.
|
|||
@cindex @option{^-v^/VERBOSE^} (@code{gnatmetric})
|
||||
Verbose mode;
|
||||
@command{gnatmetric} generates version information and then
|
||||
a trace of sources being procesed.
|
||||
a trace of sources being processed.
|
||||
|
||||
@item ^-dv^/DEBUG_OUTPUT^
|
||||
@cindex @option{^-dv^/DEBUG_OUTPUT^} (@code{gnatmetric})
|
||||
|
|
|
@ -1318,7 +1318,7 @@ long __gnat_error_handler (int *, void *);
|
|||
still need to be handled by such handlers, however, in which case
|
||||
__gnat_error_handler needs to return SS$_RESIGNAL. Consider for
|
||||
instance the use of a third party library compiled with DECAda and
|
||||
performing it's own exception handling internally.
|
||||
performing its own exception handling internally.
|
||||
|
||||
To allow some user-level flexibility, which conditions should be
|
||||
resignaled is controlled by a predicate function, provided with the
|
||||
|
|
|
@ -212,7 +212,7 @@ struct layout
|
|||
function is located in it's caller's frame, and the save operation only
|
||||
takes place if the function performs a call.
|
||||
|
||||
To have __gnat_backtrace retrieve it's own return address, we then
|
||||
To have __gnat_backtrace retrieve its own return address, we then
|
||||
define ... */
|
||||
|
||||
#define FORCE_CALL
|
||||
|
|
Loading…
Reference in New Issue