Path: csiph.com!x330-a1.tempe.blueboxinc.net!usenet.pasdenom.info!weretis.net!feeder4.news.weretis.net!news.glorb.com!border3.nntp.dca.giganews.com!border1.nntp.dca.giganews.com!nntp.giganews.com!news.iecc.com!lnews.iecc.com!nerds-end From: Hans Aberg Newsgroups: comp.compilers Subject: Re: bison c-parse.y:1115.19-20: $$ for the midrule at $4 of `structsp' has no declared type Date: Mon, 31 Oct 2011 20:49:28 +0100 Organization: A noiseless patient Spider Lines: 23 Sender: news@iecc.com Approved: comp.compilers@iecc.com Message-ID: <11-11-003@comp.compilers> References: <11-10-020@comp.compilers> NNTP-Posting-Host: lnews.iecc.com X-Trace: gal.iecc.com 1320177624 30567 64.57.183.34 (1 Nov 2011 20:00:24 GMT) X-Complaints-To: abuse@iecc.com NNTP-Posting-Date: Tue, 1 Nov 2011 20:00:24 +0000 (UTC) Xref: x330-a1.tempe.blueboxinc.net comp.compilers:305 Keywords: bison Posted-Date: 01 Nov 2011 16:00:24 EDT X-submission-address: compilers@iecc.com X-moderator-address: compilers-request@iecc.com X-FAQ-and-archives: http://compilers.iecc.com On 2011/10/31 14:15, Alessandro Basili wrote: > ... then I got the following message: > >> cd .; bison -v -d c-parse.y -o c-parse.c >> c-parse.y: conflicts: 10 shift/reduce >> c-parse.y: expected 8 shift/reduce conflicts > > I believe I'm in the dark here. Usually, it means that one has to get hold of the authors of the package, to find out what they had in mind: One can deliberately leave shift/reduce conflicts, in which case Bison will issue a warning, which can be suppressed %expect (see section 3.7.8 "Suppressing Conflict Warnings" in the Bison manual). However, there is no way to be sure of that. Especially when it say expected 8, and you got 10. But the compile and parser will run. Hans [I made the obvious patches and also got 10 rather than 8. I agree, give this decade-old code a try and see if it works. -John]