caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Joel Reymont <joelr1@gmail.com>
To: OCaml List <caml-list@inria.fr>
Subject: Re: [Caml-list] DSL for handling parsing binary memory structures?
Date: Thu, 17 May 2007 22:30:42 +0100	[thread overview]
Message-ID: <82F1F3DB-2B7A-4D2E-A42E-92DF62B037A2@gmail.com> (raw)
In-Reply-To: <20070517212157.GA20085@furbychan.cocan.org>

Rich,

Take a look at the Erlang bit syntax:

http://tinyurl.com/35rup2

Could something like this be handled by camlp4?

	Joel

On May 17, 2007, at 10:21 PM, Richard Jones wrote:

>
> I wonder if anyone has thought about or developed a domain-specific
> language in OCaml for handling the processing of binary structures?

--
http://wagerlabs.com/






  reply	other threads:[~2007-05-17 21:30 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 ` Joel Reymont [this message]
2007-05-17 21:33 ` [Caml-list] " Gerd Stolpmann
2007-05-17 23:42 ` Jon Harrop
2007-05-18  7:41 ` Christian Lindig
2007-05-18 14:56   ` Mike Furr
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=82F1F3DB-2B7A-4D2E-A42E-92DF62B037A2@gmail.com \
    --to=joelr1@gmail.com \
    --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).