cvs.gedasymbols.org/archives/browse.cgi | search |
From: | ams AT ludd DOT luth DOT se (Martin Str|mberg) |
Newsgroups: | comp.os.msdos.djgpp,comp.programming |
Subject: | Re: Bison and [f]lexical tie-ins |
Followup-To: | comp.os.msdos.djgpp,comp.programming |
Date: | 10 Jul 1999 18:52:15 GMT |
Organization: | University of Lulea, Sweden |
Lines: | 19 |
Message-ID: | <7m84ov$ns5$1@news.luth.se> |
References: | <37863AAA DOT BF85DE25 AT americasm01 DOT nt DOT com> <7m5r26$see$1 AT news DOT luth DOT se> <3786BC45 DOT B89C14F5 AT unb DOT ca> <7m784h$dd5$2 AT news DOT luth DOT se> <37876DD0 DOT 8AFDFDA0 AT unb DOT ca> |
NNTP-Posting-Host: | queeg.ludd.luth.se |
X-Newsreader: | TIN [UNIX 1.3 950824BETA PL0] |
To: | djgpp AT delorie DOT com |
DJ-Gateway: | from newsgroup comp.os.msdos.djgpp |
Reply-To: | djgpp AT delorie DOT com |
Endlisnis (s257m AT unb DOT ca) wrote: : That is sort-of what I've been doing, but to do the parsing correctly, I need to : know if "b" is a type-specifier or an ID. And the reduce/reduce errors are in the No. At the parsing stage, it seems to me from your problem desciption, all you know is that "b" is an ID (which could be a type or a variable). : parsing stage. I know how to deal with it after it's been parsed, just getting it : parsed without the reduce warnings was what I wanted. My parser still works with Hmm. So your problem appeared, when you tried to reduce the warnings. I'm not sure a C or C++ parser can be made with lex and yacc without any reduce warnings. Nielsen, String Quartet in F flat major, MartinS
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |