Re: [Scheme-reports] get-output-string on closed ports John Cowan (07 Feb 2015 13:55 UTC)
Re: [Scheme-reports] get-output-string on closed ports Alex Shinn (07 Feb 2015 14:22 UTC)
Re: [Scheme-reports] get-output-string on closed ports John Cowan (07 Feb 2015 19:12 UTC)

Re: [Scheme-reports] get-output-string on closed ports John Cowan 07 Feb 2015 19:08 UTC

Alex Shinn scripsit:

> You can't implement SRFI 6 output string ports without
> non-portable extensions.

Okay, got it.

But R6RS custom ports were designed around the port operations available
in R6RS.  If the editors had decided to use SRFI 6 ports, there probably
would have been an 'extract' operation in custom output ports.

This, by the way, is why I'm not planning to propose a custom port
abstraction for R7RS-large.  There are lots of different kinds of ports in
the wider Scheme world, and every one has some extensions or restrictions
that would have to be taken account of in a custom-port scheme in order
to make it really universal.

--
John Cowan          http://www.ccil.org/~cowan        cowan@ccil.org
Monday we watch-a Firefly's house, but he no come out.  He wasn't home.
Tuesday we go to the ball game, but he fool us.  He no show up.  Wednesday he
go to the ball game, and we fool him.  We no show up.  Thursday was a
double-header.  Nobody show up.  Friday it rained all day.  There was no ball
game, so we stayed home and we listened to it on-a the radio.  --Chicolini

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