Re: gnubol: Hacks needed to parse COBOL

[Tim Josling <TIMJOSLING@prodigy.net>]

RKRayhawk@aol.com wrote:

> (good advice/bison 102)

I am trying to get the hacks down to those that are needed because of genuine
uncertainty combined with a need to reduce something at the same time. Often I
can get around it by expanding out some of the nested productions. Sometimes
not.

Now that I have the precedence fully working it has made a lot of things easier.

Also you commented on the fragility of the fact I am doing lookahead and so is
the parser. Bison only looks one token forward and I this should not span the
'procedure division [].' sentence. So as long as I trigger the token rework at
that moment I should be able to avoid trouble. But it requires careful
management.

Regards,
Tim Josling




--
This message was sent through the gnu-cobol mailing list.  To remove yourself
from this mailing list, send a message to majordomo@lusars.net with the
words "unsubscribe gnu-cobol" in the message body.  For more information on
the GNU COBOL project, send mail to gnu-cobol-owner@lusars.net.