From: Catonano <catonano@gmail.com>
To: Chris Vine <vine35792468@gmail.com>
Cc: guile-user@gnu.org
Subject: Re: dynamic-wind
Date: Mon, 17 Jul 2017 12:04:19 +0200 [thread overview]
Message-ID: <CAJ98PDxoBKRj2RvaT5kxPDED5oP9SJvfvX3ZhtEwNfBfouac_w@mail.gmail.com> (raw)
In-Reply-To: <20170709154928.170385a5@bother.homenet>
I'm so glad for all the people who intervened in this discussion
As this made the subtleties of the issue clearer.
Thank you people !
2017-07-09 16:49 GMT+02:00 Chris Vine <vine35792468@gmail.com>:
> On Sun, 9 Jul 2017 11:09:25 -0300
> Vítor De Araújo <vbuaraujo@sapo.pt> wrote:
>
> unwind-protect is a dynamic-wind without the in guard.
>
>
>
[...]
> As I said, dynamic-wind is a very blunt instrument. I find it useful
> only for very local resources of a particular kind. Releasing a mutex
> is a common case where dynamic-winds are useful (guile has the
> with-mutex form). Ports, as in your example, are not as clear cut.
> Sure, you may want to close the port when you exit a particular block
> in the case of a normal exit, an exception or an escape continuation,
> but do you necessarily want to do so if you might re-enter later and
> closing the port is a destructive operation (it vacates input buffers)?
>
>
In my particular case, I think that abruptly closing the file and then
reopening it would be an acceptable trade off
Freexl functions return error codes when problems arise and those could
help the user in assessing the problem
xls files can be corrupted as different versions of Office can save them in
inconsistent states and there's only so much my library can do
Thank you again, people
next prev parent reply other threads:[~2017-07-17 10:04 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-09 12:59 dynamic-wind Chris Vine
2017-07-09 14:09 ` dynamic-wind Vítor De Araújo
2017-07-09 14:49 ` dynamic-wind Chris Vine
2017-07-17 10:04 ` Catonano [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-06-30 20:33 dynamic-wind Catonano
2017-06-30 21:48 ` dynamic-wind Panicz Maciej Godek
2017-07-02 6:00 ` dynamic-wind Catonano
2017-07-02 6:01 ` dynamic-wind Catonano
2017-07-02 11:58 ` dynamic-wind Chris Vine
2017-07-05 6:14 ` dynamic-wind Catonano
2017-07-05 8:23 ` dynamic-wind David Kastrup
2017-07-08 20:03 ` dynamic-wind Amirouche Boubekki
2017-07-08 21:34 ` dynamic-wind Marko Rauhamaa
2017-07-09 7:21 ` dynamic-wind David Kastrup
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=CAJ98PDxoBKRj2RvaT5kxPDED5oP9SJvfvX3ZhtEwNfBfouac_w@mail.gmail.com \
--to=catonano@gmail.com \
--cc=guile-user@gnu.org \
--cc=vine35792468@gmail.com \
/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).