+2017-05-18 Rical Jasan <ricaljasan@pacific.net>
+
+ * manual/conf.texi: Convert @tables of annotated @items to
+ @vtables.
+ * manual/lang.texi: Likewise.
+ * manual/pattern.texi: Likewise.
+ * manual/resource.texi: Likewise.
+ * manual/socket.texi: Likewise.
+
2017-05-18 Rical Jasan <ricaljasan@pacific.net>
* manual/crypt.texi: Move a comment out of an @*x list.
safely push to these limits without checking whether the particular
system you are using can go that far.
-@table @code
+@vtable @code
@comment limits.h
@comment POSIX.1
@item _POSIX_AIO_LISTIO_MAX
The value of this macro is the most restrictive limit permitted by POSIX
for the numbers used in the @samp{\@{@var{min},@var{max}\@}} construct
in a regular expression. Its value is @code{255}.
-@end table
+@end vtable
@node Limits for Files
@section Limits on File System Capacity
have these strict limitations. The actual limit should be requested if
necessary.
-@table @code
+@vtable @code
@comment limits.h
@comment POSIX.1
@item _POSIX_LINK_MAX
@comment POSIX.1
@item POSIX_REC_XFER_ALIGN
Recommended file transfer buffer alignment.
-@end table
+@end vtable
@node Pathconf
@section Using @code{pathconf}
argument to @code{pathconf} and @code{fpathconf}. The values are all
integer constants.
-@table @code
+@vtable @code
@comment unistd.h
@comment POSIX.1
@item _PC_LINK_MAX
@comment POSIX.1
@item _PC_REC_XFER_ALIGN
Inquire about the value of @code{POSIX_REC_XFER_ALIGN}.
-@end table
+@end vtable
@strong{Portability Note:} On some systems, @theglibc{} does not
enforce @code{_PC_NAME_MAX} or @code{_PC_PATH_MAX} limits.
@node Utility Minimums
@section Minimum Values for Utility Limits
-@table @code
+@vtable @code
@comment limits.h
@comment POSIX.2
@item _POSIX2_BC_BASE_MAX
category @samp{order} keyword in a locale definition. Its value is
@code{2}. @Theglibc{} does not presently support locale
definitions.
-@end table
+@end vtable
@node String Parameters
@section String-Valued Parameters
Currently there is just one parameter you can read with @code{confstr}:
-@table @code
+@vtable @code
@comment unistd.h
@comment POSIX.2
@item _CS_PATH
The returned string specifies which additional flags must be given to
the lint tool if a source is compiled using the
@code{_LARGEFILE64_SOURCE} feature select macro; @pxref{Feature Test Macros}.
-@end table
+@end vtable
The way to use @code{confstr} without any arbitrary limit on string size
is to call it twice: first call it to get the length, allocate the
preprocessor directives, whereas @code{sizeof} cannot. The following
macros are defined in @file{limits.h}.
-@table @code
+@vtable @code
@comment limits.h
@comment ISO
@item CHAR_WIDTH
@code{int}, @code{unsigned int}, @code{long int}, @code{unsigned long
int}, @code{long long int} and @code{unsigned long long int},
respectively.
-@end table
+@end vtable
Further such macros are defined in @file{stdint.h}. Apart from those
for types specified by width (@pxref{Integers}), the following are
defined.
-@table @code
+@vtable @code
@comment stdint.h
@comment ISO
@item INTPTR_WIDTH
These are the widths of the types @code{intptr_t}, @code{uintptr_t},
@code{ptrdiff_t}, @code{sig_atomic_t}, @code{size_t}, @code{wchar_t}
and @code{wint_t}, respectively.
-@end table
+@end vtable
@node Range of Type
@subsection Range of an Integer Type
These are the available flags for the @var{flags} argument:
-@table @code
+@vtable @code
@comment fnmatch.h
@comment GNU
@item FNM_FILE_NAME
The pattern matches if the input string cannot be matched with any of
the patterns in the @var{pattern-list}.
@end table
-@end table
+@end vtable
@node Globbing
@section Globbing
Here are the possible nonzero values that @code{regcomp} can return:
-@table @code
+@vtable @code
@comment regex.h
@comment POSIX.2
@item REG_BADBR
@comment POSIX.2
@item REG_ESPACE
@code{regcomp} ran out of memory.
-@end table
+@end vtable
@node Flags for POSIX Regexps
@subsection Flags for POSIX Regular Expressions
These are the bit flags that you can use in the @var{cflags} operand when
compiling a regular expression with @code{regcomp}.
-@table @code
+@vtable @code
@comment regex.h
@comment POSIX.2
@item REG_EXTENDED
permit @samp{[^@dots{}]} to match a newline.
Otherwise, newline acts like any other ordinary character.
-@end table
+@end vtable
@node Matching POSIX Regexps
@subsection Matching a Compiled POSIX Regular Expression
The function @code{regexec} accepts the following flags in the
@var{eflags} argument:
-@table @code
+@vtable @code
@comment regex.h
@comment POSIX.2
@item REG_NOTBOL
@item REG_NOTEOL
Do not regard the end of the specified string as the end of a line; more
generally, don't make any assumptions about what text might follow it.
-@end table
+@end vtable
Here are the possible nonzero values that @code{regexec} can return:
-@table @code
+@vtable @code
@comment regex.h
@comment POSIX.2
@item REG_NOMATCH
@comment POSIX.2
@item REG_ESPACE
@code{regexec} ran out of memory.
-@end table
+@end vtable
@node Regexp Subexpressions
@subsection Match Results with Subexpressions
If @code{wordexp} succeeds, it returns 0. Otherwise, it returns one
of these error codes:
-@table @code
+@vtable @code
@comment wordexp.h
@comment POSIX.2
@item WRDE_BADCHAR
There was a syntax error in the input string. For example, an unmatched
quoting character is a syntax error. This error code is also used to
signal division by zero and overflow in arithmetic expansion.
-@end table
+@end vtable
@end deftypefun
@comment wordexp.h
@var{flags} argument to @code{wordexp}. Choose the flags you want,
and combine them with the C operator @code{|}.
-@table @code
+@vtable @code
@comment wordexp.h
@comment POSIX.2
@item WRDE_APPEND
@item WRDE_UNDEF
If the input refers to a shell variable that is not defined, report an
error.
-@end table
+@end vtable
@node Wordexp Example
@subsection @code{wordexp} Example
In most systems, @var{processes} has only two valid values:
-@table @code
+@vtable @code
@comment sys/resource.h
@comment BSD
@item RUSAGE_SELF
@comment BSD
@item RUSAGE_CHILDREN
All child processes (direct and indirect) that have already terminated.
-@end table
+@end vtable
The return value of @code{getrusage} is zero for success, and @code{-1}
for failure.
Here is a table of socket-level option names; all are defined in the
header file @file{sys/socket.h}.
-@table @code
+@vtable @code
@comment sys/socket.h
@comment BSD
@item SO_DEBUG
the error status of the socket. The value is an @code{int}, which represents
the previous error status.
@c !!! what is "socket error status"? this is never defined.
-@end table
+@end vtable
@node Networks Database
@section Networks Database
projects / thirdparty / glibc.git / commitdiff
