From: Joel Reymont <joelr1@gmail.com>
To: Jon Harrop <jon@ffconsultancy.com>
Cc: caml-list@yquem.inria.fr
Subject: Re: [Caml-list] Function inlining and functor
Date: Mon, 25 Jun 2007 16:36:53 +0100 [thread overview]
Message-ID: <3C66712F-1267-42A5-9D08-BBB9D5D579B1@gmail.com> (raw)
In-Reply-To: <200706251622.21625.jon@ffconsultancy.com>
How would MetaOCaml help here?
On Jun 25, 2007, at 4:22 PM, Jon Harrop wrote:
> Short of generating OCaml code or using MetaOCaml, yes.
>
--
http://topdog.cc - EasyLanguage to C# compiler
http://wagerlabs.com - Blog
next prev parent reply other threads:[~2007-06-25 15:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-25 14:39 Quôc Peyrot
2007-06-25 15:22 ` [Caml-list] " Jon Harrop
2007-06-25 15:36 ` Joel Reymont [this message]
2007-06-25 15:41 ` Basile STARYNKEVITCH
2007-06-25 15:50 ` Quôc Peyrot
2007-06-25 15:58 ` Jon Harrop
2007-06-25 17:04 ` Quôc Peyrot
2007-06-26 3:22 ` Jon Harrop
2007-06-25 16:07 ` Jon Harrop
2007-06-25 20:11 ` Joel Reymont
2007-06-26 3:22 ` Jon Harrop
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=3C66712F-1267-42A5-9D08-BBB9D5D579B1@gmail.com \
--to=joelr1@gmail.com \
--cc=caml-list@yquem.inria.fr \
--cc=jon@ffconsultancy.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;
as well as URLs for NNTP newsgroup(s).