<?xml version="1.0" encoding="ISO-8859-1"?>

<!DOCTYPE message PUBLIC
  "-//MLarc//DTD MLarc output files//EN"
  "../../mlarc.dtd"[
  <!ATTLIST message
    listname CDATA #REQUIRED
    title CDATA #REQUIRED
  >
]>

  <?xml-stylesheet href="../../mlarc.xsl" type="text/xsl"?>


<message 
  url="2002/07/dd1422b2b96cc7b758f0c426faaf6849"
  from="Michael Vanier &lt;mvanier@c...&gt;"
  author="Michael Vanier"
  date="2002-07-23T20:11:24"
  subject="Re: [Caml-list] ocaml for Mono/.NET?"
  prev="2002/07/9c5db8b4fa5d55db5af454a33fbf62e4"
  next="2002/07/95de666352c0f6a57db385835c3792d1"
  prev-in-thread="2002/07/6e80a715ca44af7c0deb60cf011d0a77"
  prev-thread="2002/07/ed6e258ddd3082e1de940b5ff3b369ea"
  next-thread="2002/07/88879fbf18a9124b2bfb027a299f557a"
  root="../../"
  period="month"
  listname="caml-list"
  title="Archives of the Caml mailing list">

<thread subject="[Caml-list] ocaml for Mono/.NET?">
<msg 
  url="2002/07/baaa01d7b8a97fafc2d4150df5a3a6fd"
  from="Michael Vanier &lt;mvanier@c...&gt;"
  author="Michael Vanier"
  date="2002-07-20T14:36:13"
  subject="[Caml-list] ocaml for Mono/.NET?">
<msg 
  url="2002/07/6e80a715ca44af7c0deb60cf011d0a77"
  from="Xavier Leroy &lt;xavier.leroy@i...&gt;"
  author="Xavier Leroy"
  date="2002-07-23T09:00:32"
  subject="Re: [Caml-list] ocaml for Mono/.NET?">
</msg>
<msg 
  url="2002/07/dd1422b2b96cc7b758f0c426faaf6849"
  from="Michael Vanier &lt;mvanier@c...&gt;"
  author="Michael Vanier"
  date="2002-07-23T20:11:24"
  subject="Re: [Caml-list] ocaml for Mono/.NET?">
</msg>
</msg>
</thread>

<contents>

&gt; Date: Sun, 21 Jul 2002 00:25:49 -0400
&gt; From: Travis Bemann &lt;bemann@execpc.com&gt;
&gt; 
&gt; On Wed, Jul 17, 2002 at 12:31:52AM -0700, Michael Vanier wrote:
&gt; &gt;
&gt; &gt; Are there any plans to port ocaml to .NET?  Given that the Mono
&gt; &gt; implementation of .NET is coming along nicely, having an ocaml compiler
&gt; &gt; that can compile to .NET IL would greatly increase ocaml's visibility, not
&gt; &gt; to mention solving some of the library and packaging issues that keep
&gt; &gt; coming up with ocaml.  I know about the F# project, but that implementati=
&gt; on
&gt; &gt; appears to be only for a subset of ocaml, and is controlled by Microsoft.
&gt; &gt; I'd be happier with something from the core ocaml team.  Of course, MY
&gt; &gt; motivation is that I'd like to be able to write nifty graphical apps in
&gt; &gt; ocaml under Linux.  After all, once you learn ocaml, C# is not really very
&gt; &gt; tempting ;-)
&gt; 
&gt; The thing is that this subset is FORCED by the inherent design of the
&gt; CLR/.NET bytecode virtual machine, which doesn't support stuff like
&gt; parameterized modules.  Any attempt to port something like OCaml to
&gt; something like CLR/.NET will only result in its bastardization, and
&gt; thus the loss of many of its features/advantages.
&gt; 

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

</contents>

</message>

