SCM Repository
View of /sml/trunk/src/cml/doc/ML-Doc/running.mldoc
Parent Directory
|
Revision Log
Revision 287 -
(download)
(annotate)
Sat May 22 20:58:41 1999 UTC (21 years, 8 months ago) by monnier
File size: 1420 byte(s)
Sat May 22 20:58:41 1999 UTC (21 years, 8 months ago) by monnier
File size: 1420 byte(s)
Initial revision
<!-- running.mldoc --> <!DOCTYPE ML-DOC SYSTEM> <COPYRIGHT OWNER="Bell Labs, Lucent Technologies" YEAR=1999> <VERSION VERID="1.0" YEAR=1999 MONTH=1 DAY=8> <TITLE>Porting old programs</TITLE> <SECTION> <HEAD>Running &CML; programs</HEAD> <PP> &CML; does not currently support executing &CML; code from the &SMLNJ; top-level loop. This restriction is because the &SMLNJ; compiler is not thread safe. Instead, one uses the <VALREF STRID="RunCML">RunCML.doit</VALREF> command to run programs. <SECTION LABEL="sec:using-cm"> <HEAD>Using the compilation manager</HEAD> <PP> The recommended way to compile &CML; programs is by using the &SMLNJ; <IT>Compilation Manager</IT> (CM). </SECTION> <SECTION> <HEAD>The <TT>cml-cm</TT> command</HEAD> <PP> The &SMLNJ; installation provides the option of building the <TT>cml-cm</TT> command. This is basically a version of &SMLNJ; that knows how to autoload &CML; components when compiling code that references them. When using <TT>cml-cm</TT>, it is still necessary to use <VALREF STRID="RunCML">RunCML.doit</VALREF> to execute your code. <PP> Unfortunately, there have been problems with the way that the compilation manager initializes autoloaded modules, and thus <TT>cml-cm</TT> has been broken in a number of released versions. Therefore, we recommend that you use the methods described in <SECREF LABEL="sec:using-cm"> above when working with &CML; </SECTION> </SECTION>
root@smlnj-gforge.cs.uchicago.edu | ViewVC Help |
Powered by ViewVC 1.0.0 |