Re: Unexpected C Parsing Conflict (Paulo Jorge de O. C. de Matos)
Sat, 26 Apr 2008 12:27:40 +0100

          From comp.compilers

Related articles
Unexpected C Parsing Conflict (2008-04-25)
Re: Unexpected C Parsing Conflict (2008-04-26)
| List of all articles for this month |

From: (Paulo Jorge de O. C. de Matos)
Newsgroups: comp.compilers
Date: Sat, 26 Apr 2008 12:27:40 +0100
Organization: NNTP Server
References: 08-04-095
Keywords: C, parse
Posted-Date: 26 Apr 2008 13:05:23 EDT (Paulo Jorge de O. C. de Matos) writes:

> I have found a conflict in parsing C99 which arises from the fact that
> after a mult_expr a '*' (according to bison) can come up which means
> that it can either reduce mult_expr or shift the '*' for yet another
> multiplication.
> Now, * comes up as a unary operator and in the pointer definition but
> I can't find how or where they can follow a multiplication. Can
> someone let me know either how to solve this shift/reduce conflict or
> give me a concrete example where a * comes after a multiplication and
> is not a multiplication operator?

I have been able in the meantime to solve the issue. I had missing a
comma in the initializer-list nonterminal symbol definition.

Paulo Jorge Matos - pocm at
PhD Student @ ECS
University of Southampton, UK

Post a followup to this message

Return to the comp.compilers page.
Search the comp.compilers archives again.