| From: Ray Dillinger <[email protected]> | Date: Thu, 10 Sep 2009 01:28:58 -0700 | | Can we at least agree that a developer, having read the Thing One | report, should be able to *use* the module system without making | guesses as to how a particular implementation organizes it? R6RS | failed to address finding standard modules in an installed system.
That seems reasonable. Is that what (withdrawn) SRFI-83 was about? | A short list repeated from an earlier post, because damnit, this | is important! | ... | | Mention that implementations are strongly encouraged to | provide and document (unspecified) ways to define "non- | portable" modules that do things not accessible in pure | scheme (such as bitgroveling, file and character I/O, | access the binary format in which scheme's data is held | at runtime, operating sytem calls, etc). "Bitgroveling" is implemented portably (in pure Scheme) in SRFI-60 <http://srfi.schemers.org/srfi-60/srfi-60.html>. Portable (pure Scheme) conversions to and from integer-encoded and IEEE-754-encoded byte-vectors are provided by SLIB <http://people.csail.mit.edu/jaffer/slib_7.html#SEC199>. _______________________________________________ r6rs-discuss mailing list [email protected] http://lists.r6rs.org/cgi-bin/mailman/listinfo/r6rs-discuss
