unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Kevin Ryde <user42@zip.com.au>
Subject: tasks call-with-output-string segv
Date: Sat, 13 Sep 2003 11:25:09 +1000	[thread overview]
Message-ID: <87oexpiioa.fsf@zip.com.au> (raw)

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 :-).


_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel


             reply	other threads:[~2003-09-13  1:25 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-13  1:25 Kevin Ryde [this message]
2003-09-13  2:45 ` tasks call-with-output-string segv Rob Browning
2003-09-23 23:51   ` Kevin Ryde
2003-10-01 17:29     ` Rob Browning
2003-10-02  1:21       ` Kevin Ryde
2003-10-02  1:41         ` Rob Browning

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/guile/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87oexpiioa.fsf@zip.com.au \
    --to=user42@zip.com.au \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).