Re: Multiple, different, %merge of a token sequence

[Joel E. Denny]

On Mon, 1 May 2006, Derek M Jones wrote:

> What happens is that the bison generated parser builds
> all four parse stacks, resolves one pair of sizeof
> ambiguities by calling sizeof_merge (leaving three stacks)
> and then calls multiplicative_merge twice (leaving 1 stack).
> 
> I think there should be two calls to sizeof_merge and one to
> multiplicative_merge.

Make sure you are running at least Bison 2.1.  If the results still don't 
make sense to you, post again and I'll look harder at this.

In the future, please tell us what version of Bison you are running.

Joel