From: Marko Rauhamaa <marko@pacujo.net>
To: Amirouche Boubekki <amirouche.boubekki@gmail.com>
Cc: guile-user@gnu.org
Subject: Re: dynamic-wind
Date: Sun, 09 Jul 2017 00:34:13 +0300 [thread overview]
Message-ID: <87r2xqmx4a.fsf@elektro.pacujo.net> (raw)
In-Reply-To: <CAL7_Mo_jv=U+_novfchtBh7-H8TitNeMxQGEt5zhL8_ZwhxxBw@mail.gmail.com> (Amirouche Boubekki's message of "Sat, 08 Jul 2017 20:03:53 +0000")
Amirouche Boubekki <amirouche.boubekki@gmail.com>:
> I consider dynamic-wind an advanced concept not required for usual
> hacking.
Hm. Python's try/finally has several uses in virtually every program.
Trouble is, Scheme's continuations make it impossible to know when
something is really final. In fact, implementing coroutines and
cooperative multitasking using continuations almost guarantee a repeated
back-and-forth through dynamic-wind.
I strongly suspect Scheme's continuations are more trouble than they are
worth.
Marko
next prev parent reply other threads:[~2017-07-08 21:34 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 ` dynamic-wind David Kastrup
2017-07-08 20:03 ` dynamic-wind Amirouche Boubekki
2017-07-08 21:34 ` Marko Rauhamaa [this message]
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=87r2xqmx4a.fsf@elektro.pacujo.net \
--to=marko@pacujo.net \
--cc=amirouche.boubekki@gmail.com \
--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).