From: Richard Jones <rich@annexia.org>
To: caml-list@inria.fr
Subject: DSL for handling parsing binary memory structures?
Date: Thu, 17 May 2007 22:21:57 +0100 [thread overview]
Message-ID: <20070517212157.GA20085@furbychan.cocan.org> (raw)
I wonder if anyone has thought about or developed a domain-specific
language in OCaml for handling the processing of binary structures?
I was thinking of writing something to make system calls into the Xen
hypervisor. The main problem is that the hypervisor takes & returns
binary structures which have very precise size / alignment
requirements, bitfields, etc. (and the requirements change with
versions of the hypervisor). It sounds like the ideal use for a DSL
to describe the binary structure of each version of each call and
automatically build accessors.
Rich.
--
Richard Jones
Red Hat
next reply other threads:[~2007-05-17 21:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-17 21:21 Richard Jones [this message]
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
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=20070517212157.GA20085@furbychan.cocan.org \
--to=rich@annexia.org \
--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