Hi all,
I have a rule as following (:ab|ba|a|b)
: K_timeunit TIME_LITERAL';'
K_timeprecision TIME_LITERAL';'
< >
| K_timeprecision TIME_LITERAL';'
K_timeunit TIME_LITERAL';'
< >
| K_timeprecision TIME_LITERAL';'
< >
You haven't given enough information; it looks like there's an embedded
action you've left out. Construct a simple test case and post it.
Alternatively, just start with the production as shown in SV3.1a:
timeunits_declaration
: timeunit time_literal ';'
| timeprecision time_literal ';'
Hi Evan,
As you mentioned the problem was with the action in between.
I modified it now it works fine.
There are only some shift/reduce conflicts now,which are expected.
Thanks
Sreeraj
From: Evan Lavelle
To: help-bison@gnu.org
Sent: Friday, 19 June, 2009 4:47
Hi all,
I'm writing my Master thesis that includes a parser. I chose to use Flex and
Bison to help me with this and include the parser into my Visual C++ project.
I stoped at the following issue and I do not know how to recover from it.
Everything appears to be fine as far as I can see
Just a generic comment: Whenever I think I've defined something via an included
header file, but get this type of error, I generate the preprocessor output to
see what the compiler really is seeing. There might be some macro preventing
the definition from really being included.
-Mary Ann
---
On 19 Jun 2009, at 17:38, Ewa Rom wrote:
I'm writing my Master thesis that includes a parser. I chose to use
Flex and Bison to help me with this and include the parser into my
Visual C++ project.
...
Then I try to build the project and I get the following error:
1>CoProveParser.y(28) : er
Hans,
The bison.exe is 2.4.1.3411
I run it on Win XP HE Version 2002 SP3
Do you recommed going to bison 2.6?
Thank you
Ewa
> From: hab...@math.su.se
> To: ewuni...@hotmail.com
> Date: Fri, 19 Jun 2009 18:55:57 +0200
> CC: help-bison@gnu.org
> Subject: Re: Unable to compile in Visual
On 19 Jun 2009, at 19:22, Ewa Rom wrote:
The bison.exe is 2.4.1.3411
I run it on Win XP HE Version 2002 SP3
Do you recommed going to bison 2.6?
Do that, just to be sure, and the try the other advice, run it through
the processor to see what that syntax error "missing ';' before '*'"
comes