From: "Nathaniel Gray" <n8gray@gmail.com>
To: "Jeremy Yallop" <jeremy.yallop@ed.ac.uk>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] ANN: patterns v0.4
Date: Tue, 17 Jun 2008 14:37:53 -0700 [thread overview]
Message-ID: <aee06c9e0806171437s11028137v7d916e64d02c9935@mail.gmail.com> (raw)
In-Reply-To: <48579E13.8070706@ed.ac.uk>
On Tue, Jun 17, 2008 at 4:20 AM, Jeremy Yallop <jeremy.yallop@ed.ac.uk> wrote:
> I'm pleased to announce a new release of `patterns', an OCaml
> framework for writing extensions to pattern matching using Camlp4.
Ooh, very interesting! Have you looked at "active patterns" in F#?
They look really useful and I've been wanting to code them up in
camlp4 for a while now but haven't had the time. It sounds like your
framework could make that much easier.
Cheers,
-n8
--
>>>-- Nathaniel Gray -- Caltech Computer Science ------>
>>>-- Mojave Project -- http://mojave.cs.caltech.edu -->
next prev parent reply other threads:[~2008-06-17 21:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-17 11:20 Jeremy Yallop
2008-06-17 21:37 ` Nathaniel Gray [this message]
2008-06-17 21:58 ` [Caml-list] " Jeremy Yallop
2008-06-20 16:26 ` Richard Jones
2008-06-20 16:56 ` Martin Jambon
2008-06-24 21:27 ` Nathaniel Gray
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=aee06c9e0806171437s11028137v7d916e64d02c9935@mail.gmail.com \
--to=n8gray@gmail.com \
--cc=caml-list@inria.fr \
--cc=jeremy.yallop@ed.ac.uk \
/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