[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: too many warnings from Bison CVS for Pike
From: |
Joel E. Denny |
Subject: |
Re: too many warnings from Bison CVS for Pike |
Date: |
Tue, 14 Feb 2006 18:29:11 -0500 (EST) |
On Tue, 14 Feb 2006, Hans Aberg wrote:
> If %union using a C++ compiler automatically invokes the dynamic C-
> parserstack, then there would only be the need for such an option for user
> that want to use a POD type without %union.
Well, I hate to admit it, but I have a peculiar situation when I don't use
%union and I do use #define YYSTYPE_IS_TRIVIAL 1. YYSTYPE_IS_TRIVIAL is
not actually documented for the user, but the problem should go away once
I can convert to the C++ skeletons.
> But is not the combination of YYLTYPE_IS_TRIVIAL and YYSTYPE_IS_TRIVIAL the
> same as the macro CPP_SEMANTIC_POD I suggested? Why do you need two macros? Is
> not enough with one macro YYTYPES_ARE_POD, which, when defined, invoked the
> dynamic C-parser?
The easiest approach is just to document the existing macros. Who knows,
other Bison users might be using them now anyway. I have no strong
preference about this.
Joel
- Re: too many warnings from Bison CVS for Pike, Paul Eggert, 2006/02/11
- Re: too many warnings from Bison CVS for Pike, Paul Eggert, 2006/02/13
- Re: too many warnings from Bison CVS for Pike, Hans Aberg, 2006/02/13
- Re: too many warnings from Bison CVS for Pike, Paul Eggert, 2006/02/13
- Re: too many warnings from Bison CVS for Pike, Hans Aberg, 2006/02/14
- Re: too many warnings from Bison CVS for Pike, Paul Eggert, 2006/02/14
- Re: too many warnings from Bison CVS for Pike, Hans Aberg, 2006/02/14
- Re: too many warnings from Bison CVS for Pike, Akim Demaille, 2006/02/20