From: Jeremy Yallop <jeremy.yallop@ed.ac.uk>
To: Nathaniel Gray <n8gray@gmail.com>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] ANN: patterns v0.4
Date: Tue, 17 Jun 2008 22:58:35 +0100 [thread overview]
Message-ID: <4858338B.3020103@ed.ac.uk> (raw)
In-Reply-To: <aee06c9e0806171437s11028137v7d916e64d02c9935@mail.gmail.com>
Nathaniel Gray wrote:
> 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.
Yes, one of the reason for writing the framework was to be able to
implement F#-like active patterns. I think it should be reasonably
straightforward to do -- in fact, I'd expect design considerations to
take up more time than actual implementation work (although I say that
from the perspective of being already familiar with the "patterns"
framework, of course). If I remember rightly, there's a note at the end
of the ICFP07 active patterns paper about using polymorphic variants to
add active patterns in OCaml, which seems like it might be a good
starting point.
You might also be interested in the "views" feature of Martin Jambon's
"Micmatch", which is along the same lines as active patterns:
http://martin.jambon.free.fr/micmatch-manual.html#htoc10
Jeremy.
next prev parent reply other threads:[~2008-06-17 21:58 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 ` [Caml-list] " Nathaniel Gray
2008-06-17 21:58 ` Jeremy Yallop [this message]
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=4858338B.3020103@ed.ac.uk \
--to=jeremy.yallop@ed.ac.uk \
--cc=caml-list@inria.fr \
--cc=n8gray@gmail.com \
/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