[MLton-commit] r4771

[Vesa Karvonen]

Documentation.
----------------------------------------------------------------------

U   mltonlib/trunk/com/ssh/extended-basis/unstable/readme.txt

----------------------------------------------------------------------

Modified: mltonlib/trunk/com/ssh/extended-basis/unstable/readme.txt
===================================================================
--- mltonlib/trunk/com/ssh/extended-basis/unstable/readme.txt	2006-10-24 23:06:01 UTC (rev 4770)
+++ mltonlib/trunk/com/ssh/extended-basis/unstable/readme.txt	2006-10-25 08:48:40 UTC (rev 4771)
@@ -31,18 +31,18 @@
       (export*.sml).  The contents of this directory should be sufficient
       to understand the extensions provided by this library.
 
-   basis.mlb
+   basis.mlb, basis.cm
 
-      This basis file defines the extended basis library including all of
-      the original basis library.  The idea is that users refer to this
-      instead of the original basis library.
+      These build files define the extended basis library including all of
+      the original basis library.  The idea is that users refer to one of
+      these, depending on the compiler, instead of the original basis
+      library.
 
-   extensions.mlb
+   extensions.mlb, extensions.cm
 
-      This basis file defines only the extensions provided by this
-      library.  Users may refer to this basis file, but this is probably
-      more interesting to maintainers.  You can, for example, run the
-      command
+      These build files define only the extensions provided by this
+      library.  Users may refer to these files, but they are probably more
+      interesting to maintainers.  You can, for example, run the command
 
          mlton -stop tc -show-basis extensions.basis extensions.mlb
 
@@ -59,7 +59,15 @@
       implementation details.  Different compilers implement different
       subsets of the original basis library.
 
+   detail/<COMPILER>/workarounds/
 
+      These directories (e.g. detail/smlnj/workarounds) contain compiler
+      specific workarounds.  The idea is that workarounds are separated
+      from other code so that once a compiler becomes more conforming to
+      the language definition and basis library specification, the
+      workarounds can be easily removed.
+
+
 About Motivation and Scope
 --------------------------