summaryrefslogtreecommitdiff
path: root/NEWS
diff options
context:
space:
mode:
authorEric Blake <ebb9@byu.net>2007-02-24 14:02:23 +0000
committerEric Blake <ebb9@byu.net>2007-09-21 15:39:30 -0600
commite1c1a4dc1d6a523c0ef6513f3ba3d287c53a071d (patch)
tree0c5a041b8b7b89942a38d086db4c3e62a8e8b4bb /NEWS
parent1471706538220c3bb527ea242dcf4dbd99d00961 (diff)
downloadm4-e1c1a4dc1d6a523c0ef6513f3ba3d287c53a071d.tar.gz
Reserve all uses of raw ${} in macro definitions, not just
${<digit>}. * src/builtin.c (set_macro_sequence): Change default macro sequence. * doc/m4.texinfo (Operation modes): Update to match. * src/m4.c (usage): Likewise. * NEWS: Likewise.
Diffstat (limited to 'NEWS')
-rw-r--r--NEWS6
1 files changed, 3 insertions, 3 deletions
diff --git a/NEWS b/NEWS
index ef99ea17..85f59a88 100644
--- a/NEWS
+++ b/NEWS
@@ -23,9 +23,9 @@ Version 1.4.9 - ?? ??? 2007, by ???? (CVS version 1.4.8a)
* 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