Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!seismo!rutgers!ucla-cs!zen!ucbvax!hoptoad!gnu
From: gnu@hoptoad.uucp (John Gilmore)
Newsgroups: comp.sources.bugs
Subject: Re: yacc complains even though everything's OK
Message-ID: <2521@hoptoad.uucp>
Date: Sun, 26-Jul-87 16:54:31 EDT
Article-I.D.: hoptoad.2521
Posted: Sun Jul 26 16:54:31 1987
Date-Received: Sun, 26-Jul-87 22:37:42 EDT
References: <1740@encore.UUCP> <330@rabbit1.UUCP> <1649@sfsup.UUCP>
Organization: Nebula Consultants in San Francisco
Lines: 23

in article <1740@encore.UUCP>, pierson@encore.UUCP (Dan Pierson) says:
> conflicts: 19 shift/reduce, 80 reduce/reduce
> Bison produces the same thing, though the diagnostics seem better.
> Does anyone know what the problem is?

mpl@sfsup.UUCP (M.P.Lindner) wrote:
> The complaints of yacc are normal and OK...

I added -s and -r switches to Bison (the GNU yacc-compatible parser generator)
which allow the user to specify how many shift/reduce conflicts and
how many reduce/reduce conflicts are expected.  No message is produced
if the numbers specified are correct.

I got tired of seeing every Makefile that used yacc say:

	@echo "expect 17 shift/reduce conflicts"
	yacc ....

I've sent in the changes so they will probably appear in a future
Bison release.
-- 
{dasys1,ncoast,well,sun,ihnp4}!hoptoad!gnu	     gnu@postgres.berkeley.edu
Alt.all: the alternative radio of the Usenet.