[Scheme-reports] current-XXX-port is binary? Per Bothner (03 Aug 2011 19:04 UTC)
Re: [Scheme-reports] current-XXX-port is binary? John Cowan (03 Aug 2011 19:21 UTC)
Re: [Scheme-reports] current-XXX-port is binary? Per Bothner (03 Aug 2011 19:32 UTC)

[Scheme-reports] current-XXX-port is binary? Per Bothner 03 Aug 2011 19:03 UTC

This seems wrong - these default ports need to be character ports.

For normal "simple" use-cases people are reading and writing text, not
binary.
The nullary read, read-char, peek-char, and read-line default to
current-input-port - which thus should be character ports.
Likewise for write, display, etc.

current-input-port and current-output-port are seldom bound to binary
files: In a Unix-like-pipeline or re-direction, the data are almost
always text.  If standard input is UTF-8, you may need to read multiple
bytes for each read-char.

Note also that in R6RS these are textual ports.

Please fix!
--
	--Per Bothner
per@bothner.com   http://per.bothner.com/

_______________________________________________
Scheme-reports mailing list
Scheme-reports@scheme-reports.org
http://lists.scheme-reports.org/cgi-bin/mailman/listinfo/scheme-reports