Update.

2002-06-19  Steven Munroe  <sjmunroe@vnet.ibm.com>

	* Examples/ex9.c (main):  Use list of children and join them.
	(thread): Do not call exit.

12 files changed, 37 insertions, 37 deletions

diff --git a/manual/argp.texi b/manual/argp.texi
index b744697..090d49f 100644
--- a/manual/argp.texi
+++ b/manual/argp.texi
@@ -467,7 +467,7 @@ Here's an example that uses both, for different args:
 
 
 @smallexample
-...
+@dots{}
 case ARGP_KEY_ARG:
   if (@var{state}->arg_num == 0)
     /* First argument */
diff --git a/manual/arith.texi b/manual/arith.texi
index c40ba3c..0f2e6fe 100644
--- a/manual/arith.texi
+++ b/manual/arith.texi
@@ -755,9 +755,9 @@ is a simple example of the way to use @code{fetestexcept}:
   feclearexcept (FE_ALL_EXCEPT);
   f = compute ();
   raised = fetestexcept (FE_OVERFLOW | FE_INVALID);
-  if (raised & FE_OVERFLOW) @{ /* ... */ @}
-  if (raised & FE_INVALID) @{ /* ... */ @}
-  /* ... */
+  if (raised & FE_OVERFLOW) @{ /* @dots{} */ @}
+  if (raised & FE_INVALID) @{ /* @dots{} */ @}
+  /* @dots{} */
 @}
 @end smallexample
 
@@ -2396,8 +2396,8 @@ or to the largest representable value if the floating-point format
 doesn't support infinities.  You can prepend a @code{"+"} or @code{"-"}
 to specify the sign.  Case is ignored when scanning these strings.
 
-The strings @code{"nan"} and @code{"nan(@var{chars...})"} are converted
-to NaN.  Again, case is ignored.  If @var{chars...} are provided, they
+The strings @code{"nan"} and @code{"nan(@var{chars@dots{}})"} are converted
+to NaN.  Again, case is ignored.  If @var{chars@dots{}} are provided, they
 are used in some unspecified fashion to select a particular
 representation of NaN (there can be several).
 
diff --git a/manual/charset.texi b/manual/charset.texi
index 4fb58d1..2ebde7d 100644
--- a/manual/charset.texi
+++ b/manual/charset.texi
@@ -177,9 +177,9 @@ code like
 @smallexample
 @{
   int c;
-  ...
+  @dots{}
   while ((c = getc (fp)) < 0)
-    ...
+    @dots{}
 @}
 @end smallexample
 
@@ -190,9 +190,9 @@ are used:
 @smallexample
 @{
   wint_t c;
-  ...
+  @dots{}
   while ((c = wgetc (fp)) != WEOF)
-    ...
+    @dots{}
 @}
 @end smallexample
 
@@ -437,7 +437,7 @@ problem:
   while (! feof (fp))
     @{
       fread (&buf[len], 1, MB_CUR_MAX - len, fp);
-      /* @r{... process} buf */
+      /* @r{@dots{} process} buf */
       len -= used;
     @}
 @}
@@ -491,7 +491,7 @@ clearing the whole variable with code such as follows:
   mbstate_t state;
   memset (&state, '\0', sizeof (state));
   /* @r{from now on @var{state} can be used.}  */
-  ...
+  @dots{}
 @}
 @end smallexample
 
@@ -523,7 +523,7 @@ Code using @code{mbsinit} often looks similar to this:
   mbstate_t state;
   memset (&state, '\0', sizeof (state));
   /* @r{Use @var{state}.}  */
-  ...
+  @dots{}
   if (! mbsinit (&state))
     @{
       /* @r{Emit code to return to initial state.}  */
@@ -531,7 +531,7 @@ Code using @code{mbsinit} often looks similar to this:
       const wchar_t *srcp = empty;
       wcsrtombs (outbuf, &srcp, outbuflen, &state);
     @}
-  ...
+  @dots{}
 @}
 @end smallexample
 
@@ -911,7 +911,7 @@ this solution is unsuitable, there is a very slow but more accurate
 solution.
 
 @smallexample
-  ...
+  @dots{}
   if (len < MB_CUR_LEN)
     @{
       mbstate_t temp_state;
@@ -925,7 +925,7 @@ solution.
           return NULL;
         @}
     @}
-  ...
+  @dots{}
 @end smallexample
 
 Here we perform the conversion that might overflow the buffer so that
@@ -2395,7 +2395,7 @@ The @code{int __internal_use} element is mostly used together with
 if (!data->__internal_use
      && data->__invocation_counter == 0)
   /* @r{Emit prolog.}  */
-  ...
+  @dots{}
 @end smallexample
 
 This element must never be modified.
@@ -2708,7 +2708,7 @@ gconv (struct __gconv_step *step, struct __gconv_step_data *data,
 @{
   struct __gconv_step *next_step = step + 1;
   struct __gconv_step_data *next_data = data + 1;
-  ...
+  @dots{}
 @end smallexample
 
 The @code{next_step} pointer references the next step information and
diff --git a/manual/ctype.texi b/manual/ctype.texi
index 593f7f3..1117363 100644
--- a/manual/ctype.texi
+++ b/manual/ctype.texi
@@ -625,7 +625,7 @@ is_in_class (int c, const char *class)
     return isalpha (c);
   if (strcmp (class, "cntrl") == 0)
     return iscntrl (c);
-  ...
+  @dots{}
   return 0;
 @}
 @end smallexample
diff --git a/manual/filesys.texi b/manual/filesys.texi
index a74f32d..0f12746 100644
--- a/manual/filesys.texi
+++ b/manual/filesys.texi
@@ -453,7 +453,7 @@ Code to call @code{readdir_r} could look like this:
   @} u;
 
   if (readdir_r (dir, &u.d, &res) == 0)
-    ...
+    @dots{}
 @end smallexample
 @end deftypefun
 
@@ -1501,7 +1501,7 @@ modify the attributes of a file.
                                  and what their values mean.
 * Reading Attributes::          How to read the attributes of a file.
 * Testing File Type::           Distinguishing ordinary files,
-                                 directories, links...
+                                 directories, links@dots{}
 * File Owner::                  How ownership for new files is determined,
 			         and how to change it.
 * Permission Bits::             How information about a file's access
diff --git a/manual/install.texi b/manual/install.texi
index afadcdb..a8f003d 100644
--- a/manual/install.texi
+++ b/manual/install.texi
@@ -45,7 +45,7 @@ GNU Make, and possibly others.  @xref{Tools for Compilation}, below.
 GNU libc can be compiled in the source directory, but we strongly advise
 building it in a separate build directory.  For example, if you have
  unpacked
-the glibc sources in @file{/src/gnu/glibc-2.2.0}, create a directory
+the glibc sources in @file{/src/gnu/glibc-2.3}, create a directory
 @file{/src/gnu/glibc-build} to put the object files in.  This allows
 removing the whole build directory in case an error occurs, which is the
 safest way to get a fresh start and should always be done.
@@ -54,7 +54,7 @@ From your object directory, run the shell script @file{configure} located
 at the top level of the source tree.  In the scenario above, you'd type
 
 @smallexample
-$ ../glibc-2.2.0/configure @var{args...}
+$ ../glibc-2.3/configure @var{args@dots{}}
 @end smallexample
 
 Please note that even if you're building in a separate build directory,
@@ -64,9 +64,9 @@ directory, especially some files in the manual subdirectory.
 @noindent
 @code{configure} takes many options, but you can get away with knowing
 only two: @samp{--prefix} and @samp{--enable-add-ons}.  The
-@code{--prefix} option tells @code{configure} where you want glibc 
+@code{--prefix} option tells @code{configure} where you want glibc
 installed. This defaults to @file{/usr/local}.  The
-@samp{--enable-add-ons} option tells @code{configure} to use all the 
+@samp{--enable-add-ons} option tells @code{configure} to use all the
 add-on bundles it finds in the source directory.  Since important
 functionality is provided in add-ons, you should always specify this
 option.
diff --git a/manual/locale.texi b/manual/locale.texi
index f477ac8..e3e0563 100644
--- a/manual/locale.texi
+++ b/manual/locale.texi
@@ -1201,7 +1201,7 @@ least also in the IBM AIX library.
 This function would normally be used like this:
 
 @smallexample
-  ...
+  @dots{}
   /* @r{Use a safe default.}  */
   _Bool doit = false;
 
diff --git a/manual/memory.texi b/manual/memory.texi
index e64dc8d..c840e70 100644
--- a/manual/memory.texi
+++ b/manual/memory.texi
@@ -751,7 +751,7 @@ End with a line saying just "end".
 >call mcheck(0)
 >continue
 >end
-(gdb) ...
+(gdb) @dots{}
 @end smallexample
 
 This will however only work if no initialization function of any object
@@ -1003,7 +1003,7 @@ my_free_hook (void *ptr, const void *caller)
 
 main ()
 @{
-  ...
+  @dots{}
 @}
 @end smallexample
 
diff --git a/manual/resource.texi b/manual/resource.texi
index 3beb939..9d2e17b 100644
--- a/manual/resource.texi
+++ b/manual/resource.texi
@@ -546,7 +546,7 @@ any one time is equal to the number of CPUs, you can easily extrapolate
 the information.
 
 The functions described in this section are all defined by the POSIX.1
-and POSIX.1b standards (the @code{sched...} functions are POSIX.1b).
+and POSIX.1b standards (the @code{sched@dots{}} functions are POSIX.1b).
 However, POSIX does not define any semantics for the values that these
 functions get and set.  In this chapter, the semantics are based on the
 Linux kernel's implementation of the POSIX standard.  As you will see,
@@ -656,7 +656,7 @@ the high priority process group.  All the priority in the world won't
 stop an interrupt handler from running and delivering a signal to the
 process if you hit Control-C.
 
-Some systems use absolute priority as a means of allocating a fixed 
+Some systems use absolute priority as a means of allocating a fixed
 percentage of CPU time to a process.  To do this, a super high priority
 privileged process constantly monitors the process' CPU usage and raises
 its absolute priority when the process isn't getting its entitled share
diff --git a/manual/startup.texi b/manual/startup.texi
index 35ddbc4..5ccb78b 100644
--- a/manual/startup.texi
+++ b/manual/startup.texi
@@ -657,7 +657,7 @@ Example:
 #include <sys/syscall.h>
 #include <errno.h>
 
-...
+@dots{}
 
 int rc;
 
@@ -677,7 +677,7 @@ following preferable code:
 #include <sys/stat.h>
 #include <errno.h>
 
-...
+@dots{}
 
 int rc;
 
diff --git a/manual/stdio.texi b/manual/stdio.texi
index 05ecab0..39fd4fb 100644
--- a/manual/stdio.texi
+++ b/manual/stdio.texi
@@ -497,7 +497,7 @@ sometimes not possible):
 @smallexample
 FILE *fp;
 @{
-   ...
+   @dots{}
    flockfile (fp);
    fputs ("This is test number ", fp);
    fprintf (fp, "%d\n", test);
@@ -2450,7 +2450,7 @@ For example:
 
 @smallexample
 #define myprintf(a, b, c, d, e, rest...) \
-            printf (mytemplate , ## rest...)
+            printf (mytemplate , ## rest)
 @end smallexample
 
 @noindent
@@ -5295,7 +5295,7 @@ the following in the environment before calling the @code{fmtmsg} function
 the first time:
 
 @smallexample
-MSGVERB=@var{keyword}[:@var{keyword}[:...]]
+MSGVERB=@var{keyword}[:@var{keyword}[:@dots{}]]
 @end smallexample
 
 Valid @var{keyword}s are @code{label}, @code{severity}, @code{text},
@@ -5314,7 +5314,7 @@ described above are available.  Any other numeric value would make
 If the user puts @code{SEV_LEVEL} with a format like
 
 @smallexample
-SEV_LEVEL=[@var{description}[:@var{description}[:...]]]
+SEV_LEVEL=[@var{description}[:@var{description}[:@dots{}]]]
 @end smallexample
 
 @noindent
diff --git a/manual/time.texi b/manual/time.texi
index 9744982..645c876 100644
--- a/manual/time.texi
+++ b/manual/time.texi
@@ -1435,7 +1435,7 @@ character, not the number of bytes.
 Also the format string @var{template} is a wide character string.  Since
 all characters needed to specify the format string are in the basic
 character set it is portably possible to write format strings in the C
-source code using the @code{L"..."} notation.  The parameter
+source code using the @code{L"@dots{}"} notation.  The parameter
 @var{brokentime} has the same meaning as in the @code{strftime} call.
 
 The @code{wcsftime} function supports the same flags, modifiers, and