From: ludo@gnu.org (Ludovic Courtès)
To: guile-devel@gnu.org
Subject: Re: [PATCH 3/4] Work towards a more complete implementation of `(rnrs io ports)'
Date: Wed, 24 Nov 2010 21:24:28 +0100 [thread overview]
Message-ID: <878w0i79mr.fsf@gnu.org> (raw)
In-Reply-To: 87d3pvli4p.fsf@delenn.lan
Hi,
Andreas Rottmann <a.rottmann@gmx.at> writes:
> To quote that paragraph about `call-with-port':
>
> ,----
> | Proc must accept one argument. The call-with-port procedure calls proc
> | with port as an argument. If proc returns, port is closed automatically
> | and the values returned by proc are returned. If proc does not return,
> | port is not closed automatically, except perhaps when it is possible to
> | prove that port will never again be used for an input or output
> | operation.
> `----
>
> I interpreted that the way I did based on the question of what should
> happen when `proc' throws an exception (or otherwise invokes a
> continuation that makes it leave its current dynamic extent). To me, it
> seems that in this case, `proc' does not _return_, and hence the port
> should not be closed. Just to clarify, by a procedure "returning", I
> understand delivering a value (or values) to its continuation, which
> does not happen if the procedure invokes some arbitrary (other)
> continuation.
Oh, yes, makes sense to me now.
Thanks,
Ludo’.
next prev parent reply other threads:[~2010-11-24 20:24 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-15 21:45 Some work on the R6RS I/O libraries Andreas Rottmann
2010-11-19 23:59 ` Ludovic Courtès
2010-11-20 17:40 ` [PATCH 1/4] Fix missing port-table locking and bytevector output port segfault Andreas Rottmann
2010-11-20 22:43 ` Ludovic Courtès
2010-11-20 17:40 ` [PATCH 2/4] Add implementation of "transcoded ports" Andreas Rottmann
2010-11-20 22:52 ` Ludovic Courtès
2010-11-21 22:07 ` Andreas Rottmann
2010-11-21 22:17 ` [PATCH 1/4] Turn `(rnrs io ports)' into an R6RS library Andreas Rottmann
2010-11-21 22:17 ` [PATCH 2/4] Reorganize the R6RS I/O condition types Andreas Rottmann
2010-11-21 22:17 ` [PATCH 3/4] Work towards a more complete implementation of `(rnrs io ports)' Andreas Rottmann
2010-11-23 21:13 ` Ludovic Courtès
2010-11-23 23:44 ` Andreas Rottmann
2010-11-24 20:24 ` Ludovic Courtès [this message]
2010-11-21 22:17 ` [PATCH 4/4] Add implementation of "transcoded ports" Andreas Rottmann
2010-11-24 22:29 ` Ludovic Courtès
2010-11-25 0:08 ` Andreas Rottmann
2010-11-25 21:15 ` Ludovic Courtès
2010-11-20 17:40 ` [PATCH 3/4] Reorganize the R6RS I/O condition types Andreas Rottmann
2010-11-20 17:40 ` [PATCH 4/4] Work towards a more complete implementation of `(rnrs io ports)' Andreas Rottmann
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=878w0i79mr.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guile-devel@gnu.org \
/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).