diff options
author | Akim Demaille <akim.demaille@gmail.com> | 2021-01-31 13:18:51 +0100 |
---|---|---|
committer | Akim Demaille <akim.demaille@gmail.com> | 2021-02-01 05:54:06 +0100 |
commit | dc8fe0678a6f32a1d755bb163efcac42976220d9 (patch) | |
tree | bb0457c06d80ca6302d7ecbbe33af73c74736595 /NEWS | |
parent | a70e21215ae8ae8d9c65a633a858ad30b7fd6690 (diff) | |
download | bison-dc8fe0678a6f32a1d755bb163efcac42976220d9.tar.gz |
c++: make it clear that #define YYSTYPE is not supported
We have been accepting this for years, but it is deprecated: people
are expecting to define api.value.type instead.
* doc/bison.texi: Make it clear that YYSTYPE and YYLTYPE are for C
only.
Diffstat (limited to 'NEWS')
-rw-r--r-- | NEWS | 7 |
1 files changed, 7 insertions, 0 deletions
@@ -2,6 +2,13 @@ GNU Bison NEWS * Noteworthy changes in release 3.7.5 (2021-01-24) [stable] +** Deprecated features + + It is always recommended to prefer `%define api.value.type foo` to + `#define YYSTYPE foo`. The latter is supported in C for compatibility + with Yacc, but not in C++. Warnings are now issued if `#define YYSTYPE` + is used in C++, and eventually support will be removed. + ** Bug fixes *** Counterexample Generation |