* manual/arith.texi: Avoid @strong{Note:}.

* manual/creature.texi: Likewise.
	* manual/filesys.texi: Likewise.
	* manual/math.texi: Likewise.
	* manual/memory.texi: Likewise.
	* manual/resource.texi: Likewise.
	* manual/syslog.texi: Likewise.
	* manual/time.texi: Likewise.
This commit is contained in:
Ulrich Drepper 2008-08-02 16:30:28 +00:00
parent 3501542f94
commit 48b22986cc
10 changed files with 24 additions and 12 deletions

View File

@ -1,5 +1,14 @@
2008-08-02 Ulrich Drepper <drepper@redhat.com>
* manual/arith.texi: Avoid @strong{Note:}.
* manual/creature.texi: Likewise.
* manual/filesys.texi: Likewise.
* manual/math.texi: Likewise.
* manual/memory.texi: Likewise.
* manual/resource.texi: Likewise.
* manual/syslog.texi: Likewise.
* manual/time.texi: Likewise.
* sysdeps/posix/clock_getres.c (hp_timing_getres): Remove inline
to prevent warning.

5
NEWS
View File

@ -1,4 +1,4 @@
GNU C Library NEWS -- history of user-visible changes. 2008-8-1
GNU C Library NEWS -- history of user-visible changes. 2008-8-2
Copyright (C) 1992-2007, 2008 Free Software Foundation, Inc.
See the end for copying conditions.
@ -30,6 +30,9 @@ Version 2.9
* Many functions, exported and internal, now atomically set the close-on-exec
flag when run on a sufficiently new kernel. Implemented by Ulrich Drepper.
* Sorting rules for some Indian languages (Kannada, Gurumukhi, Telugu)
Implemented by Pravin Satpute.
Version 2.8

View File

@ -418,7 +418,7 @@ This function returns @code{-1} if @var{x} represents negative infinity,
This function returns a nonzero value if @var{x} is a ``not a number''
value, and zero otherwise.
@strong{Note:} The @code{isnan} macro defined by @w{ISO C99} overrides
@strong{NB:} The @code{isnan} macro defined by @w{ISO C99} overrides
the BSD function. This is normally not a problem, because the two
routines behave identically. However, if you really need to get the BSD
function for some reason, you can write
@ -968,7 +968,7 @@ decide whether traps will occur for each of the exceptions, by setting
bits in the @dfn{control word}. In C, traps result in the program
receiving the @code{SIGFPE} signal; see @ref{Signal Handling}.
@strong{Note:} @w{IEEE 754} says that trap handlers are given details of
@strong{NB:} @w{IEEE 754} says that trap handlers are given details of
the exceptional situation, and can set the result value. C signals do
not provide any mechanism to pass this information back and forth.
Trapping exceptions in C is therefore not very useful.
@ -1721,7 +1721,7 @@ Not all machines provide hardware support for these operations. On
machines that don't, the macros can be very slow. Therefore, you should
not use these functions when NaN is not a concern.
@strong{Note:} There are no macros @code{isequal} or @code{isunequal}.
@strong{NB:} There are no macros @code{isequal} or @code{isunequal}.
They are unnecessary, because the @code{==} and @code{!=} operators do
@emph{not} throw an exception if one or both of the operands are NaN.

View File

@ -217,7 +217,7 @@ sequence of definitions:
Note that if you do this, you must link your program with the BSD
compatibility library by passing the @samp{-lbsd-compat} option to the
compiler or linker. @strong{Note:} If you forget to do this, you may
compiler or linker. @strong{NB:} If you forget to do this, you may
get very strange errors at run time.
@end defvr

View File

@ -3239,7 +3239,7 @@ are replaced with six characters which make the whole string a unique
file name. Usually the template string is something like
@samp{/tmp/@var{prefix}XXXXXX}, and each program uses a unique @var{prefix}.
@strong{Note:} Because @code{mktemp} and @code{mkstemp} modify the
@strong{NB:} Because @code{mktemp} and @code{mkstemp} modify the
template string, you @emph{must not} pass string constants to them.
String constants are normally in read-only storage, so your program
would crash when @code{mktemp} or @code{mkstemp} tried to modify the

View File

@ -1366,7 +1366,7 @@ The prototypes for these functions are in @file{stdlib.h}.
This function returns the next pseudo-random number in the sequence.
The value returned ranges from @code{0} to @code{RAND_MAX}.
@strong{Note:} Temporarily this function was defined to return a
@strong{NB:} Temporarily this function was defined to return a
@code{int32_t} value to indicate that the return value always contains
32 bits even if @code{long int} is wider. The standard demands it
differently. Users must always be aware of the 32-bit limitation,

View File

@ -2326,7 +2326,7 @@ additional block on each iteration. This is impossible with
variable-sized arrays.
@end itemize
@strong{Note:} If you mix use of @code{alloca} and variable-sized arrays
@strong{NB:} If you mix use of @code{alloca} and variable-sized arrays
within one function, exiting a scope in which a variable-sized array was
declared frees all blocks allocated with @code{alloca} during the
execution of that scope.

View File

@ -591,7 +591,7 @@ ready to execute instructions right now. When a process blocks to wait
for something like I/O, its absolute priority is irrelevant.
@cindex runnable process
@strong{Note:} The term ``runnable'' is a synonym for ``ready to run.''
@strong{NB:} The term ``runnable'' is a synonym for ``ready to run.''
When two processes are running or ready to run and both have the same
absolute priority, it's more interesting. In that case, who gets the
@ -663,7 +663,7 @@ privileged process constantly monitors the process' CPU usage and raises
its absolute priority when the process isn't getting its entitled share
and lowers it when the process is exceeding it.
@strong{Note:} The absolute priority is sometimes called the ``static
@strong{NB:} The absolute priority is sometimes called the ``static
priority.'' We don't use that term in this manual because it misses the
most important feature of the absolute priority: its absoluteness.

View File

@ -337,7 +337,7 @@ Locally defined
Results are undefined if the facility code is anything else.
@strong{note:} @code{syslog} recognizes one other facility code: that of
@strong{NB:} @code{syslog} recognizes one other facility code: that of
the kernel. But you can't specify that facility code with these
functions. If you try, it looks the same to @code{syslog} as if you are
requesting the default facility. But you wouldn't want to anyway,

View File

@ -1652,7 +1652,7 @@ The seconds as a decimal number (range @code{0} through @code{60}).
Leading zeroes are permitted but not required.
@strong{Note:} The Unix specification says the upper bound on this value
@strong{NB:} The Unix specification says the upper bound on this value
is @code{61}, a result of a decision to allow double leap seconds. You
will not see the value @code{61} because no minute has more than one
leap second, but the myth persists.