Related articles |
---|
if then else shift/reduce Syndrome tarnwb@holly.colostate.edu (Tarn Burton) (1996-02-13) |
Re: if then else shift/reduce Syndrome solution@gate.net (1996-02-13) |
Re: if then else shift/reduce Syndrome tim@franck.Princeton.EDU (1996-02-13) |
Re: if then else shift/reduce Syndrome mab@wdl.loral.com (1996-02-14) |
Re: if then else shift/reduce Syndrome theo@engr.mun.ca (1996-02-16) |
Re: if then else shift/reduce Syndrome meissner@cygnus.com (Michael Meissner) (1996-02-16) |
Re: if then else shift/reduce Syndrome solution@gate.net (1996-02-16) |
Re: if then else shift/reduce Syndrome tarnwb@holly.colostate.edu (Tarn Burton) (1996-02-16) |
Re: if then else shift/reduce Syndrome meissner@cygnus.com (Michael Meissner) (1996-02-21) |
Re: if then else shift/reduce Syndrome henry@zoo.toronto.edu (Henry Spencer) (1996-02-27) |
[2 later articles] |
From: | mab@wdl.loral.com (Mark A Biggar) |
Newsgroups: | comp.compilers |
Date: | 14 Feb 1996 21:17:47 -0500 |
Organization: | Loral Western Development Labs |
References: | 96-02-123 |
Keywords: | yacc, parse |
In article 96-02-123 Tarn Burton <tarnwb@holly.colostate.edu> writes:
>Does anyone know how to get rid of the bison shift/reduce conflict in
>the C if then else.
The solution almost always used for this case is to IGNORE IT. Bison's
default action for a S/R conflict (to shift) is exactly what you what here.
--
Mark Biggar
mab@wdl.loral.com
--
Return to the
comp.compilers page.
Search the
comp.compilers archives again.