From: rixed@happyleptic.org
To: caml-list@inria.fr
Subject: Re: [Caml-list] ANN: Brand-new BER MetaOCaml for OCaml 4.00.1
Date: Thu, 31 Jan 2013 13:23:02 +0100 [thread overview]
Message-ID: <20130131122301.GA14452@securactive.lan> (raw)
In-Reply-To: <20130131074903.16892.qmail@www1.g3.pair.com>
Once disabled Tk (--no-tk) everything compiled and installed as documented.
Thank you.
I understand that this is very interesting from a research perspective, but
practically meta-programming is only useful as long as performances are the
concern, for these problems when some critical information is not known until
runtime; I can't think of another usage for runtime code specialisation anyway.
So the question that immediately arises is then: why is metaocaml supporting
byte code only? Is a metaocamlopt planned, envisaged, doable, in a galaxy
not too far away?
For the record, I encounter a surprising lot number of occasions, both in pet
projects and at work, where meta-programming is a fruitful approach. Probably
it's such a technique that once you used it once you suddenly discover how hard
you missed it until then. If so then it could be a killer feature for OCaml.
Only recently I've used it from scheme to specialize scheme, from scheme to
specialize C, from python to specialize C, from C to specialize C, from OCaml
to specialize assembly and from OCaml to specialize OCaml (yes, with Printf and
Dynlink). The only 'natural' language for doing such things is of course
Lisp/Scheme, but even in Lisp you don't have many guaranties that the generated
code is safe - you just know that your code fragment is a valid s-expression;
not much that what you got from the printf+compile+dlopen approach). MetaOCaml
looks so much more interesting from a practical point of view!
next prev parent reply other threads:[~2013-01-31 12:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-31 7:49 oleg
2013-01-31 12:23 ` rixed [this message]
2013-02-01 2:12 ` Francois Berenger
2013-02-01 6:53 oleg
2013-02-01 7:53 ` Francois Berenger
2013-02-26 18:09 ` Anil Madhavapeddy
2013-02-19 3:37 bob zhang
2013-02-20 1:51 ` Jacques Carette
2013-02-20 14:03 ` bob zhang
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=20130131122301.GA14452@securactive.lan \
--to=rixed@happyleptic.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;
as well as URLs for NNTP newsgroup(s).