<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:st1="urn:schemas-microsoft-com:office:smarttags" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=Content-Type content="text/html; charset=us-ascii">
<meta name=Generator content="Microsoft Word 11 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]--><o:SmartTagType
namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="PlaceName"/>
<o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags"
name="PlaceType"/>
<o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags"
name="place"/>
<o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags"
name="PersonName"/>
<!--[if !mso]>
<style>
st1\:*{behavior:url(#default#ieooui) }
</style>
<![endif]-->
<style>
<!--
/* Font Definitions */
@font-face
{font-family:Helvetica;
panose-1:2 11 6 4 2 2 2 2 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman";}
a:link, span.MsoHyperlink
{color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{color:purple;
text-decoration:underline;}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:Arial;
color:navy;}
@page Section1
{size:595.3pt 841.9pt;
margin:70.85pt 70.85pt 70.85pt 70.85pt;}
div.Section1
{page:Section1;}
-->
</style>
</head>
<body lang=FR link=blue vlink=purple style='word-wrap: break-word;-khtml-nbsp-mode: space;
-khtml-line-break: after-white-space'>
<div class=Section1>
<p class=MsoNormal><font size=2 color=navy face=Arial><span lang=EN-GB
style='font-size:10.0pt;font-family:Arial;color:navy'>In response to « how
do you mean « does not require it anymore » »,
I guess I should have written “would not” instead. Sorry, I’m
french and my English is not so good.<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span lang=EN-GB
style='font-size:10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span lang=EN-GB
style='font-size:10.0pt;font-family:Arial;color:navy'>The reason why a “real”
64 bits version is interesting for me is that my software uses a lot of RAM and
the more it can address, the better it is.<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span lang=EN-GB
style='font-size:10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span lang=EN-GB
style='font-size:10.0pt;font-family:Arial;color:navy'>There are 3 reasons why I’m
considering porting the MLton compiler. <o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span lang=EN-GB
style='font-size:10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span lang=EN-GB
style='font-size:10.0pt;font-family:Arial;color:navy'>The first one is that I’m
afraid it would be hard for me to contribute to “gcc” whereas it is
much easier for me to contribute to MLton. <o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span lang=EN-GB
style='font-size:10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span lang=EN-GB
style='font-size:10.0pt;font-family:Arial;color:navy'>The second one is that the
Windows version of GNU tools is usually available much later than the Linux
version (probably because the GNU community does not like Windows) and this is
exactly what’s happening here. The 64 bits version of Windows has been released
a long time ago and the GNU tools still don’t support it.<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span lang=EN-GB
style='font-size:10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span lang=EN-GB
style='font-size:10.0pt;font-family:Arial;color:navy'>The third one is that another
compiler for an ML language (Objective Caml) which is available for both MinGW
and the Microsoft tools already supports Win64. As a consequence, I thought it
could be the way forward.<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span lang=EN-GB
style='font-size:10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p>
<div style='border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm 4.0pt'>
<div>
<div class=MsoNormal align=center style='text-align:center'><font size=3
face="Times New Roman"><span style='font-size:12.0pt'>
<hr size=2 width="100%" align=center tabindex=-1>
</span></font></div>
<p class=MsoNormal><b><font size=2 face=Tahoma><span style='font-size:10.0pt;
font-family:Tahoma;font-weight:bold'>From:</span></font></b><font size=2
face=Tahoma><span style='font-size:10.0pt;font-family:Tahoma'> Wesley Terpstra
[mailto:wesley@terpstra.ca] <br>
<b><span style='font-weight:bold'>Sent:</span></b> Thursday, July 26, 2007 2:54
PM<br>
<b><span style='font-weight:bold'>To:</span></b> <st1:PersonName
ProductID="Nicolas Bertolotti" w:st="on">Nicolas Bertolotti</st1:PersonName><br>
<b><span style='font-weight:bold'>Cc:</span></b> mlton@mlton.org<br>
<b><span style='font-weight:bold'>Subject:</span></b> Re: [MLton] Windows port
of MLton using the Microsoft tools (e.g. without MinGW)</span></font><o:p></o:p></p>
</div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'><o:p> </o:p></span></font></p>
<div>
<div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'>On Jul 26, 2007, at 1:17 PM, <st1:PersonName
ProductID="Nicolas Bertolotti" w:st="on">Nicolas Bertolotti</st1:PersonName>
wrote:<o:p></o:p></span></font></p>
</div>
<blockquote style='margin-top:5.0pt;margin-bottom:5.0pt' type=cite><O:SMARTTAGTYPE namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="PlaceName"><O:SMARTTAGTYPE namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="PlaceType"><O:SMARTTAGTYPE namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="place">
<div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
class=apple-style-span><font size=1 color=black face=Helvetica><span
lang=EN-GB style='font-size:9.0pt;font-family:Helvetica;color:black'>I</span></font></span><font
size=2 face=Arial><span lang=EN-GB style='font-size:10.0pt;font-family:Arial'>’m
interested in getting a Win64 version of MLton. Now the 64 bits port for Linux
(and also other targets as I could read some messages about it on the mailing
list) is getting stable, I guess it should not be too complex to update the
MinGW <ST1:PLACE u1:st="on"><ST1:PLACETYPE u1:st="on"><st1:place w:st="on"><st1:PlaceType
w:st="on">port</ST1:PLACETYPE></st1:PlaceType> of <ST1:PLACENAME u1:st="on"><st1:PlaceName
w:st="on">MLton</ST1:PLACENAME></ST1:PLACE></st1:PlaceName></st1:place> for
Win64.</span></font><o:p></o:p></p>
</div>
</blockquote>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'></O:SMARTTAGTYPE></O:SMARTTAGTYPE></O:SMARTTAGTYPE>In contrast to
skaller, I think this is the way forward. MinGW is a very thin wrapper that
provides most of what a UNIX-ish app like MLton needs. As you can still link to
and FFI to MS compiled code, there's little downside.<br>
<br>
<o:p></o:p></span></font></p>
<div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><font
size=2 face=Arial><span lang=EN-GB style='font-size:10.0pt;font-family:Arial'><O:P></O:P><O:SMARTTAGTYPE namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="PlaceName"><O:SMARTTAGTYPE namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="PlaceType"><O:SMARTTAGTYPE namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="place"><O:P>Unfortunately,
MinGW is not yet available for Win64. The gcc port is definitely not stable
(the binutils seem to run fine) and the MinGW headers and libraries are still
experimental.</O:P></span></font><o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'></O:SMARTTAGTYPE></O:SMARTTAGTYPE></O:SMARTTAGTYPE>Are you in a hurry?
I'm sure that gcc for windows will work in the near future. Fixing any problems
in the MinGW headers once gcc works seems like much less work than trying to
port MLton and its dependencies to MS's compiler.<o:p></o:p></span></font></p>
</div>
<blockquote style='margin-top:5.0pt;margin-bottom:5.0pt' type=cite><O:SMARTTAGTYPE namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="PlaceName"><O:SMARTTAGTYPE namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="PlaceType"><O:SMARTTAGTYPE namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="place">
<div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><font
size=2 face=Arial><span lang=EN-GB style='font-size:10.0pt;font-family:Arial'><O:P>The
fact we need MinGW to use MLton on Windows seems to be an obstacle in terms of
portability and the fact it does not require it anymore would make life (at
least mine ;-)) easier.</O:P></span></font><o:p></o:p></p>
</div>
</blockquote>
<div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'></O:SMARTTAGTYPE></O:SMARTTAGTYPE></O:SMARTTAGTYPE>How do you mean
"does not require it anymore"? I'd not heard of anyone porting MLton
to a non-gcc compiler?<o:p></o:p></span></font></p>
</div>
</div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'><o:p> </o:p></span></font></p>
<div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'>In the meantime, 32-bit applications still work great (and use less
memory). So unless need >2GB of memory in a MLton app, you're not missing
much.<o:p></o:p></span></font></p>
</div>
<div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'><o:p> </o:p></span></font></p>
</div>
</div>
</div>
</body>
</html>