[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: api.prefix history
From: |
Akim Demaille |
Subject: |
Re: api.prefix history |
Date: |
Sun, 30 Aug 2020 09:31:25 +0200 |
Hi Matthew.
> Le 25 août 2020 à 16:15, Matthew Fernandez <matthew.fernandez@gmail.com> a
> écrit :
>
> Hello all,
>
> I accidentally stumbled across a quirk, that Bison 2.6 - 3.0 expects the
> api.prefix option value to be given without braces. This surprised me because
> the Bison %define summary [0] gives no relevant change history for this
> option beyond its introduction in 2.6. Could the change I’ve described be
> added to the historical description?
Sure. Done. Cheers.
commit 0522047c96e18361b62a42da3a15817959483cbd
Author: Akim Demaille <akim.demaille@gmail.com>
Date: Sun Aug 30 09:29:00 2020 +0200
doc: history of api.prefix
Reported by Matthew Fernandez <matthew.fernandez@gmail.com>.
https://lists.gnu.org/r/help-bison/2020-08/msg00015.html
* doc/bison.texi (api.prefix): We move to {} in 3.0.
diff --git a/doc/bison.texi b/doc/bison.texi
index e404eb03..48428f04 100644
--- a/doc/bison.texi
+++ b/doc/bison.texi
@@ -6296,7 +6296,10 @@ Introduced in Bison 3.3 to replace
@code{parser_class_name}.
@item Default Value: @code{YY} for Java, @code{yy} otherwise.
-@item History: introduced in Bison 2.6
+@item History:
+introduced in Bison 2.6, with its argument in double quotes. Uses braces
+since Bison 3.0 (double quotes are still supported for backward
+compatibility).
@end itemize
@end deffn
- api.prefix history, Matthew Fernandez, 2020/08/25
- Re: api.prefix history,
Akim Demaille <=