Re: Unexpected C Parsing Conflict

pocm@[EMAIL PROTECTED]
 (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 ****ft 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 ****ft/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 soton.ac.uk
http://www.personal.soton.ac.uk/pocm
PhD Student @[EMAIL PROTECTED]
 ECS
University of Southampton, UK