From: "Andrew Kennedy" <akenn@microsoft.com>
To: "Michael Vanier" <mvanier@cs.caltech.edu>, <bemann@execpc.com>
Cc: <caml-list@inria.fr>
Subject: RE: [Caml-list] ocaml for Mono/.NET?
Date: Thu, 25 Jul 2002 21:33:29 -0700 [thread overview]
Message-ID: <BCDB2C3F59F5744EBE37C715D66E779CE31CFA@red-msg-04.redmond.corp.microsoft.com> (raw)
Our SML.NET implementation compiles the functors of Standard ML by
expanding them at compile-time.
There *is* a tension between supporting all the features of the source
language and at the same time providing smooth inter-operation with
other .NET languages. Hopefully for functional languages this tension
will lessen when parametric polymorphism is supported by the .NET CLR.
- Andrew.
-----Original Message-----
From: Michael Vanier [mailto:mvanier@cs.caltech.edu]
Sent: 21 July 2002 00:27
To: bemann@execpc.com
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] ocaml for Mono/.NET?
> Date: Sun, 21 Jul 2002 00:25:49 -0400
> From: Travis Bemann <bemann@execpc.com>
>
> On Wed, Jul 17, 2002 at 12:31:52AM -0700, Michael Vanier wrote:
> >
> > Are there any plans to port ocaml to .NET? Given that the Mono
> > implementation of .NET is coming along nicely, having an ocaml
compiler
> > that can compile to .NET IL would greatly increase ocaml's
visibility, not
> > to mention solving some of the library and packaging issues that
keep
> > coming up with ocaml. I know about the F# project, but that
implementati=
> on
> > appears to be only for a subset of ocaml, and is controlled by
Microsoft.
> > I'd be happier with something from the core ocaml team. Of course,
MY
> > motivation is that I'd like to be able to write nifty graphical apps
in
> > ocaml under Linux. After all, once you learn ocaml, C# is not
really very
> > tempting ;-)
>
> The thing is that this subset is FORCED by the inherent design of the
> CLR/.NET bytecode virtual machine, which doesn't support stuff like
> parameterized modules. Any attempt to port something like OCaml to
> something like CLR/.NET will only result in its bastardization, and
> thus the loss of many of its features/advantages.
>
That's interesting, considering that standard ML is one of the languages
supposedly targeted by the common language runtime (by which I mean that
the SML team was consulted on what features they would need in the
intermediate language in order to support SML). Doesn't SML have
parameterized modules?
Mike
-------------------
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
-------------------
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:[~2002-07-26 4:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-26 4:33 Andrew Kennedy [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-07-17 7:31 Michael Vanier
[not found] ` <20020721002549.A752@execpc.com>
2002-07-21 7:27 ` Michael Vanier
2002-07-23 9:00 ` Xavier Leroy
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=BCDB2C3F59F5744EBE37C715D66E779CE31CFA@red-msg-04.redmond.corp.microsoft.com \
--to=akenn@microsoft.com \
--cc=bemann@execpc.com \
--cc=caml-list@inria.fr \
--cc=mvanier@cs.caltech.edu \
/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