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 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
k you very much for your help!
--Vince--
On 8/21/2021 12:54 AM, Akim Demaille wrote:
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
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
