HCoop / hcoop / debian / mlton.git / blame
| Commit | Line | Data |
|---|---|---|
| 7f918cf1 CE |
1 | WishList |
| 2 | ======== | |
| 3 | ||
| 4 | This page is mainly for recording recurring feature requests. If you | |
| 5 | have a new feature request, you probably want to query interest on one | |
| 6 | of the <:Contact:mailing lists> first. | |
| 7 | ||
| 8 | Please be aware of MLton's policy on | |
| 9 | <:LanguageChanges:language changes>. Nonetheless, we hope to provide | |
| 10 | support for some of the "immediate" <:SuccessorML:> proposals in a | |
| 11 | future release. | |
| 12 | ||
| 13 | ||
| 14 | == Support for link options in ML Basis files == | |
| 15 | ||
| 16 | Introduce a mechanism to specify link options in <:MLBasis:ML Basis> | |
| 17 | files. For example, generalizing a bit, a ML Basis declaration of the | |
| 18 | form | |
| 19 | ||
| 20 | ---- | |
| 21 | option "option" | |
| 22 | ---- | |
| 23 | ||
| 24 | could be introduced whose semantics would be the same (as closely as | |
| 25 | possible) as if the option string were specified on the compiler | |
| 26 | command line. | |
| 27 | ||
| 28 | The main motivation for this is that a MLton library that would | |
| 29 | introduce bindings (through <:ForeignFunctionInterface:FFI>) to an | |
| 30 | external library could be packaged conveniently as a single MLB file. | |
| 31 | For example, to link with library `foo` the MLB file would simply | |
| 32 | contain: | |
| 33 | ||
| 34 | ---- | |
| 35 | option "-link-opt -lfoo" | |
| 36 | ---- | |
| 37 | ||
| 38 | Similar feature requests have been discussed previously on the mailing lists: | |
| 39 | ||
| 40 | * http://www.mlton.org/pipermail/mlton/2004-July/025553.html | |
| 41 | * http://www.mlton.org/pipermail/mlton/2005-January/026648.html |