From: Joel Reymont <joelr1@gmail.com>
To: blue storm <bluestorm.dylc@gmail.com>
Cc: "O'Caml Mailing List" <caml-list@yquem.inria.fr>
Subject: Re: [Caml-list] camlp4: precedence, LEFTA, NONA, etc.
Date: Thu, 12 Mar 2009 09:20:23 +0000 [thread overview]
Message-ID: <A902C323-2EFF-4F05-B057-87415E684335@gmail.com> (raw)
In-Reply-To: <527cf6bc0903120213k731ee9f5xb6b1104f12f001b@mail.gmail.com>
On Mar 12, 2009, at 9:13 AM, blue storm wrote:
> You should reverse your rules (starting with the
> higher-precendence construnction instead of the atomic values), and
> possibly split some of your level into different levels (eg. "<" and
> "+") for finer-grained precedence.
I have it reversed then as I thought the rules went in increasing
order of precedence :-(. Thanks for correcting me!
---
http://tinyco.de
Mac, C++, OCaml
next prev parent reply other threads:[~2009-03-12 9:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-11 23:46 Joel Reymont
2009-03-12 9:13 ` [Caml-list] " blue storm
2009-03-12 9:20 ` Joel Reymont [this message]
2009-03-12 9:38 ` Joel Reymont
2009-03-12 11:31 ` Mauricio Fernandez
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=A902C323-2EFF-4F05-B057-87415E684335@gmail.com \
--to=joelr1@gmail.com \
--cc=bluestorm.dylc@gmail.com \
--cc=caml-list@yquem.inria.fr \
/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;
as well as URLs for NNTP newsgroup(s).