From: Benjamin Geer <ben@socialtools.net>
To: "Rafael 'Dido' Sevilla" <dido@imperium.ph>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] eliminating shift/reduce conflicts
Date: Fri, 12 Sep 2003 09:36:32 +0100 [thread overview]
Message-ID: <3F618590.3050406@socialtools.net> (raw)
In-Reply-To: <20030912082632.GA9048@imperium.ph>
Rafael 'Dido' Sevilla wrote:
> I however have some rules that
> need to be prefixed by either a single FOO or a foo_list
It might be easier to always parse a foo_list, even if it only contains
one element.
Ben
-------------------
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:36 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 [this message]
2003-09-12 8:40 ` Christian Lindig
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=3F618590.3050406@socialtools.net \
--to=ben@socialtools.net \
--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