[Scheme-reports] get-output-string on closed ports William D Clinger (30 Jan 2015 15:29 UTC)
Re: [Scheme-reports] get-output-string on closed ports taylanbayirli@gmail.com (30 Jan 2015 21:18 UTC)
Re: [Scheme-reports] get-output-string on closed ports cowan@ccil.org (30 Jan 2015 21:55 UTC)

[Scheme-reports] get-output-string on closed ports William D Clinger 30 Jan 2015 15:25 UTC

Alex Shinn wrote:

> None of SRFI 6, R6RS or R7RS specify what happens when you
> call get-output-string on a string port which has been closed.
>
> John took a survey (http://trac.sacrideo.us/wg/wiki/GetFromClosedStringPort)
> and it looks like the de facto standard is that this "is an error."
> I'm inclined to add an errata to that effect (similarly for
> get-output-bytevector).

Please do.  Reading from or writing to a closed port should always
be an error.

Will Clinger

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