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>      07/02/24 14:02:23

Index: doc/m4.texinfo
===================================================================
RCS file: /sources/m4/m4/doc/m4.texinfo,v
retrieving revision 1.1.1.1.2.114
retrieving revision 1.1.1.1.2.115
diff -u -b -r1.1.1.1.2.114 -r1.1.1.1.2.115
--- doc/m4.texinfo      8 Feb 2007 14:52:29 -0000       1.1.1.1.2.114
+++ doc/m4.texinfo      24 Feb 2007 14:02:23 -0000      1.1.1.1.2.115
@@ -590,13 +590,13 @@
 @code{pushdef}).  Empty matches are ignored; therefore, supplying the
 empty string as @var{REGEXP} disables any warning.  If the optional
 @var{REGEXP} is not supplied, then the default regular expression is
address@hidden(@address@hidden@}\|[0-9][0-9]+\)} (a literal @samp{$} followed
-by multiple digits or by an open brace and a digit), since these
-sequences will change semantics in the default operation of
address@hidden M4 2.0 (due to a change in how more than 9 arguments in a
-macro definition will be handled, @pxref{Arguments}).  Providing an
-alternate regular expression can provide a useful reverse lookup feature
-of finding where a macro is defined to have a given definition.
address@hidden(@address@hidden@}\|[0-9][0-9]+\)} (a literal @samp{$} followed by
+multiple digits or by an open brace), since these sequences will
+change semantics in the default operation of @acronym{GNU} M4 2.0 (due
+to a change in how more than 9 arguments in a macro definition will be
+handled, @pxref{Arguments}).  Providing an alternate regular
+expression can provide a useful reverse lookup feature of finding
+where a macro is defined to have a given definition.
 
 @item -W @var{REGEXP}
 @itemx address@hidden
@@ -6388,7 +6388,7 @@
 @bye
 
 @c Local Variables:
address@hidden coding: ISO-8859-1
address@hidden coding: iso-8859-1
 @c fill-column: 72
 @c ispell-local-dictionary: "american"
 @c indent-tabs-mode: nil