Mercurial > gnulib
changeset 30544:de01c7cf6d30
Fix typos in manual.
* doc/manywarnings.texi, doc/gnulib-intro.texi: Fix typos.
Signed-off-by: Ralf Wildenhues <Ralf.Wildenhues@gmx.de>
| author | Ralf Wildenhues <Ralf.Wildenhues@gmx.de> |
|---|---|
| date | Sun, 07 Dec 2008 12:01:33 +0100 |
| parents | a5cf1b61376c |
| children | f49cbec7fee3 |
| files | ChangeLog doc/gnulib-intro.texi doc/manywarnings.texi |
| diffstat | 3 files changed, 8 insertions(+), 4 deletions(-) [+] |
line wrap: on
line diff
--- a/ChangeLog Sat Dec 06 16:50:32 2008 +0100 +++ b/ChangeLog Sun Dec 07 12:01:33 2008 +0100 @@ -1,3 +1,7 @@ +2008-12-07 Ralf Wildenhues <Ralf.Wildenhues@gmx.de> + + * doc/manywarnings.texi, doc/gnulib-intro.texi: Fix typos. + 2008-12-06 Bruno Haible <bruno@clisp.org> * lib/c-stack.h (c_stack_action): Clarify possible side effects.
--- a/doc/gnulib-intro.texi Sat Dec 06 16:50:32 2008 +0100 +++ b/doc/gnulib-intro.texi Sun Dec 07 12:01:33 2008 +0100 @@ -16,7 +16,7 @@ @item Security: Gnulib provides functions that are immune against vulnerabilities -that plagues the uses of the corresponding commonplace functions. For +that plague the uses of the corresponding commonplace functions. For example, @code{asprintf}, @code{canonicalize_file_name} are not affected by buffer sizing problems that affect @code{sprintf}, @code{realpath}. @code{openat} does not have the race conditions that @code{open} has. Etc.
--- a/doc/manywarnings.texi Sat Dec 06 16:50:32 2008 +0100 +++ b/doc/manywarnings.texi Sun Dec 07 12:01:33 2008 +0100 @@ -3,7 +3,7 @@ The @code{manywarnings} module allows you to enable as many GCC warnings as possible for your package. The purpose is to protect against introducing new -code that triggers warning that weren't already triggered by the existing code +code that triggers warnings that weren't already triggered by the existing code base. An example use of the module is as follows: @@ -25,11 +25,11 @@ @end smallexample This module is meant to be used by developers who are not very experienced -regarding the various GCC warning option. In the beginning you will set the +regarding the various GCC warning options. In the beginning you will set the list of undesired warnings (@samp{nw} in the example above) to empty, and compile the package with all possible warnings enabled. The GCC option @code{-fdiagnostics-show-option}, available in GCC 4.1 or newer, helps -understanding which warnings is originated from which option. Then you will +understanding which warnings originated from which option. Then you will go through the list of warnings. You will likely deactivate warnings that occur often and don't point to mistakes in the code, by adding them to the @samp{nw} variable, then reconfiguring and recompiling. When warnings point