Re: closing string output ports?

[Kevin Ryde]

Nic <address@hidden> writes:
>
> (call-with-output-string
>    (lambda (prt)
>      (display "pah!" prt)
>      (close-port prt)))

Looks like a gremlin in call-with-output-string, it doesn't seem to
guard against its port having been closed.

Dunno what it ought to do in that case, maybe throw an error, maybe
return #f or unspecified.

> Should my soft port close-port impl call close-port on the underlying
> port?

It looks like one isn't meant to close a string port before getting
the result.  The manual doesn't seem to say anything about that
though.