From: Jon Harrop <jdh30@cam.ac.uk>
To: caml-list@inria.fr
Subject: [Caml-list] OCaml to C
Date: Fri, 7 May 2004 22:11:12 +0100 [thread overview]
Message-ID: <200405072211.12238.jdh30@cam.ac.uk> (raw)
I was just wondering if there was a compiler which could convert ocaml code
into self-contained, efficient C code which could then be sold? By efficient,
I mean performance comparable to that of native-code compiled ocaml.
I am asking because I think that C code (even unreadable C) may currently be
more commercially viable than ocaml code.
Cheers,
Jon.
-------------------
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
next reply other threads:[~2004-05-07 21:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-07 21:11 Jon Harrop [this message]
2004-05-08 21:37 ` John Goerzen
2004-05-09 8:50 ` Jere Sanisalo
2004-05-09 19:48 ` David Brown
2004-05-10 19:10 ` John Goerzen
2004-05-10 20:03 ` Eric Stokes
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=200405072211.12238.jdh30@cam.ac.uk \
--to=jdh30@cam.ac.uk \
--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).