From: Christian Lindig <lindig@cs.uni-sb.de>
To: "Rafael 'Dido' Sevilla" <dido@imperium.ph>
Cc: Caml Mailing List <caml-list@inria.fr>
Subject: Re: [Caml-list] eliminating shift/reduce conflicts
Date: Fri, 12 Sep 2003 10:40:47 +0200 [thread overview]
Message-ID: <20030912084047.GB31078@st> (raw)
In-Reply-To: <20030912082632.GA9048@imperium.ph>
On Fri, Sep 12, 2003 at 04:26:32PM +0800, Rafael 'Dido' Sevilla wrote:
> I have an ocamlyacc grammar that contains productions that look like:
>
> foo_list: FOO { [$1] }
> | foo_list COMMA FOO { $3 :: $1 }
> ;
>
> bar: foo_list COLON xyzzy { ... }
> baz: FOO COLON yzzyx { ... }
>
> This of course produces a shift/reduce conflict, and shifting fails to
> parse the 'bar' correctly.
I have tried to build a little grammar to reproduce your problem but
failed. If you could post a small stand-alone grammar for OCamlyacc
somebody might be able to help you. The easiest way to remove conflicts
in Yacc is to alter the precedence of individual tokens using %left or
%right. Read the section about 'Declarations' in the OCamlYacc manual.
My toy grammar is below.
%token COLON COMMA FOO ETC
%start start
%type<unit>start
%%
start
: foo_list ETC bar ETC baz {}
;
foo_list
: FOO {}
| foo_list COMMA FOO {}
;
bar
: foo_list COLON ETC {}
;
baz
: FOO COLON ETC {}
%%
-- Christian
--
Christian Lindig http://www.st.cs.uni-sb.de/~lindig/
-------------------
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
next prev parent reply other threads:[~2003-09-12 8:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-12 8:26 Rafael 'Dido' Sevilla
2003-09-12 8:36 ` Benjamin Geer
2003-09-12 8:40 ` Christian Lindig [this message]
2003-09-12 9:22 ` Rafael 'Dido' Sevilla
2003-09-12 9:29 ` Eckart Goehler
2003-09-12 10:46 ` Remi Vanicat
2003-09-12 14:04 ` Ken Rose
2003-09-12 14:55 ` Eric C. Cooper
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20030912084047.GB31078@st \
--to=lindig@cs.uni-sb.de \
--cc=caml-list@inria.fr \
--cc=dido@imperium.ph \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox