[patch] typos in various docs
Jan van Male
jan.vanmale@fenk.wau.nl
Tue Oct 31 07:14:00 GMT 2000
>On Sat, Oct 28, 2000 at 07:14:01PM +0200, Jan van Male wrote:
>> Hi,
>>
>> Attached is a patch to fix some typos in various documents. They include
>> texinfo documentation, should these go (also) somewhere else? Also two
>> diffs to the web pages are included. These were (apparently) not applied
>> last time, are these pages frozen?
>
>No attachments.
>
>Jeffrey D. Oldham
>oldham@codesourcery.com
oops! here you go:
Index: gcc/contrib/warn_summary
===================================================================
RCS file: /cvs/gcc/egcs/contrib/warn_summary,v
retrieving revision 1.4
diff -u -r1.4 warn_summary
--- warn_summary 1998/10/31 08:30:53 1.4
+++ warn_summary 2000/10/31 15:02:54
@@ -7,7 +7,7 @@
# [-pass|-wpass] [file(s)]
#
# -llf
-# Filter out long lines from the bootstap output before any other
+# Filter out long lines from the bootstrap output before any other
# action. This is useful for systems with broken awks/greps which choke
# on long lines. It is not done by default as it sometimes slows things
# down.
Index: gcc/gcc/c-tree.texi
===================================================================
RCS file: /cvs/gcc/egcs/gcc/c-tree.texi,v
retrieving revision 1.3
diff -u -r1.3 c-tree.texi
--- c-tree.texi 2000/10/23 14:43:33 1.3
+++ c-tree.texi 2000/10/31 15:02:58
@@ -574,7 +574,7 @@
@item UNKNOWN_TYPE
This node is used to represent a type the knowledge of which is
-unsufficiant for a sound processing.
+insufficient for a sound processing.
@item OFFSET_TYPE
This node is used to represent a data member; for example a
@@ -1055,7 +1055,7 @@
@code{OVERLOAD} node in the list of overloaded functions. The macros
@code{OVL_CURRENT} and @code{OVL_NEXT} are actually polymorphic; you can
use them to work with @code{FUNCTION_DECL} nodes as well as with
-overlods. In the case of a @code{FUNCTION_DECL}, @code{OVL_CURRENT}
+overloads. In the case of a @code{FUNCTION_DECL}, @code{OVL_CURRENT}
will always return the function itself, and @code{OVL_NEXT} will always
be @code{NULL_TREE}.
@@ -1076,13 +1076,13 @@
@code{RECORD_TYPE} for @code{C}.
The @code{DECL_REAL_CONTEXT} and @code{DECL_CLASS_CONTEXT} are not
-availble in C; instead you should simply use @code{DECL_CONTEXT}. In C,
+available in C; instead you should simply use @code{DECL_CONTEXT}. In C,
the @code{DECL_CONTEXT} for a function maybe another function. This
representation indicates that the GNU nested function extension is in
use. For details on the semantics of nested functions, see the GCC
Manual. The nested function can refer to local variables in its
containing function. Such references are not explicitly marked in the
-tree sturcture; back-ends must look at the @code{DECL_CONTEXT} for the
+tree structure; back-ends must look at the @code{DECL_CONTEXT} for the
referenced @code{VAR_DECL}. If the @code{DECL_CONTEXT} for the
referenced @code{VAR_DECL} is not the same as the function currently
being processed, and neither @code{DECL_EXTERNAL} nor @code{DECL_STATIC}
@@ -1114,7 +1114,7 @@
@findex DECL_DESTRUCTOR_P
@findex DECL_OVERLOADED_OPERATOR_P
@findex DECL_CONV_FN_P
-@findex DECL_ARTIFIICIAL
+@findex DECL_ARTIFICIAL
@findex DECL_GLOBAL_CTOR_P
@findex DECL_GLOBAL_DTOR_P
@findex GLOBAL_INIT_PRIORITY
@@ -1211,7 +1211,7 @@
@item DECL_COMPLETE_DESTRUCTOR_P
This predicate holds if the function is the destructor for an object a
-complet type.
+complete type.
@item DECL_OVERLOADED_OPERATOR_P
This macro holds if the function is an overloaded operator.
@@ -1641,7 +1641,7 @@
These statements represent the location to which control is transferred
when an exception is thrown. The @code{START_CATCH_TYPE} is the type of
exception that will be caught by this handler; it is equal (by pointer
-equalit) to @code{CATCH_ALL_TYPE} if this handler is for all types.
+equality) to @code{CATCH_ALL_TYPE} if this handler is for all types.
@item SUBOBJECT
@@ -2109,7 +2109,7 @@
@item CALL_EXPR
These nodes are used to represent calls to functions, including
non-static member functions. The first operand is a pointer to the
-function to call; it is always an expresion whose type is a
+function to call; it is always an expression whose type is a
@code{POINTER_TYPE}. The second argument is a @code{TREE_LIST}. The
arguments to the call appear left-to-right in the list. The
@code{TREE_VALUE} of each list node contains the expression
@@ -2165,7 +2165,7 @@
appear within a @code{LOOP_EXPR}.
@item CLEANUP_POINT_EXPR
-These nodes represent full-expressions. The single oeprand is an
+These nodes represent full-expressions. The single operand is an
expression to evaluate. Any destructor calls engendered by the creation
of temporaries during the evaluation of that expression should be
performed immediately after the expression is evaluated.
@@ -2198,7 +2198,7 @@
A @code{SAVE_EXPR} represents an expression (possibly involving
side-effects) that is used more than once. The side-effects should
occur only the first time the expression is evaluated. Subsequent uses
-should juse reuse the computed value. The first operand to the
+should just reuse the computed value. The first operand to the
@code{SAVE_EXPR} is the expression to evaluate. The side-effects should
be executed where the @code{SAVE_EXPR} is first encountered in a
depth-first preorder traversal of the expression tree.
Index: gcc/gcc/extend.texi
===================================================================
RCS file: /cvs/gcc/egcs/gcc/extend.texi,v
retrieving revision 1.65
diff -u -r1.65 extend.texi
--- extend.texi 2000/10/04 18:03:33 1.65
+++ extend.texi 2000/10/31 15:03:00
@@ -853,7 +853,7 @@
@code{0x1.fp3} written in hexadecimal format. In that format the
@code{0x} hex introducer and the @code{p} or @code{P} exponent field are
mandatory. The exponent is a decimal number that indicates the power of
-2 by which the significand part will be multiplied. Thus @code{0x1.f} is
+2 by which the significant part will be multiplied. Thus @code{0x1.f} is
1 15/16, @code{p3} multiplies it by 8, and the value of @code{0x1.fp3}
is the same as @code{1.55e1}.
@@ -2702,7 +2702,7 @@
An @code{asm} instruction without any operands or clobbers (and ``old
style'' @code{asm}) will not be deleted or moved significantly,
-regardless, unless it is unreachable, the same wasy as if you had
+regardless, unless it is unreachable, the same way as if you had
written a @code{volatile} keyword.
Note that even a volatile @code{asm} instruction can be moved in ways
Index: gcc/gcc/gcov.texi
===================================================================
RCS file: /cvs/gcc/egcs/gcc/gcov.texi,v
retrieving revision 1.4
diff -u -r1.4 gcov.texi
--- gcov.texi 1999/11/10 17:17:15 1.4
+++ gcov.texi 2000/10/31 15:03:00
@@ -217,7 +217,7 @@
indicating the number of times the call returned divided by the number
of times the call was executed will be printed. This will usually be
100%, but may be less for functions call @code{exit} or @code{longjmp},
-and thus may not return everytime they are called.
+and thus may not return every time they are called.
The execution counts are cumulative. If the example program were
executed again without removing the @code{.da} file, the count for the
@@ -336,7 +336,7 @@
number is the number of counts in the file, followed by the counts
(stored as 8-byte numbers). Each count corresponds to the number of
times each arc in the program is executed. The counts are cumulative;
-each time the program is executed, it attemps to combine the existing
+each time the program is executed, it attempts to combine the existing
@code{.da} files with the new counts for this invocation of the
program. It ignores the contents of any @code{.da} files whose number of
arcs doesn't correspond to the current program, and merely overwrites
Index: gcc/gcc/rtl.texi
===================================================================
RCS file: /cvs/gcc/egcs/gcc/rtl.texi,v
retrieving revision 1.29
diff -u -r1.29 rtl.texi
--- rtl.texi 2000/09/08 09:56:25 1.29
+++ rtl.texi 2000/10/31 15:03:01
@@ -2210,7 +2210,7 @@
space is given to each address-difference. @var{min} and @var{max}
are set up by branch shortening and hold a label with a minimum and a
maximum address, respectively. @var{flags} indicates the relative
-position of @var{base}, @var{min} and @var{max} to the cointaining insn
+position of @var{base}, @var{min} and @var{max} to the containing insn
and of @var{min} and @var{max} to @var{base}. See rtl.def for details.@refill
@end table
@@ -2915,7 +2915,7 @@
@findex REG_BR_PRED
@item REG_BR_PRED
These notes are found in JUMP insns after delayed branch scheduling
-has taken place. They indicate both the direction and the likelyhood
+has taken place. They indicate both the direction and the likelihood
of the JUMP. The format is a bitmask of ATTR_FLAG_* values.
@findex REG_FRAME_RELATED_EXPR
Index: gcc/gcc/tm.texi
===================================================================
RCS file: /cvs/gcc/egcs/gcc/tm.texi,v
retrieving revision 1.149
diff -u -r1.149 tm.texi
--- tm.texi 2000/10/18 17:51:54 1.149
+++ tm.texi 2000/10/31 15:03:06
@@ -6004,7 +6004,7 @@
@findex ASM_OUTPUT_DEF_FROM_DECLS
@item ASM_OUTPUT_DEF_FROM_DECLS (@var{stream}, @var{decl_of_name},
@var{decl_of_value})
A C statement to output to the stdio stream @var{stream} assembler code
-which defines (equates) the symbol whoes tree node is @var{decl_of_name}
+which defines (equates) the symbol whose tree node is @var{decl_of_name}
to have the value of the tree node @var{decl_of_value}. This macro will
be used in preference to @samp{ASM_OUTPUT_DEF} if it is defined and if
the tree nodes are available.
@@ -6263,7 +6263,7 @@
functions rather than initialization functions.
When @code{ASM_OUTPUT_CONSTRUCTOR} and @code{ASM_OUTPUT_DESTRUCTOR} are
-defined, the initializaiton routine generated for the generated object
+defined, the initialization routine generated for the generated object
file will have static linkage.
@end table
@@ -6477,11 +6477,11 @@
@item ASM_FPRINTF_EXTENSIONS(@var{file}, @var{argptr}, @var{format})
@findex ASM_FPRINTF_EXTENSIONS
-If defiend this macro should expand to a series of @code{case}
+If defined this macro should expand to a series of @code{case}
statements which will be parsed inside the @code{switch} statement of
the @code{asm_fprintf} function. This allows targets to define extra
printf formats which may useful when generating their assembler
-statements. Noet that upper case letters are reserved for future
+statements. Note that upper case letters are reserved for future
generic extensions to asm_fprintf, and so are not available to target
specific code. The output file is given by the parameter @var{file}.
The varargs input pointer is @var{argptr} and the rest of the format
@@ -7852,7 +7852,7 @@
other compilers for the same target. In general, we discourage
definition of target-specific pragmas for GCC.
-If the pragma can be implemented by atttributes then the macro
+If the pragma can be implemented by attributes then the macro
@samp{INSERT_ATTRIBUTES} might be a useful one to define as well.
Preprocessor macros that appear on pragma lines are not expanded. All
Index: gcc/libio/iostream.texi
===================================================================
RCS file: /cvs/gcc/egcs/libio/iostream.texi,v
retrieving revision 1.2
diff -u -r1.2 iostream.texi
--- iostream.texi 1998/05/06 21:08:51 1.2
+++ iostream.texi 2000/10/31 15:03:11
@@ -1907,7 +1907,7 @@
@node Filebuf internals
@section Filebuf internals
-The @code{filebuf} is used a lot, so it is importamt that it be
+The @code{filebuf} is used a lot, so it is important that it be
efficient. It is also supports rather complex semantics.
so let us examine its implementation.
Index: gcc/libstdc++/stl/README
===================================================================
RCS file: /cvs/gcc/egcs/libstdc++/stl/README,v
retrieving revision 1.3
diff -u -r1.3 README
--- README 1998/09/15 13:43:59 1.3
+++ README 2000/10/31 15:03:11
@@ -4,7 +4,7 @@
Note that this is based on a pre-Draft Standard for C++.
Things are likely to change. For example, the header file names
are very likely to change. The Allocator interface will change. Etc, etc.
-CYGNUS MAKES NO COMMITTMENT (yet) TO SUPPORT BACKWARD COMPATIBILITY FOR STL.
+CYGNUS MAKES NO COMMITMENT (yet) TO SUPPORT BACKWARD COMPATIBILITY FOR STL.
For examples of things that should work, look in the ../tests directory.
Index: gcc/texinfo/NEWS
===================================================================
RCS file: /cvs/gcc/egcs/texinfo/NEWS,v
retrieving revision 1.4
diff -u -r1.4 NEWS
--- NEWS 1998/03/24 19:40:24 1.4
+++ NEWS 2000/10/31 15:03:12
@@ -178,7 +178,7 @@
* Cleaner built in documentation, and documentation functions.
Use:
- o `M-x describe-variable' to read a variable's documenation
+ o `M-x describe-variable' to read a variable's documentation
o `M-x describe-key' to find out what a particular keystroke does.
o `M-x describe-function' to read a function's documentation.
o `M-x where-is' to find out what keys invoke a particular function.
@@ -234,7 +234,7 @@
* When scrolling with C-v, C-M-v, or M-v, only "Page Only" scrolling
will happen.
-* Continous scrolling (along with `]' (info-global-next) and `['
+* Continuous scrolling (along with `]' (info-global-next) and `['
(info-global-prev) works better. `]' and `[' accept numeric
arguments, moving that many nodes in that case.
@@ -267,7 +267,7 @@
"Next Only" causes the Next or Prev node to
be selected when you scroll past the bottom
or top of a node. "Continous" moves
- linearly through the files hierchichal
+ linearly through the files hierarchical
structure.
`scroll-step' 0 Controls how scrolling is done
for you when
@@ -318,7 +318,7 @@
* Screen height changes made quite robust.
* Interactive function "set-screen-height" implements user height changes.
* Scrolling on some terminals is faster now.
-* C-l with numeric arguement is fixed.
+* C-l with numeric argument is fixed.
----------------------------------------
This release of Info is version 2.2 beta.
Index: gcc/texinfo/cygnus/texiplus.tex
===================================================================
RCS file: /cvs/gcc/egcs/texinfo/cygnus/texiplus.tex,v
retrieving revision 1.2
diff -u -r1.2 texiplus.tex
--- texiplus.tex 1998/03/24 18:05:30 1.2
+++ texiplus.tex 2000/10/31 15:03:12
@@ -250,7 +250,7 @@
\setbox0=\hbox{\printednodename}%
\ifdim \wd0=0pt%
\def\printednodename{\ignorespaces #1}%
-%%% Uncommment the following line to make the actual chapter or section title
+%%% Uncomment the following line to make the actual chapter or section title
%%% appear inside the square brackets.
%\def\printednodename{#1-title}%
\fi%
Index: gcc/texinfo/doc/macro.texi
===================================================================
RCS file: /cvs/gcc/egcs/texinfo/doc/macro.texi,v
retrieving revision 1.2
diff -u -r1.2 macro.texi
--- macro.texi 1998/03/24 18:05:38 1.2
+++ macro.texi 2000/10/31 15:03:12
@@ -133,7 +133,7 @@
will be seen as a call to a builtin @texinfo{} command. This allows one
to redefine a builtin @texinfo{} command as a macro, and then use that
command within the definition of the macro itself. For example, one
-might wish to make sure that whereever a term was defined with
+might wish to make sure that wherever a term was defined with
@code{@@dfn@{@dots{}@}}, the location of the definition would appear
in the concept index for the manual. Here is a macro which redefines
@code{@@dfn} to do just that:
Index: gcc/texinfo/doc/texinfo.tex
===================================================================
RCS file: /cvs/gcc/egcs/texinfo/doc/texinfo.tex,v
retrieving revision 1.3
diff -u -r1.3 texinfo.tex
--- texinfo.tex 1998/03/24 19:40:41 1.3
+++ texinfo.tex 2000/10/31 15:03:14
@@ -303,7 +303,7 @@
% This loses if there are any *other* active characters besides spaces
% in the argument -- _ ^ +, for example -- since they get expanded.
% Fortunately, Texinfo does not define any such commands. (If it ever
-% does, the catcode of the characters in questionwill have to be changed
+% does, the catcode of the characters in question will have to be changed
% here.) But this means we cannot call \removeactivespaces as part of
% \argremovec{,omment}, since @c uses \parsearg, and thus the argument
% that \parsearg gets might well have any character at all in it.
Index: gcc/texinfo/doc/texinfo.texi
===================================================================
RCS file: /cvs/gcc/egcs/texinfo/doc/texinfo.texi,v
retrieving revision 1.2
diff -u -r1.2 texinfo.texi
--- texinfo.texi 1998/03/24 18:05:41 1.2
+++ texinfo.texi 2000/10/31 15:03:24
@@ -11451,7 +11451,7 @@
commands, by delineating a region with the @code{@@tex} and @code{@@end
tex} commands. (The @code{@@tex} command also causes Info to ignore the
region, like the @code{@@iftex} command.) The sole exception is that
-@code{@@} chracter still introduces a command, so that @code{@@end tex}
+@code{@@} character still introduces a command, so that @code{@@end tex}
can be recognized properly.
@cindex Mathematical expressions
@@ -11986,7 +11986,7 @@
@noindent @TeX{} will produce a @dfn{DVI file} as well as several auxiliary
files containing information for indices, cross references, etc. The
DVI file (for @dfn{DeVice Independent} file) can be printed on virtually
-any printe (see the following sections).
+any printer (see the following sections).
@pindex texindex
The @code{tex} formatting command itself does not sort the indices; it
Index: gcc/texinfo/doc/texinfo.txi
===================================================================
RCS file: /cvs/gcc/egcs/texinfo/doc/texinfo.txi,v
retrieving revision 1.2
diff -u -r1.2 texinfo.txi
--- texinfo.txi 1999/09/04 15:08:53 1.2
+++ texinfo.txi 2000/10/31 15:03:37
@@ -11438,7 +11438,7 @@
commands, by delineating a region with the @code{@@tex} and @code{@@end
tex} commands. (The @code{@@tex} command also causes Info to ignore the
region, like the @code{@@iftex} command.) The sole exception is that
-@code{@@} chracter still introduces a command, so that @code{@@end tex}
+@code{@@} character still introduces a command, so that @code{@@end tex}
can be recognized properly.
@cindex Mathematical expressions
Index: gcc/texinfo/doc/userdoc.texi
===================================================================
RCS file: /cvs/gcc/egcs/texinfo/doc/userdoc.texi,v
retrieving revision 1.2
diff -u -r1.2 userdoc.texi
--- userdoc.texi 1998/03/24 18:05:43 1.2
+++ userdoc.texi 2000/10/31 15:03:39
@@ -147,7 +147,7 @@
move the cursor about the screen. The notation used in this manual to
describe keystrokes is identical to the notation used within the Emacs
manual, and the GNU Readline manual. @xref{Characters, , Character
-Conventions, emacs, the GNU Emacs Manual}, if you are unfamilar with the
+Conventions, emacs, the GNU Emacs Manual}, if you are unfamiliar with the
notation.
The following table lists the basic cursor movement commands in Info.
@@ -485,7 +485,7 @@
The most basic searching command is @samp{s} (@code{search}). The
@samp{s} command prompts you for a string in the echo area, and then
-searches the remainder of the info file for an ocurrence of that string.
+searches the remainder of the info file for an occurrence of that string.
If the string is found, the node containing it is selected, and the
cursor is left positioned at the start of the found string. Subsequent
@samp{s} commands show you the default search string within @samp{[} and
@@ -1227,7 +1227,7 @@
@node Info for Sys Admins
@chapter Info for System Administrators
-This text describes some common ways of setting up an Info heierarchy
+This text describes some common ways of setting up an Info hierarchy
from scratch, and details the various options that are available when
installing Info. This text is designed for the person who is installing
GNU Info on the system; although users may find the information present
@@ -1237,9 +1237,9 @@
@menu
* Setting the INFOPATH:: Where are my Info files kept?
* Editing the DIR node:: What goes in `DIR', and why?
-* Storing Info files:: Alternate formats allow flexibilty in setups.
+* Storing Info files:: Alternate formats allow flexibility in setups.
* Using `localdir':: Building DIR on the fly.
-* Example setups:: Some common ways to origanize Info files.
+* Example setups:: Some common ways to organize Info files.
@end menu
@node Setting the INFOPATH
@@ -1252,7 +1252,7 @@
@node Storing Info files
@section Storing Info files
-Alternate formats allow flexibilty in setups.
+Alternate formats allow flexibility in setups.
@node Using `localdir'
@section Using `localdir'
@@ -1260,7 +1260,7 @@
@node Example setups
@section Example setups
-Some common ways to origanize Info files.
+Some common ways to organize Info files.
@end ifset
@ifset STANDALONE
Index: gcc/texinfo/info/info.texi
===================================================================
RCS file: /cvs/gcc/egcs/texinfo/info/info.texi,v
retrieving revision 1.2
diff -u -r1.2 info.texi
--- info.texi 1998/03/24 18:06:32 1.2
+++ info.texi 2000/10/31 15:03:40
@@ -699,7 +699,7 @@
Usually, the way to create the nodes is with Texinfo @pxref{Top,, Overview of
Texinfo, texinfo, Texinfo: The GNU Documentation Format}); this has the
advantage that you can also make a printed manual from them. However,
-if hyou want to edit an Info file, here is how.
+if you want to edit an Info file, here is how.
The new node can live in an existing documentation file, or in a new
one. It must have a @key{^_} character before it (invisible to the
Index: gcc/texinfo/info/userdoc.texi
===================================================================
RCS file: /cvs/gcc/egcs/texinfo/info/userdoc.texi,v
retrieving revision 1.2
diff -u -r1.2 userdoc.texi
--- userdoc.texi 1998/03/24 18:06:52 1.2
+++ userdoc.texi 2000/10/31 15:03:41
@@ -147,7 +147,7 @@
move the cursor about the screen. The notation used in this manual to
describe keystrokes is identical to the notation used within the Emacs
manual, and the GNU Readline manual. @xref{Characters, , Character
-Conventions, emacs, the GNU Emacs Manual}, if you are unfamilar with the
+Conventions, emacs, the GNU Emacs Manual}, if you are unfamiliar with the
notation.
The following table lists the basic cursor movement commands in Info.
@@ -485,7 +485,7 @@
The most basic searching command is @samp{s} (@code{search}). The
@samp{s} command prompts you for a string in the echo area, and then
-searches the remainder of the info file for an ocurrence of that string.
+searches the remainder of the info file for an occurrence of that string.
If the string is found, the node containing it is selected, and the
cursor is left positioned at the start of the found string. Subsequent
@samp{s} commands show you the default search string within @samp{[} and
@@ -1227,7 +1227,7 @@
@node Info for Sys Admins
@chapter Info for System Administrators
-This text describes some common ways of setting up an Info heierarchy
+This text describes some common ways of setting up an Info hierarchy
from scratch, and details the various options that are available when
installing Info. This text is designed for the person who is installing
GNU Info on the system; although users may find the information present
@@ -1237,9 +1237,9 @@
@menu
* Setting the INFOPATH:: Where are my Info files kept?
* Editing the DIR node:: What goes in `DIR', and why?
-* Storing Info files:: Alternate formats allow flexibilty in setups.
+* Storing Info files:: Alternate formats allow flexibility in setups.
* Using `localdir':: Building DIR on the fly.
-* Example setups:: Some common ways to origanize Info files.
+* Example setups:: Some common ways to organize Info files.
@end menu
@node Setting the INFOPATH
@@ -1252,7 +1252,7 @@
@node Storing Info files
@section Storing Info files
-Alternate formats allow flexibilty in setups.
+Alternate formats allow flexibility in setups.
@node Using `localdir'
@section Using `localdir'
@@ -1260,7 +1260,7 @@
@node Example setups
@section Example setups
-Some common ways to origanize Info files.
+Some common ways to organize Info files.
@end ifset
@ifset STANDALONE
Index: gcc/texinfo/makeinfo/macro.texi
===================================================================
RCS file: /cvs/gcc/egcs/texinfo/makeinfo/macro.texi,v
retrieving revision 1.2
diff -u -r1.2 macro.texi
--- macro.texi 1998/03/24 18:07:52 1.2
+++ macro.texi 2000/10/31 15:03:41
@@ -133,7 +133,7 @@
will be seen as a call to a builtin @texinfo{} command. This allows one
to redefine a builtin @texinfo{} command as a macro, and then use that
command within the definition of the macro itself. For example, one
-might wish to make sure that whereever a term was defined with
+might wish to make sure that wherever a term was defined with
@code{@@dfn@{@dots{}@}}, the location of the definition would appear
in the concept index for the manual. Here is a macro which redefines
@code{@@dfn} to do just that:
Index: gcc/texinfo/makeinfo/makeinfo.texi
===================================================================
RCS file: /cvs/gcc/egcs/texinfo/makeinfo/makeinfo.texi,v
retrieving revision 1.2
diff -u -r1.2 makeinfo.texi
--- makeinfo.texi 1998/03/24 18:07:55 1.2
+++ makeinfo.texi 2000/10/31 15:03:41
@@ -199,7 +199,7 @@
exist.@refill
@item --no-number-footnotes
-Supress automatic footnote numbering. By default, @code{makeinfo}
+Suppress automatic footnote numbering. By default, @code{makeinfo}
numbers each footnote sequentially in a single node, resetting the
current footnote number to 1 at the start of each node.
Index: gcc/texinfo/makeinfo/macros/example.texi
===================================================================
RCS file: /cvs/gcc/egcs/texinfo/makeinfo/macros/example.texi,v
retrieving revision 1.2
diff -u -r1.2 example.texi
--- example.texi 1998/03/24 18:07:59 1.2
+++ example.texi 2000/10/31 15:03:41
@@ -128,7 +128,7 @@
exist.
@item --no-number-footnotes
-Supress automatic footnote numbering. By default, @makeinfo{}
+Suppress automatic footnote numbering. By default, @makeinfo{}
numbers each footnote sequentially in a single node, resetting the
current footnote number to 1 at the start of each node.
Index: gcc/texinfo/makeinfo/macros/resume.texi
===================================================================
RCS file: /cvs/gcc/egcs/texinfo/makeinfo/macros/resume.texi,v
retrieving revision 1.2
diff -u -r1.2 resume.texi
--- resume.texi 1998/03/24 18:08:03 1.2
+++ resume.texi 2000/10/31 15:03:41
@@ -1,5 +1,5 @@
@c
-@c Reusme writing macros. Produce a very specific format.
+@c Resume writing macros. Produce a very specific format.
@c
@c A macro which creates a macro. The resultant macro can be called to
@@ -37,7 +37,7 @@
@end macro
@c A typical entry in a resume has a from-date, a to-date, a location,
-@c a job title, and a longer descrition body.
+@c a job title, and a longer description body.
@macro entry{from-date, to-date, where, what, body}
@paragraphindent 8
Index: gcc/zlib/README
===================================================================
RCS file: /cvs/gcc/egcs/zlib/README,v
retrieving revision 1.1
diff -u -r1.1 README
--- README 1999/05/04 19:30:26 1.1
+++ README 2000/10/31 15:03:42
@@ -65,7 +65,7 @@
http://www.python.org/doc/lib/module-zlib.html
A zlib binding for TCL written by Andreas Kupries <a.kupries@westend.com>
-is availlable at http://www.westend.com/~kupries/doc/trf/man/man.html
+is available at http://www.westend.com/~kupries/doc/trf/man/man.html
An experimental package to read and write files in .zip format,
written on top of zlib by Gilles Vollant <info@winimage.com>, is
@@ -93,7 +93,7 @@
- zlib doesn't work with gcc 2.6.3 on a DEC 3000/300LX under OSF/1 2.1
it works when compiled with cc.
-- on Digital Unix 4.0D (formely OSF/1) on AlphaServer, the cc option -std1
+- on Digital Unix 4.0D (formerly OSF/1) on AlphaServer, the cc option -std1
is necessary to get gzprintf working correctly. This is done by configure.
- zlib doesn't work on HP-UX 9.05 with some versions of /bin/cc. It works
Index: wwwdocs/htdocs/egcs-1.1/features.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/egcs-1.1/features.html,v
retrieving revision 1.12
diff -u -r1.12 features.html
--- features.html 2000/10/15 19:01:33 1.12
+++ features.html 2000/10/31 15:03:42
@@ -51,7 +51,7 @@
performance tuning for Ultra class machines. The SPARC port now
uses the Haifa scheduler.
<li> Alpha port has been tuned for the EV6 processor and has an
- optimized expanstion of memcpy/bzero. The Alpha port now uses
+ optimized expansion of memcpy/bzero. The Alpha port now uses
the Haifa scheduler.
<li> RS6000/PowerPC: EGCS 1.1 includes support for the Power64
architecture and aix4.3 support. The RS6000/PowerPC port now
Index: wwwdocs/htdocs/egcs-1.1/news.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/egcs-1.1/news.html,v
retrieving revision 1.4
diff -u -r1.4 news.html
--- news.html 1999/07/29 04:27:45 1.4
+++ news.html 2000/10/31 15:03:42
@@ -65,7 +65,7 @@
(major missing feature is trigraphs).
Memory footprint for the compiler has been significantly reduced for certain
-pathalogical cases.
+pathological cases.
Build time improvements for targets which support lots of sched parameters
(alpha and mips primarily).
More information about the Gcc-patches
mailing list