unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: David Kastrup <dak@gnu.org>
To: guile-user@gnu.org
Subject: Re: dynamic-wind
Date: Wed, 05 Jul 2017 10:23:50 +0200	[thread overview]
Message-ID: <87r2xvb8bt.fsf@fencepost.gnu.org> (raw)
In-Reply-To: CAJ98PDxsMStZKFnTuG1VYxpdnTXZcEPh1gmoYOR9BZzj+82fbg@mail.gmail.com

Catonano <catonano@gmail.com> writes:

> Chris,
>
> thank you for your remarks.
>
> Yo're right that I was being caught up by continuations AND that I was
> probably missing the generality of the concept of dynamic wind
>
> And yet, I still want to clarify my point
>
> My point is not that the manual is incomplete or inaccurate
>
> My point is that the manual does not a good job of _introducing_ people to
> the concept of dynamic wind
>
> Especially people wo have not clear in mind a complete map of the use cases
> with relative possible solutions.
>
> The manual tends to be a very good reference for already educated people.
> But it's not as good in educating people in the first place, in my view.

Arguably the manual example is not done well because it does not cater
for the case that other continuations might get invoked from a different
cwd.  So the cwd should get caught in the entry path of the dynamic-wind
rather than outside, something which I find surprisingly hard to do.
It's also not clear to me what the semantics of delimited continuations
are: for those I don't see a formal reason that there couldn't be
several active at the same time, making resource management via
dynamic-wind even more tricky.

-- 
David Kastrup




  reply	other threads:[~2017-07-05  8:23 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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         ` David Kastrup [this message]
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
  -- strict thread matches above, loose matches on Subject: below --
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     ` dynamic-wind Catonano

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=87r2xvb8bt.fsf@fencepost.gnu.org \
    --to=dak@gnu.org \
    --cc=guile-user@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).