[hcoop/debian/mlton.git] / doc / guide / localhost / MLBasis

<!DOCTYPE html>\r
<html lang="en">\r
<head>\r
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">\r
<meta name="generator" content="AsciiDoc 8.6.9">\r
<title>MLBasis</title>\r
<link rel="stylesheet" href="./asciidoc.css" type="text/css">\r
<link rel="stylesheet" href="./pygments.css" type="text/css">\r
\r
\r
<script type="text/javascript" src="./asciidoc.js"></script>\r
<script type="text/javascript">\r
/*<![CDATA[*/\r
asciidoc.install();\r
/*]]>*/\r
</script>\r
<link rel="stylesheet" href="./mlton.css" type="text/css">\r
</head>\r
<body class="article">\r
<div id="banner">\r
<div id="banner-home">\r
<a href="./Home">MLton 20180207</a>\r
</div>\r
</div>\r
<div id="header">\r
<h1>MLBasis</h1>\r
</div>\r
<div id="content">\r
<div id="preamble">\r
<div class="sectionbody">\r
<div class="paragraph"><p>The ML Basis system extends <a href="StandardML">Standard ML</a> to support\r
programming-in-the-very-large, namespace management at the module\r
level, separate delivery of library sources, and more.  While Standard\r
ML modules are a sophisticated language for programming-in-the-large,\r
it is difficult, if not impossible, to accomplish a number of routine\r
namespace management operations when a program draws upon multiple\r
libraries provided by different vendors.</p></div>\r
<div class="paragraph"><p>The ML Basis system is a simple, yet powerful, approach that builds\r
upon the programmer&#8217;s intuitive notion (and\r
<a href="DefinitionOfStandardML"> The Definition of Standard ML (Revised)</a>'s\r
formal notion) of the top-level environment (a <em>basis</em>).  The system\r
is designed as a natural extension of <a href="StandardML"> Standard ML</a>; the\r
formal specification of the ML Basis system\r
(<a href="MLBasis.attachments/mlb-formal.pdf"><span class="monospaced">mlb-formal.pdf</span></a>) is given in the style\r
of the Definition.</p></div>\r
<div class="paragraph"><p>Here are some of the key features of the ML Basis system:</p></div>\r
<div class="olist arabic"><ol class="arabic">\r
<li>\r
<p>\r
Explicit file order: The order of files (and, hence, the order of\r
evaluation) in the program is explicit.  The ML Basis system&#8217;s\r
semantics are structured in such a way that for any well-formed\r
project, there will be exactly one possible interpretation of the\r
project&#8217;s syntax, static semantics, and dynamic semantics.\r
</p>\r
</li>\r
<li>\r
<p>\r
Implicit dependencies: A source file (corresponding to an SML\r
top-level declaration) is elaborated in the environment described by\r
preceding declarations.  It is not necessary to explicitly list the\r
dependencies of a file.\r
</p>\r
</li>\r
<li>\r
<p>\r
Scoping and renaming: The ML Basis system provides mechanisms for\r
limiting the scope of (i.e, hiding) and renaming identifiers.\r
</p>\r
</li>\r
<li>\r
<p>\r
No naming convention for finding the file that defines a module.\r
To import a module, its defining file must appear in some ML Basis\r
file.\r
</p>\r
</li>\r
</ol></div>\r
</div>\r
</div>\r
<div class="sect1">\r
<h2 id="_next_steps">Next steps</h2>\r
<div class="sectionbody">\r
<div class="ulist"><ul>\r
<li>\r
<p>\r
<a href="MLBasisSyntaxAndSemantics">MLBasisSyntaxAndSemantics</a>\r
</p>\r
</li>\r
<li>\r
<p>\r
<a href="MLBasisExamples">MLBasisExamples</a>\r
</p>\r
</li>\r
<li>\r
<p>\r
<a href="MLBasisPathMap">MLBasisPathMap</a>\r
</p>\r
</li>\r
<li>\r
<p>\r
<a href="MLBasisAnnotations">MLBasisAnnotations</a>\r
</p>\r
</li>\r
<li>\r
<p>\r
<a href="MLBasisAvailableLibraries">MLBasisAvailableLibraries</a>\r
</p>\r
</li>\r
</ul></div>\r
</div>\r
</div>\r
</div>\r
<div id="footnotes"><hr></div>\r
<div id="footer">\r
<div id="footer-text">\r
</div>\r
<div id="footer-badges">\r
</div>\r
</div>\r
</body>\r
</html>\r
Commit	Line	Data
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>MLBasis</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
	14	asciidoc.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>MLBasis</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>The ML Basis system extends <a href="StandardML">Standard ML</a> to support\r
	32	programming-in-the-very-large, namespace management at the module\r
	33	level, separate delivery of library sources, and more. While Standard\r
	34	ML modules are a sophisticated language for programming-in-the-large,\r
	35	it is difficult, if not impossible, to accomplish a number of routine\r
	36	namespace management operations when a program draws upon multiple\r
	37	libraries provided by different vendors.</p></div>\r
	38	<div class="paragraph"><p>The ML Basis system is a simple, yet powerful, approach that builds\r
	39	upon the programmer’s intuitive notion (and\r
	40	<a href="DefinitionOfStandardML"> The Definition of Standard ML (Revised)</a>'s\r
	41	formal notion) of the top-level environment (a <em>basis</em>). The system\r
	42	is designed as a natural extension of <a href="StandardML"> Standard ML</a>; the\r
	43	formal specification of the ML Basis system\r
	44	(<a href="MLBasis.attachments/mlb-formal.pdf"><span class="monospaced">mlb-formal.pdf</span></a>) is given in the style\r
	45	of the Definition.</p></div>\r
	46	<div class="paragraph"><p>Here are some of the key features of the ML Basis system:</p></div>\r
	47	<div class="olist arabic"><ol class="arabic">\r
	48	<li>\r
	49	<p>\r
	50	Explicit file order: The order of files (and, hence, the order of\r
	51	evaluation) in the program is explicit. The ML Basis system’s\r
	52	semantics are structured in such a way that for any well-formed\r
	53	project, there will be exactly one possible interpretation of the\r
	54	project’s syntax, static semantics, and dynamic semantics.\r
	55	</p>\r
	56	</li>\r
	57	<li>\r
	58	<p>\r
	59	Implicit dependencies: A source file (corresponding to an SML\r
	60	top-level declaration) is elaborated in the environment described by\r
	61	preceding declarations. It is not necessary to explicitly list the\r
	62	dependencies of a file.\r
	63	</p>\r
	64	</li>\r
65	<li>\r
66	<p>\r
67	Scoping and renaming: The ML Basis system provides mechanisms for\r
68	limiting the scope of (i.e, hiding) and renaming identifiers.\r
69	</p>\r
70	</li>\r
71	<li>\r
72	<p>\r
73	No naming convention for finding the file that defines a module.\r
74	To import a module, its defining file must appear in some ML Basis\r
75	file.\r
76	</p>\r
77	</li>\r
78	</ol></div>\r
79	</div>\r
80	</div>\r
81	<div class="sect1">\r
82	<h2 id="_next_steps">Next steps</h2>\r
83	<div class="sectionbody">\r
84	<div class="ulist"><ul>\r
85	<li>\r
86	<p>\r
87	<a href="MLBasisSyntaxAndSemantics">MLBasisSyntaxAndSemantics</a>\r
88	</p>\r
89	</li>\r
90	<li>\r
91	<p>\r
92	<a href="MLBasisExamples">MLBasisExamples</a>\r
93	</p>\r
94	</li>\r
95	<li>\r
96	<p>\r
97	<a href="MLBasisPathMap">MLBasisPathMap</a>\r
98	</p>\r
99	</li>\r
100	<li>\r
101	<p>\r
102	<a href="MLBasisAnnotations">MLBasisAnnotations</a>\r
103	</p>\r
104	</li>\r
105	<li>\r
106	<p>\r
107	<a href="MLBasisAvailableLibraries">MLBasisAvailableLibraries</a>\r
108	</p>\r
109	</li>\r
110	</ul></div>\r
111	</div>\r
112	</div>\r
113	</div>\r
114	<div id="footnotes"><hr></div>\r
115	<div id="footer">\r
116	<div id="footer-text">\r
117	</div>\r
118	<div id="footer-badges">\r
119	</div>\r
120	</div>\r
121	</body>\r
122	</html>\r