Hi Vince,
> Le 23 août 2021 à 14:58, Vince Huffaker a écrit :
>
> Hi Akim,
>
>>> But, maybe there's some alternative approach for bison in the future?
>>> Maybe we could reserve a range of token values... or somehow indicate to
>>> Bison that our token values are not truly 'custom', but are
Hi Akim,
But, maybe there's some alternative approach for bison in the future? Maybe we
could reserve a range of token values... or somehow indicate to Bison that our
token values are not truly 'custom', but are sequential numbers... maybe that
would help? Don't know -- just trying ideas..
Hi Vince,
> Le 22 août 2021 à 22:14, Vince Huffaker a écrit :
>
> That macro doesn't seem to exist, but the _MSC_VER does, so this line:
>
> #ifndef _MSC_VER
>
> fixes the issue.
Yes, of course, sorry about that...
>> Also, do you really need to specify the numbers for all the toke
Hi Akim,
Thank you for your reply. See the input file, ApReadBinary.ypp (I have reduced
it greatly from the original). The HPP file has the bad line at line # 3900 -
the YY_ASSERT is too long.
But line 3900 is no long, if you read "line" in the text file sense:
3900 YY_ASSERT (to
Hi Vince,
> Le 22 août 2021 à 03:58, Vince Huffaker a écrit :
>
> Hi,
>
> Thank you for your reply. See the input file, ApReadBinary.ypp (I have
> reduced it greatly from the original). The HPP file has the bad line at line
> # 3900 - the YY_ASSERT is too long.
But line 3900 is no long, if
Hi,
Thank you for your reply. See the input file, ApReadBinary.ypp (I have
reduced it greatly from the original). The HPP file has the bad line at
line # 3900 - the YY_ASSERT is too long.
The key parameters in the YPP file seem to be:
%language "c++"
%define parse.assert
Thank you very muc
Hi Vince,
> Le 20 août 2021 à 21:39, Vince Huffaker a écrit :
>
> Hi,
>
> I know this has been a known bug, but it says that it is fixed, and we just
> installed the latest bison, 3.7.6 (from cygwin). We are building a YPP file
> and getting this error on a YY_ASSERT line that has lots of to
Hi,
I know this has been a known bug, but it says that it is fixed, and we
just installed the latest bison, 3.7.6 (from cygwin). We are building a
YPP file and getting this error on a YY_ASSERT line that has lots of
tokens in it.
Was this bug fixed? Do we have some weirdness in our code th