m4-commit
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Changes to m4/NEWS,v [branch-1_4]


From: Eric Blake
Subject: Changes to m4/NEWS,v [branch-1_4]
Date: Sat, 24 Feb 2007 14:02:24 +0000

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

Index: NEWS
===================================================================
RCS file: /sources/m4/m4/NEWS,v
retrieving revision 1.1.1.1.2.93
retrieving revision 1.1.1.1.2.94
diff -u -b -r1.1.1.1.2.93 -r1.1.1.1.2.94
--- NEWS        8 Feb 2007 14:52:29 -0000       1.1.1.1.2.93
+++ NEWS        24 Feb 2007 14:02:23 -0000      1.1.1.1.2.94
@@ -23,9 +23,9 @@
 * A new `--warn-macro-sequence' command-line option allows detection of
   sequences in `define' and `pushdef' definitions that match an optional
   regular expression.  The default regular expression is
-  `\$\({[0-9][^}]*}\|[0-9][0-9]+\)', corresponding to the sequences that
-  might not behave correctly when upgrading to the eventual M4 2.0.  By
-  default, M4 2.0 will follow the POSIX requirement that a macro definition
+  `\$\({[^}]*}\|[0-9][0-9]+\)', corresponding to the sequences that might
+  not behave correctly when upgrading to the eventual M4 2.0.  By default,
+  M4 2.0 will follow the POSIX requirement that a macro definition
   containing `$11' must expand to the first argument concatenated with 1,
   rather than the eleventh argument; and will take advantage of the POSIX
   wording that allows implementations to treat `${11}' as the eleventh




reply via email to

[Prev in Thread] Current Thread [Next in Thread]