From: Brian Smith <brian-l-smith@uiowa.edu>
Cc: OCaml Mailing list <caml-list@inria.fr>
Subject: O'Caml, JVM, and .NET (was Re: [Caml-list] F#)
Date: Sun, 09 Jun 2002 12:04:03 -0500 [thread overview]
Message-ID: <3D038A83.904@uiowa.edu> (raw)
In-Reply-To: <BCDB2C3F59F5744EBE37C715D66E779C0481E206@red-msg-04.redmond.corp.microsoft.com>
I have looked over the archives and I have seen there has been a fair
amount of discussion on compiling O'Caml to JVM bytecode or the .NET
intermediate language. The primary advantage cited seems to be reuse of
.NET and J2SE/J2EE libraries. People have said that compiling O'Caml to
JVM/.NET is difficult because of mismatches in the .NET/JVM object model
and the O'Caml object model.
But, would it be easier to reuse Java libraries by:
* extending the O'Caml runtime to be able to interpret JVM bytecodes
(i.e. be able to dynamically link to *.class and *.jar files), or
* cross-compiling JVM bytecode into O'Caml bytecode, or
* compiling Java source code into O'Caml bytecode
Similar questions apply for .NET, of course.
I would like to do more programming in O'Caml but it is sometimes
difficult to choose O'Caml over Java when there are _so_ many libraries
available for Java, with more added seemingly every day.
Thanks,
Brian
Don Syme wrote:
> I chose to implement a core Caml compiler for .NET partly to test out
> generics, but also because I want to be able to program against .NET
> libraries using the language I love to program in, and reuse the
> libraries and techniques I've developed. I guess it's possible I'll
> get a bit of flak from the Caml community about F#.
-------------------
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
prev parent reply other threads:[~2002-06-09 17:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-08 23:04 [Caml-list] F# Don Syme
2002-06-09 17:04 ` Brian Smith [this message]
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=3D038A83.904@uiowa.edu \
--to=brian-l-smith@uiowa.edu \
--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).