diff options
| author | Akim Demaille <akim.demaille@gmail.com> | 2021-11-07 09:27:52 +0100 |
|---|---|---|
| committer | Akim Demaille <akim.demaille@gmail.com> | 2021-11-07 09:52:05 +0100 |
| commit | 6571c2d1b134bd04d81f1426c08985407e8c7087 (patch) | |
| tree | fe0328628246b1db6b2a661c6738a1940a5bfac1 /NEWS | |
| parent | c95d0dd5f54b98825e4cfe00a807db78a073e376 (diff) | |
| download | bison-6571c2d1b134bd04d81f1426c08985407e8c7087.tar.gz | |
warnings: don't complain about m4_foo and b4_foo when from the user
Currently, occurrences of these identifiers in the user's input yield
spurious warnings.
To tell the difference between a legitimate m4_foo from the user, and
a bad m4_foo coming from a non-evaluated macro of a skeleton, escape
the user's identifiers as m4@'_foo. We already use @' as a special
sequence to be stripped from the skeleton's output.
See <https://lists.gnu.org/r/bug-bison/2021-10/msg00026.html> and
previous commit ("warnings: be less picky about occurrences of m4_/b4_
in the output").
* src/flex-scanner.h (OBSTACK_SGROW): New.
* src/output.c (output_escaped): Escape m4_ and b4_.
* src/scan-code.l: Likewise.
* src/system.h (obstack_escape): Likewise.
And rewrite as a function.
* tests/skeletons.at (Suspicious sequences): Make sure the user can
use m4_foo/b4_foo without spurious warnings.
Diffstat (limited to 'NEWS')
| -rw-r--r-- | NEWS | 3 |
1 files changed, 3 insertions, 0 deletions
@@ -2,6 +2,9 @@ GNU Bison NEWS * Noteworthy changes in release ?.? (????-??-??) [?] + Fixed portability issues of the test suite on Solaris. + + Fixed spurious warnings about input containing `m4_` or `b4_`. * Noteworthy changes in release 3.8.2 (2021-09-25) [stable] |