Mercurial > hg > octave-lyh > gnulib-hg
changeset 6945:aa195d9ecb02
* functions.texi, gnulib-tool.texi, gnulib.texi: Fix some typos.
author | Ralf Wildenhues <Ralf.Wildenhues@gmx.de> |
---|---|
date | Mon, 10 Jul 2006 06:37:33 +0000 |
parents | 823fc50dfbd9 |
children | 440215b69978 |
files | doc/ChangeLog doc/functions.texi doc/gnulib-tool.texi doc/gnulib.texi |
diffstat | 4 files changed, 13 insertions(+), 9 deletions(-) [+] |
line wrap: on
line diff
--- a/doc/ChangeLog +++ b/doc/ChangeLog @@ -1,3 +1,7 @@ +2006-07-10 Ralf Wildenhues <Ralf.Wildenhues@gmx.de> + + * functions.texi, gnulib-tool.texi, gnulib.texi: Fix some typos. + 2006-07-09 Paul Eggert <eggert@cs.ucla.edu> * maintain.texi, make-stds.texi: Sync from
--- a/doc/functions.texi +++ b/doc/functions.texi @@ -237,7 +237,7 @@ fail with @code{EINVAL}, instead of returning a truncated host name. @item getopt -The default behaviour of the glibc implementation of @code{getopt} allows +The default behavior of the glibc implementation of @code{getopt} allows mixing option and non-option arguments on the command line in any order. Other implementations, such as the one in Cygwin, enforce strict POSIX compliance: they require that the option arguments precede the non-option @@ -588,7 +588,7 @@ except that @code{SIG_IGN} for @code{SIGCHLD} has the effect that the children execution times are not accounted in the @code{times} function. On some systems (BSD? SystemV? Linux?), you need to use the @code{sigaction} -flag @code{SA_NOCLDWAIT} in order to obtain this behaviour. +flag @code{SA_NOCLDWAIT} in order to obtain this behavior. @item sigaltstack @code{sigaltstack} doesn't work on HP-UX 11/IA-64 and OpenBSD 3.6/Sparc64. @@ -601,7 +601,7 @@ reinstalling itself as a handler. On BSD systems and glibc systems, on the other hand, when the signal is triggered, the kernel blocks the signal before invoking the handler. This is saner, but POSIX still allows either -behaviour. To avoid this problem, use @code{sigaction} instead of +behavior. To avoid this problem, use @code{sigaction} instead of @code{signal}. @item sigtimedwait
--- a/doc/gnulib-tool.texi +++ b/doc/gnulib-tool.texi @@ -7,7 +7,7 @@ The @command{gnulib-tool} command is the recommended way to import Gnulib modules. It is possible to borrow Gnulib modules in a package without using @command{gnulib-tool}, relying only on the -metainformation stored in the @file{modules/*} files, but with a +meta-information stored in the @file{modules/*} files, but with a growing number of modules this becomes tedious. @command{gnulib-tool} simplifies the management of source files, @file{Makefile.am}s and @file{configure.ac} in packages incorporating Gnulib modules. @@ -106,12 +106,12 @@ Some Gnulib modules depend on other Gnulib modules. @code{gnulib-tool} will automatically add the needed modules as well; you need not list -them explicitly. @code{gnulib-tool} will also memoize which dependent +them explicitly. @code{gnulib-tool} will also memorize which dependent modules it has added, so that when someday a dependency is dropped, the implicitly added module is dropped as well (unless you have explicitly requested that module). -If you want to cut a dependency, i.e. not add a module although one of +If you want to cut a dependency, i.e., not add a module although one of your requested modules depends on it, you may use the option @samp{--avoid=@var{module}} to do so. Multiple uses of this option are possible. Of course, you will then need to implement the same interface
--- a/doc/gnulib.texi +++ b/doc/gnulib.texi @@ -1,5 +1,5 @@ \input texinfo @c -*-texinfo-*- -@comment $Id: gnulib.texi,v 1.23 2006-06-21 17:22:32 jas Exp $ +@comment $Id: gnulib.texi,v 1.24 2006-07-10 06:37:33 rwild Exp $ @comment %**start of header @setfilename gnulib.info @settitle GNU Gnulib @@ -7,7 +7,7 @@ @syncodeindex pg cp @comment %**end of header -@set UPDATED $Date: 2006-06-21 17:22:32 $ +@set UPDATED $Date: 2006-07-10 06:37:33 $ @copying This manual is for GNU Gnulib (updated @value{UPDATED}), @@ -210,7 +210,7 @@ However, we realize that some applications may not want to have the GSS library abort execution in any situation. The GSS library support a hook to let the application regain control and perform its own -cleanups when an out of memory situation has occured. The application +cleanups when an out of memory situation has occurred. The application can define a function (having a @code{void} prototype, i.e., no return value and no parameters) and set the library variable @code{xalloc_fail_func} to that function. The variable should be