diff options
author | Ulrich Drepper <drepper@redhat.com> | 1997-05-25 01:12:55 +0000 |
---|---|---|
committer | Ulrich Drepper <drepper@redhat.com> | 1997-05-25 01:12:55 +0000 |
commit | cf29ffbef960c4c454d94919c6f27206f77961ff (patch) | |
tree | 564fc08211b378cac2f8d830d497898d02893ad1 /manual/stdio.texi | |
parent | a133e7a4d2fd162f67b1fa6eb34b490a710459e5 (diff) | |
download | glibc-cf29ffbef960c4c454d94919c6f27206f77961ff.tar glibc-cf29ffbef960c4c454d94919c6f27206f77961ff.tar.gz glibc-cf29ffbef960c4c454d94919c6f27206f77961ff.tar.bz2 glibc-cf29ffbef960c4c454d94919c6f27206f77961ff.zip |
Update.cvs/libc-ud-970524
1997-05-25 03:00 Ulrich Drepper <drepper@cygnus.com>
* elf/dynamic-link.h (_dl_verbose): New variable, declare.
* elf/rtld.c (_dl_verbose): New variable, define.
(dl_main): Define _dl-verbose based on DL_WARN environment variable.
* sysdeps/i386/dl-machine.h (elf_machine_rel): Print warning about
changed size in copy relocation only if symbol in shared object
is larger or _dl_verbose is nonzero.
* sysdeps/m68k/dl-machine.h (elf_machine_rel): Likewise.
* sysdeps/powerpc/dl-machine.h (elf_machine_rel): Likewise.
* sysdeps/sparc/dl-machine.h (elf_machine_rel): Likewise.
* nis/nss_nis/nis-ethers.c: Don't use relative include paths, use
<...>.
* nis/nss_nis/nis-grp.c: Likewise.
* nis/nss_nis/nis-hosts.c: Likewise.
* nis/nss_nis/nis-network.c: Likewise.
* nis/nss_nis/nis-proto.c: Likewise.
* nis/nss_nis/nis-pwd.c: Likewise.
* nis/nss_nis/nis-rpc.c: Likewise.
* nis/nss_nis/nis-spwd.c: Likewise.
* sysdeps/unix/sysv/sysd-stdio.c: Likewise.
* wcsmbs/wcscoll.c: Likewise.
* wcsmbs/wcstod.c: Likewise.
* wcsmbs/wcstof.c: Likewise.
* wcsmbs/wcstol.c: Likewise.
* wcsmbs/wcstold.c: Likewise.
* wcsmbs/wcsxfrm.c: Likewise.
Reported by Zack Weinberg <zack@rabi.phys.columbia.edu>.
* time/strftime.c: Implement # flag which changes case of output for
%a, %b, %B, %p, and %Z format.
When printing numbers, the given field width is always respected.
This means that padding happens only up to the given width.
Proposed by Stephen Gildea <gildea@intouchsys.com>.
1997-05-25 00:44 Ulrich Drepper <drepper@cygnus.com>
* sysdeps/i386/fpu/__math.h (logb): Fix thinko, reverse output
values.
Reported by Andreas Jaeger <aj@arthur.rhein-neckar.de>.
1997-05-24 21:03 Philip Blundell <pjb27@cam.ac.uk>
* db/btree/bt_open.c (__bt_open): Only try to use st_blksize (from
struct stat) if it exists for this port.
1997-05-24 20:34 Philip Blundell <pjb27@cam.ac.uk>
* sysdeps/standalone/arm/errnos.h: Add EPERM.
1997-05-23 16:28 Philip Blundell <phil@kings-cross.london.uk.eu.org>
* linewrap.h: New file, needed to compile argp without libio.
1997-05-24 11:59 Andreas Jaeger <aj@arthur.rhein-neckar.de>
* manual/stdio.texi (Formatted Messages): Corrected some typos.
1997-05-24 11:58 Philip Blundell <pjb27@cam.ac.uk>
* sysdeps/stub/start.c: Fix typo.
Diffstat (limited to 'manual/stdio.texi')
-rw-r--r-- | manual/stdio.texi | 28 |
1 files changed, 16 insertions, 12 deletions
diff --git a/manual/stdio.texi b/manual/stdio.texi index 3d6a6c1f2f..085a1c95a8 100644 --- a/manual/stdio.texi +++ b/manual/stdio.texi @@ -3825,7 +3825,7 @@ wait until the rest of the manual is more done and polished. On systems which are based on System V messages of programs (especially the system tools) are printed in a strict form using the @code{fmtmsg} function. The uniformity sometimes helps the user to interpret messages -and the strictness tests of the @code{fmtmsg} function ensures that the +and the strictness tests of the @code{fmtmsg} function ensure that the programmer follows some minimal requirements. @menu @@ -3839,7 +3839,7 @@ programmer follows some minimal requirements. @subsection Printing Formatted Messages Messages can be printed to standard error and/or to the console. To -select the destination the programmer can use the following to values, +select the destination the programmer can use the following two values, bitwise OR combined if wanted, for the @var{classification} parameter of @code{fmtmsg}: @@ -3850,7 +3850,7 @@ Display the message in standard error. Display the message on the system console. @end vtable -The errorneous piece of the system can be signal by exactly one of the +The errorneous piece of the system can be signalled by exactly one of the following values which also is bitwise ORed with the @var{classification} parameter to @code{fmtmsg}: @@ -3900,7 +3900,7 @@ reference to the online documentation where more information can be found. It should contain the @var{label} value and a unique identification number. -Each of the parameters can be of a special value which means this value +Each of the parameters can be a special value which means this value is to be omitted. The symbolic names for these values are: @vtable @code @@ -3919,7 +3919,7 @@ Ignore @var{action} parameter. Ignore @var{tag} parameter. @end vtable -There is another way certain fields can be omitted from the output the +There is another way certain fields can be omitted from the output to standard error. This is described below in the description of environment variables influencing the behaviour. @@ -3961,10 +3961,10 @@ ignored. This function is specified in the X/Open Portability Guide. It is also available on all system derived from System V. -The function return the value @code{MM_OK} if no error occurred. If +The function returns the value @code{MM_OK} if no error occurred. If only the printing to standard error failed, it returns @code{MM_NOMSG}. If printing to the console fails, it returns @code{MM_NOCON}. If -nothing is printed @code{MM_NOTOK} is returned. Among situation where +nothing is printed @code{MM_NOTOK} is returned. Among situations where all outputs fail this last value is also returned if a parameter value is incorrect. @end deftypefun @@ -3974,7 +3974,7 @@ There are two environment variables which influence the behaviour of output actually happening on standard error (@emph{not} the console output). Each of the five fields can explicitely be enabled. To do this the user has to put the @code{MSGVERB} variable with a format like -following in the environment before calling the @code{fmtmsg} function +the following in the environment before calling the @code{fmtmsg} function the first time: @smallexample @@ -3990,7 +3990,7 @@ The second environment variable which influences the behaviour of @code{fmtmsg} is @code{SEV_LEVEL}. This variable and the change in the behaviour of @code{fmtmsg} is not specified in the X/Open Portability Guide. It is available in System V systems, though. It can be used to -introduce no severity levels. By default, only the five severity levels +introduce new severity levels. By default, only the five severity levels described above are available. Any other numeric value would make @code{fmtmsg} print nothing. @@ -4026,7 +4026,7 @@ There is another possibility to introduce severity classes beside using the environment variable @code{SEV_LEVEL}. This simplifies the task of introducing new classes in a running program. One could use the @code{setenv} or @code{putenv} function to set the environment variable, -but this toilsome. +but this is toilsome. @deftypefun int addseverity (int @var{severity}, const char *@var{string}) This function allows to introduce new severity classes which can be @@ -4039,13 +4039,17 @@ value. If @var{string} is @code{NULL} the severity class with the numeric value according to @var{severity} is removed. +It is not possible to overwrite or remove one of the default severity +classes. All calls to @code{addseverity} with @var{severity} set to one +of the values for the default classes will fail. + The return value is @code{MM_OK} if the task was successfully performed. If the return value is @code{MM_NOTOK} something went wrong. This could mean that no more memory is available or a class is not available when it has to be removed. This function is not specified in the X/Open Portability Guide although -the @code{fmtsmg} is. It is available on System V systems. +the @code{fmtsmg} function is. It is available on System V systems. @end deftypefun @@ -4120,7 +4124,7 @@ TO FIX: action @noindent I.e., the output produced by the @var{text} and the @var{tag} parameters -to @code{fmtmsg} vanished. Please also note the now there is no colon +to @code{fmtmsg} vanished. Please also note that now there is no colon after the @code{NOTE} and @code{NOTE2} strings in the output. This is not necessary since there is no more output on this line since the text is missing. |