suzanne.soy/racket
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

note custom-port problems in R6RS conformance description

Browse Source 
svn: r11411
This commit is contained in:
Matthew Flatt 2008-08-25 12:34:25 +00:00
parent cc3062f201
commit f530f6c9ed
1 changed files with 12 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
collects/r6rs/scribblings/r6rs.scrbl
View File

@ -303,6 +303,18 @@ several known ways:
is referenced before it is bound, an exception is not raised; is referenced before it is bound, an exception is not raised;
instead, the reference produces @|undefined-const|.} instead, the reference produces @|undefined-const|.}
@item{A custom textual port must represent positions using integers,
and the positions must correspond to bytes in a UTF-8 encoding
of the port's data. For custom ports (byte or character) that
support both input and output, beware that buffered input can
create a mismatch between the position implemented by the
custom procedures and the port's current position; the result
from a custom position procedure is automatically adjusted to
account for buffering, and setting the port's position flushes
all buffered bytes, but writing after a read does @emph{not}
automatically reset the port's position to counteract the
effects of buffering.}
@item{The bindings in a namespace produced by @scheme[null-environment] @item{The bindings in a namespace produced by @scheme[null-environment]
or @scheme[scheme-report-environment] correspond to @|r5rs| bindings or @scheme[scheme-report-environment] correspond to @|r5rs| bindings
instead of @|r6rs| bindings. In particular, @scheme[=>], @scheme[else], instead of @|r6rs| bindings. In particular, @scheme[=>], @scheme[else],