HCoop / hcoop / debian / mlton.git / blame
? search:
summary | shortlog | log | commit | commitdiff | tree
blob | blame (incremental) | history | HEAD
Import Upstream version 20180207
[hcoop/debian/mlton.git] / doc / guide / localhost / WishList
CommitLineData
7f918cf1
CE		 1<!DOCTYPE html>\r
2<html lang="en">\r
3<head>\r
4<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">\r
5<meta name="generator" content="AsciiDoc 8.6.9">\r
6<title>WishList</title>\r
7<link rel="stylesheet" href="./asciidoc.css" type="text/css">\r
8<link rel="stylesheet" href="./pygments.css" type="text/css">\r
9\r
10\r
11<script type="text/javascript" src="./asciidoc.js"></script>\r
12<script type="text/javascript">\r
13/*<![CDATA[*/\r
14asciidoc.install();\r
15/*]]>*/\r
16</script>\r
17<link rel="stylesheet" href="./mlton.css" type="text/css">\r
18</head>\r
19<body class="article">\r
20<div id="banner">\r
21<div id="banner-home">\r
22<a href="./Home">MLton 20180207</a>\r
23</div>\r
24</div>\r
25<div id="header">\r
26<h1>WishList</h1>\r
27</div>\r
28<div id="content">\r
29<div id="preamble">\r
30<div class="sectionbody">\r
31<div class="paragraph"><p>This page is mainly for recording recurring feature requests. If you\r
32have a new feature request, you probably want to query interest on one\r
33of the <a href="Contact">mailing lists</a> first.</p></div>\r
34<div class="paragraph"><p>Please be aware of MLton&#8217;s policy on\r
35<a href="LanguageChanges">language changes</a>. Nonetheless, we hope to provide\r
36support for some of the "immediate" <a href="SuccessorML">SuccessorML</a> proposals in a\r
37future release.</p></div>\r
38</div>\r
39</div>\r
40<div class="sect1">\r
41<h2 id="_support_for_link_options_in_ml_basis_files">Support for link options in ML Basis files</h2>\r
42<div class="sectionbody">\r
43<div class="paragraph"><p>Introduce a mechanism to specify link options in <a href="MLBasis">ML Basis</a>\r
44files. For example, generalizing a bit, a ML Basis declaration of the\r
45form</p></div>\r
46<div class="listingblock">\r
47<div class="content monospaced">\r
48<pre>option "option"</pre>\r
49</div></div>\r
50<div class="paragraph"><p>could be introduced whose semantics would be the same (as closely as\r
51possible) as if the option string were specified on the compiler\r
52command line.</p></div>\r
53<div class="paragraph"><p>The main motivation for this is that a MLton library that would\r
54introduce bindings (through <a href="ForeignFunctionInterface">FFI</a>) to an\r
55external library could be packaged conveniently as a single MLB file.\r
56For example, to link with library <span class="monospaced">foo</span> the MLB file would simply\r
57contain:</p></div>\r
58<div class="listingblock">\r
59<div class="content monospaced">\r
60<pre>option "-link-opt -lfoo"</pre>\r
61</div></div>\r
62<div class="paragraph"><p>Similar feature requests have been discussed previously on the mailing lists:</p></div>\r
63<div class="ulist"><ul>\r
64<li>\r
65<p>\r
66<a href="http://www.mlton.org/pipermail/mlton/2004-July/025553.html">http://www.mlton.org/pipermail/mlton/2004-July/025553.html</a>\r
67</p>\r
68</li>\r
69<li>\r
70<p>\r
71<a href="http://www.mlton.org/pipermail/mlton/2005-January/026648.html">http://www.mlton.org/pipermail/mlton/2005-January/026648.html</a>\r
72</p>\r
73</li>\r
74</ul></div>\r
75</div>\r
76</div>\r
77</div>\r
78<div id="footnotes"><hr></div>\r
79<div id="footer">\r
80<div id="footer-text">\r
81</div>\r
82<div id="footer-badges">\r
83</div>\r
84</div>\r
85</body>\r
86</html>\r
mlton packaging