🚀 go-pugleaf

In article <330@rabbit1.UUCP>, dml@rabbit1.UUCP writes:
> in article <1740@encore.UUCP>, pierson@encore.UUCP (Dan Pierson) says:
> > Trying to yacc logo.y produces:
> > 
> > conflicts: 19 shift/reduce, 80 reduce/reduce
> > 
> > Bison produces the same thing, though the diagnostics seem better.
> > 
> > Does anyone know what the problem is?
> 
> I am experiencing the same problems, in addition to the cc failing on the
> y.tab.c result with errors in preprocessor ifdef's??????
> 
> Help please (note that if I run y.tab.c through the preprocessor 1st, save the
> output and then cc the output, it works OK??).

The complaints of yacc are normal and OK.  It is merely saying there are
conflicts in the grammar.  It does resolve them, though.  The reason for
the messages is that the grammar writer should know how many conflicts
there are, and know that he got what he expected.

As for the #if problem, I ran accross that, too.  You need to have a

#define YYDEBUG 0

somewhere.  Yacc includes lines of the form

#if YYDEBUG

which conditionally compiles code if YYDEBUG evaluates to a non-zero expression.
However, since YYDEBUG is never #defined, the preprocessor sees an undefined
symbol name where it expects a numeric expression.

Mike Lindner
...!ihnp4!attunix!mpl