[MLton-devel] [Sml-implementers] SML Basis Library webpages (fwd)

[Matthew Fluet]

For good or for ill, there seem to have been quite a number of changes in
the Basis Library since the "Last Modified April 15, 1996" version off of
the SML/NJ web pages.  But, one thing that caught my eye was the
following:

    *  Structures specified as signature instances are matched opaquely,
so all types are abstract unless explicitly specified in the signature. A
note should added to the front matter stating that this is a general
policy for structures matching basis library signatures.

Furthermore, looking at the INTEGER signature, it now reads:
signature  INTEGER
structure Int :> INTEGER
structure FixedInt :> INTEGER  (* OPTIONAL *)
structure LargeInt :> INTEGER
structure Int<N> :> INTEGER  (* OPTIONAL *)
structure Position :> INTEGER
instead of
signature INTEGER
structure Int : INTEGER
structure Int8 : INTEGER
structure FixedInt : INTEGER
structure LargeInt : INTEGER
structure Int{N} : INTEGER
structure Position : INTEGER

That would seem to "solve" the integer problem experienced by Nikos (and
also Dan Wang a while ago).  Similarly, it would easily allow Position.int
to correspond to a 64bit integer (for large files) when the top level
Int.int is still a 32bit integer.

Lots of little changes; it will take a little time to go through
everything.  The only other major change seems to be the inclusion of the
Sockets structures. 


---------- Forwarded message ----------
Date: Thu, 18 Jul 2002 10:58:22 -0500
From: John Reppy <jhr@cs.uchicago.edu>
To: sml-implementers@lists.sourceforge.net
Cc: erg@research.att.com
Subject: [MLton-devel] [Sml-implementers] SML Basis Library webpages


I have put the web pages for the latest version of the SML Basis Library
specification up on the SML implementers site at sourceforge.  The URL
is

	http://SML.sourceforge.net/Basis/index.html

The document includes a history of changes since the previous version.

There are a couple of outstanding technical issues on our list (e.g., clarifying
wide character support and adding a select operation to the Socket structure),
but we expect the specification to be pretty stable otherwise.

Comments and discussion about the specification should be directed to the
SML implementers list (sml-implementers@lists.sourceforge.net).

The HTML linking for identifiers in substructures is currently broken (a bug
in the generating tool), but please let me know of any other problems you
encounter.

	- John



-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
Sml-implementers mailing list
Sml-implementers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sml-implementers


-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
MLton-devel mailing list
MLton-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mlton-devel




-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
MLton-devel mailing list
MLton-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mlton-devel