From: Mike Furr <furr@cs.umd.edu>
To: Caml List <caml-list@inria.fr>
Subject: Re: [Caml-list] DSL for handling parsing binary memory structures?
Date: Fri, 18 May 2007 10:56:09 -0400 [thread overview]
Message-ID: <464DBE89.3020801@cs.umd.edu> (raw)
In-Reply-To: <C889307C-0663-414B-A569-4350400BD6A2@cs.uni-sb.de>
Christian Lindig wrote:
> If you are interested in the research aspect of this, Kathleen Fisher
> did interesting work on parsing ad-hoc data (mostly ascii):
[...]
> I remember to have seen something like this for OCaml in the recent
> proceedings of ICFP or POPL but can't remember right now.
I believe you're thinking of PADS/ML (http://www.padsproj.org/) which
was presented at POPL'07 by Fisher et al.
Cheers,
-mike
next prev parent reply other threads:[~2007-05-18 14:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-17 21:21 Richard Jones
2007-05-17 21:30 ` [Caml-list] " Joel Reymont
2007-05-17 21:33 ` Gerd Stolpmann
2007-05-17 23:42 ` Jon Harrop
2007-05-18 7:41 ` Christian Lindig
2007-05-18 14:56 ` Mike Furr [this message]
2007-05-18 14:44 ` Markus Mottl
2007-06-14 11:51 ` Richard Jones
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=464DBE89.3020801@cs.umd.edu \
--to=furr@cs.umd.edu \
--cc=caml-list@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).