tasks call-with-output-string segv

[Kevin Ryde]

I added to the todo list under 1.6 from what Nic Ferrier reported on
guile-user,

  - call-with-output-string seg faults if its port is closed, eg.
       (call-with-output-string close-port)
    What should happen?  Should this be an error, or should it be
    possible to get the string out of a closed string port?
    [Same situation in the cvs head.]


I don't know what call-with-output-string ought to do in this case,
but a segv is certainly not it :-).