for the University of California at Berkeley and are copyrighted by the
Regents of the University of California. They have undergone minor
changes to fit into @theglibc{} and to fit the @w{ISO C} standard,
-but the functional code is Berkeley's.@refill
+but the functional code is Berkeley's.
@item
The Internet-related code (most of the @file{inet} subdirectory) and
@w{ISO C} library features, unless you explicitly request additional
features by defining one or more of the feature macros.
@xref{Invoking GCC,, GNU CC Command Options, gcc, The GNU CC Manual},
-for more information about GCC options.@refill
+for more information about GCC options.
You should define these macros by using @samp{#define} preprocessor
directives at the top of your source code files. These directives
constant value @code{EOF} instead of a real character.
The attributes of any given character can vary between locales.
-@xref{Locales}, for more information on locales.@refill
+@xref{Locales}, for more information on locales.
These functions are declared in the header file @file{ctype.h}.
@pindex ctype.h
@standards{SVID, ctype.h}
@safety{@prelim{}@mtsafe{}@assafe{}@acsafe{}}
This is identical to @code{tolower}, and is provided for compatibility
-with the SVID. @xref{SVID}.@refill
+with the SVID. @xref{SVID}.
@end deftypefun
@deftypefun int _toupper (int @var{c})
We here refer to the standard as @w{ISO C} since this is the more
general standard in respect of ratification.
The header files and library facilities that make up @theglibc{} are
-a superset of those specified by the @w{ISO C} standard.@refill
+a superset of those specified by the @w{ISO C} standard.
@pindex gcc
If you are concerned about strict adherence to the @w{ISO C} standard, you
POSIX standards are aimed at providing lower-level support for a
particular kind of operating system environment, rather than general
programming language support which can run in many diverse operating
-system environments.@refill
+system environments.
@Theglibc{} implements all of the functions specified in
@cite{ISO/IEC 9945-1:1996, the POSIX System Application Program
For more information about the use of header files and @samp{#include}
directives, @pxref{Header Files,,, cpp.info, The GNU C Preprocessor
-Manual}.@refill
+Manual}.
@Theglibc{} provides several header files, each of which contains
the type and macro definitions and variable and function declarations
In @theglibc{}, @code{va_end} does nothing, and you need not ever
use it except for reasons of portability.
-@refill
+
@end deftypefn
Sometimes it is necessary to parse the list of parameters more than once
modules that define functions in the library, and @code{aux} for
auxiliary modules containing things like data definitions. But the
values of @code{routines} and @code{aux} are just concatenated, so there
-really is no practical difference.@refill
+really is no practical difference.
@item tests
The names of test programs for this section of the library. These
The names of ``other'' programs associated with this section of the
library. These are programs which are not tests per se, but are other
small programs included with the library. They are built by
-@w{@samp{make others}}.@refill
+@w{@samp{make others}}.
@item install-lib
@itemx install-data
installed in the directory specified by @samp{datadir} in
@file{configparms} or @file{Makeconfig}. Files listed in @code{install}
are installed in the directory specified by @samp{bindir} in
-@file{configparms} or @file{Makeconfig}.@refill
+@file{configparms} or @file{Makeconfig}.
@item distribute
Other files from this subdirectory which should be put into a
appended to the list, appearing after the subdirectory containing the
@file{Implies} file. Lines in an @file{Implies} file that begin with a
@samp{#} character are ignored as comments. For example,
-@file{unix/bsd/Implies} contains:@refill
+@file{unix/bsd/Implies} contains:
@smallexample
# BSD has Internet-related things.
unix/inet
@file{sysdeps/generic} and write your new implementation in the
appropriate system-specific subdirectory. Note that if a file is to be
system-dependent, it @strong{must not} appear in one of the main source
-directories.@refill
+directories.
There are a few special files that may exist in each subdirectory of
@file{sysdeps}:
@samp{sysdep-routines}, to specify extra modules to be included in the
library. You should use @samp{sysdep-routines} rather than adding
modules to @samp{routines} because the latter is used in determining
-what to distribute for each subdirectory of the main source tree.@refill
+what to distribute for each subdirectory of the main source tree.
Each makefile in a subdirectory in the ordered list of subdirectories to
be searched is included in order. Since several system-dependent
of @file{sysdeps} implements. For example,
@file{sysdeps/unix/inet/Subdirs} contains @file{inet}; the @file{inet}
directory contains various network-oriented operations which only make
-sense to put in the library on systems that support the Internet.@refill
+sense to put in the library on systems that support the Internet.
@item configure
finish defining them for the particular machine and operating system
variant. See @file{sysdeps/unix/sysdep.h} and the machine-specific
@file{sysdep.h} implementations to see what these macros are and what
-they should do.@refill
+they should do.
The system-specific makefile for the @file{unix} directory
(@file{sysdeps/unix/Makefile}) gives rules to generate several files
fails. If the file cannot be opened, it prints an error message and
jumps out to the command level of your program using @code{longjmp}.
Let's change @code{open2} (@pxref{Alloca Example}) to use this
-subroutine:@refill
+subroutine:
@smallexample
int
established that return point. Returning from @code{setjmp} by means of
@code{longjmp} returns the @var{value} argument that was passed to
@code{longjmp}, rather than @code{0}. (But if @var{value} is given as
-@code{0}, @code{setjmp} returns @code{1}).@refill
+@code{0}, @code{setjmp} returns @code{1}).
@end deftypefun
There are a lot of obscure but important restrictions on the use of
The characters are written onto the end of the current object.
To get at them, you must finish the object with @code{obstack_finish}
-(@pxref{Growing Objects}).@refill
+(@pxref{Growing Objects}).
@end deftypefun
@node Variable Arguments Output
@c inconsistent state in case of cancellation.
The @code{obstack_vprintf} function is the equivalent of
@code{obstack_printf} with the variable argument list specified directly
-as for @code{vprintf}.@refill
+as for @code{vprintf}.
@end deftypefun
Here's an example showing how you might use @code{vfprintf}. This is a
This is like @code{strstr}, but @var{needle} and @var{haystack} are byte
arrays rather than strings. @var{needle-len} is the
length of @var{needle} and @var{haystack-len} is the length of
-@var{haystack}.@refill
+@var{haystack}.
This function is a GNU extension.
@end deftypefun