<!DOCTYPE html>
<html lang="en">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<meta name="generator" content="AsciiDoc 8.6.10">
<title>WishList</title>
<link rel="stylesheet" href="./asciidoc.css" type="text/css">
<link rel="stylesheet" href="./pygments.css" type="text/css">


<script type="text/javascript" src="./asciidoc.js"></script>
<script type="text/javascript">
/*<![CDATA[*/
asciidoc.install();
/*]]>*/
</script>
<link rel="stylesheet" href="./mlton.css" type="text/css">
</head>
<body class="article">
<div id="banner">
<div id="banner-home">
<a href="./Home">MLton 20201002</a>
</div>
</div>
<div id="header">
<h1>WishList</h1>
</div>
<div id="content">
<div id="preamble">
<div class="sectionbody">
<div class="paragraph"><p>This page is mainly for recording recurring feature requests.  If you
have a new feature request, you probably want to query interest on one
of the <a href="Contact">mailing lists</a> first.</p></div>
<div class="paragraph"><p>Please be aware of MLton&#8217;s policy on
<a href="LanguageChanges">language changes</a>.  Nonetheless, we hope to provide
support for some of the "immediate" <a href="SuccessorML">SuccessorML</a> proposals in a
future release.</p></div>
</div>
</div>
<div class="sect1">
<h2 id="_support_for_link_options_in_ml_basis_files">Support for link options in ML Basis files</h2>
<div class="sectionbody">
<div class="paragraph"><p>Introduce a mechanism to specify link options in <a href="MLBasis">ML Basis</a>
files.  For example, generalizing a bit, a ML Basis declaration of the
form</p></div>
<div class="listingblock">
<div class="content monospaced">
<pre>option "option"</pre>
</div></div>
<div class="paragraph"><p>could be introduced whose semantics would be the same (as closely as
possible) as if the option string were specified on the compiler
command line.</p></div>
<div class="paragraph"><p>The main motivation for this is that a MLton library that would
introduce bindings (through <a href="ForeignFunctionInterface">FFI</a>) to an
external library could be packaged conveniently as a single MLB file.
For example, to link with library <span class="monospaced">foo</span> the MLB file would simply
contain:</p></div>
<div class="listingblock">
<div class="content monospaced">
<pre>option "-link-opt -lfoo"</pre>
</div></div>
<div class="paragraph"><p>Similar feature requests have been discussed previously on the mailing lists:</p></div>
<div class="ulist"><ul>
<li>
<p>
<a href="http://www.mlton.org/pipermail/mlton/2004-July/025553.html">http://www.mlton.org/pipermail/mlton/2004-July/025553.html</a>
</p>
</li>
<li>
<p>
<a href="http://www.mlton.org/pipermail/mlton/2005-January/026648.html">http://www.mlton.org/pipermail/mlton/2005-January/026648.html</a>
</p>
</li>
</ul></div>
</div>
</div>
</div>
<div id="footnotes"><hr></div>
<div id="footer">
<div id="footer-text">
</div>
<div id="footer-badges">
</div>
</div>
</body>
</html>
