Received: from localhost (IDENT:root@hectic-2.jpl.nasa.gov [128.149.68.204])
	by hub.org (8.9.3/8.9.3) with ESMTP id CAA39040
	for <pgsql-interfaces@postgreSQL.org>;
	Tue, 22 Jun 1999 02:35:23 -0400 (EDT)
	(envelope-from lockhart@alumni.caltech.edu)
Received: from alumni.caltech.edu (lockhart@localhost [127.0.0.1])
	by localhost (8.8.7/8.8.7) with ESMTP id GAA19753;
	Tue, 22 Jun 1999 06:36:42 GMT
Sender: lockhart@hub.org
Message-ID: <376F2EFA.6AECCBE@alumni.caltech.edu>
Date: Tue, 22 Jun 1999 06:36:42 +0000
From: Thomas Lockhart <lockhart@alumni.caltech.edu>
X-Mailer: Mozilla 4.6 [en] (X11; I; Linux 2.0.36 i686)
X-Accept-Language: en
MIME-Version: 1.0
To: selkovjr@mcs.anl.gov
CC: pgsql-interfaces@postgreSQL.org
Subject: Re: [INTERFACES] esql\c documentation
References: <199906220143.UAA24345@antares.mcs.anl.gov>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

> Excuse me -- what's wrong with shift/reduce conflicts? I have over a
> hundred of those in one of my applications.

If it is the kind of shift/reduce conflict reported by yacc/bison
(rather than a less severe clarification printed in the bison "-v" log
file) then it means that there is a significant part of your grammar
which can *never* be reached! The parser will always choose one of the
two possible paths in the conflict, and will never choose the other.
Not good if you actually wanted to use the full language.

                    - Thomas

-- 
Thomas Lockhart				lockhart@alumni.caltech.edu
South Pasadena, California