Changes to m4/doc/m4.texinfo,v [branch-1_4]

[Eric Blake]

CVSROOT:        /sources/m4
Module name:    m4
Branch:         branch-1_4
Changes by:     Eric Blake <ericb>      06/07/24 20:02:16

Index: doc/m4.texinfo
===================================================================
RCS file: /sources/m4/m4/doc/m4.texinfo,v
retrieving revision 1.1.1.1.2.51
retrieving revision 1.1.1.1.2.52
diff -u -b -r1.1.1.1.2.51 -r1.1.1.1.2.52
--- doc/m4.texinfo      19 Jul 2006 18:16:23 -0000      1.1.1.1.2.51
+++ doc/m4.texinfo      24 Jul 2006 20:02:16 -0000      1.1.1.1.2.52
@@ -3873,8 +3873,9 @@
 
 @deffn Builtin m4exit (@dvar{code, 0})
 Causes @code{m4} to exit, with exit status @var{code}.  If @var{code} is
-left out, the exit status is zero.  No further input is read, and all
-wrapped and diverted text is discarded.
+left out, the exit status is zero.  If @var{code} cannot be parsed, or
+is outside the range of 0 to 255, the exit status is one.  No further
+input is read, and all wrapped and diverted text is discarded.
 @end deffn
 
 A common use of this is to abort processing:
@@ -3908,6 +3909,11 @@
 m4exit
 @end example
 
+Note that it is still possible for the exit status to be different than
+what was requested by @code{m4exit}.  If @code{m4} detects some other
+error, such as a write error on standard out, the exit status will be
+non-zero even if @code{m4exit} requested zero.
+
 @node Frozen files
 @chapter Fast loading of frozen state
 
@@ -4235,11 +4241,6 @@
 @code{m4exit} (@pxref{M4exit}) with a non-numeric argument).
 
 @item
address@hidden requires an application to exit with non-zero status if
-it encounters a read error on stdin or write error on stdout, but GNU
address@hidden still exits with status 0 even if the disk is full.
-
address@hidden
 @acronym{POSIX} requires @code{m4wrap} (@pxref{M4wrap}) to act in FIFO
 (first-in, first-out) order, but GNU @code{m4} currently uses LIFO order.
 Furthermore, @acronym{POSIX} states that only the first argument to