unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Kevin Ryde <user42@zip.com.au>
Subject: Re: documentation.scm close files
Date: Sat, 24 May 2003 07:20:32 +1000	[thread overview]
Message-ID: <87llwxnyvz.fsf@zip.com.au> (raw)
In-Reply-To: <8765o3rosh.fsf@zagadka.ping.de> (Marius Vollmer's message of "22 May 2003 17:20:30 +0200")

Marius Vollmer <mvo@zagadka.de> writes:
>
> What about saying something about 'with-input-from', etc.
> That's probably the easiest way to ensure that ports are closed even
> in the case of errors.

Except that with-input-from-file and call-with-input-file don't
guarantee to close on error, do they?  :-)

Due to being let's not dynamic-wind of course, if I'm looking at the
right code in r4rs.scm.  Presumably this is deliberate, so
continuations can be captured and still use the port.


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


  reply	other threads:[~2003-05-23 21:20 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-07 22:58 documentation.scm close files Kevin Ryde
2003-05-17 20:07 ` Marius Vollmer
2003-05-18 22:54   ` Kevin Ryde
2003-05-21 22:40     ` Kevin Ryde
2003-05-22  9:59       ` tomas
2003-05-24  1:50         ` Kevin Ryde
2003-05-24  8:46           ` tomas
2003-06-05  1:00             ` Kevin Ryde
2003-05-22 15:20       ` Marius Vollmer
2003-05-23 21:20         ` Kevin Ryde [this message]
2003-06-01 21:02           ` Marius Vollmer
2003-06-05  1:17         ` doco with-input-from-file, with-output-to-file (was: documentation.scm close files) 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=87llwxnyvz.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).