Re: if then else shift/reduce Syndrome

solution@gate.net (Ken Walter)
16 Feb 1996 23:39:11 -0500

          From comp.compilers
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)
Re: if then else shift/reduce Syndrome neitzel@gaertner.de (1996-03-01)
Re: if then else shift/reduce Syndrome bakul@netcom.com (1996-03-03)
| List of all articles for this month |
From: solution@gate.net (Ken Walter)
Newsgroups: comp.compilers
Date: 16 Feb 1996 23:39:11 -0500
Organization: Solution Technology
References: 96-02-123 96-02-139
Keywords: yacc, parse

| 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.
|
| Yes, classify statements as open or closed.


Michael Meissner <meissner@cygnus.com> writes:
:[Tried doing this with ANSI C, doubled the number of states in the parser]


Our parser generator did fairly good table optimization so that
similar states could share some common transition information. Don't
know the actual numbers though. But with all the compression the size
of the tables wasn't a problem.


Ken Walter
--

Post a followup to this message

Return to the comp.compilers page.
Search the comp.compilers archives again.