From: Jim Farrand <jim@farrand.net>
To: Virgile Prevosto <virgile.prevosto@lip6.fr>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] Inline operators in the revised syntax
Date: Thu, 15 May 2003 10:07:26 +0100 [thread overview]
Message-ID: <20030515090726.GA22198@farrand.net> (raw)
In-Reply-To: <20030513172334.29bae6ca.virgile.prevosto@lip6.fr>
On Tue, May 13, 2003 at 05:23:34PM +0200, Virgile Prevosto wrote:
> Unfortunately for you, the camlp4 manual suggests to use syntax extensions for
> infix operators (http://caml.inria.fr/camlp4/manual/manual007.html)...
Ah, I did look in the manual, honest. Somehow I missed this.
> (* file infix.ml4. compile it with
> Hope this helps,
It helps immensely.
Many thanks,
Jim
--
Jim Farrand
--
-------------------
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
prev parent reply other threads:[~2003-05-15 9:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-13 12:21 Jim Farrand
2003-05-13 15:23 ` Virgile Prevosto
2003-05-15 9:07 ` Jim Farrand [this message]
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=20030515090726.GA22198@farrand.net \
--to=jim@farrand.net \
--cc=caml-list@inria.fr \
--cc=virgile.prevosto@lip6.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).