unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: Nic Ferrier <nferrier@tapsellferrier.co.uk>
Cc: guile-user@gnu.org, Kevin Ryde <user42@zip.com.au>
Subject: Re: closing string output ports?
Date: 07 Oct 2003 20:54:54 +0100	[thread overview]
Message-ID: <87ad8c4ycx.fsf@kanga.tapsellferrier.co.uk> (raw)
In-Reply-To: <87y8vxcd67.fsf@zagadka.ping.de>

Marius Vollmer <mvo@zagadka.de> writes:

> Kevin Ryde <user42@zip.com.au> writes:
> 
> > 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.
> 
> I think it would be useful to be able to get the output string even
> after the port has been closed.  No?


I don't really care about any of that, I just want to know what the
correct procedure should be for a virtual port. Should the virtual
port (close) the underlying port?

This is not documented.

Right now, if the underlying port is closed by the virtual port I get
an exception. 

This seems wrong, it seems like virtual ports should close the
underlying ports... but what do I know?


Nic



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


  reply	other threads:[~2003-10-07 19:54 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-31 21:14 Server-side scripting Marius Vollmer
2003-08-31 21:44 ` closing string output ports? Nic
2003-09-05 23:09   ` Kevin Ryde
2003-09-07 19:14     ` Nic Ferrier
2003-09-07 19:16     ` Nic Ferrier
2003-10-07 14:53     ` Marius Vollmer
2003-10-07 19:54       ` Nic Ferrier [this message]
2003-10-08 13:30         ` Marius Vollmer
2003-10-08 21:19       ` Kevin Ryde

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=87ad8c4ycx.fsf@kanga.tapsellferrier.co.uk \
    --to=nferrier@tapsellferrier.co.uk \
    --cc=guile-user@gnu.org \
    --cc=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).