From: Stefan Israelsson Tampe <stefan.itampe@gmail.com>
To: Chris Vine <vine35792468@gmail.com>
Cc: Guile User <guile-user@gnu.org>
Subject: Re: "Missing" libraries/concepts found in other languages/ecosystems?
Date: Sat, 11 Jul 2020 15:45:16 +0200 [thread overview]
Message-ID: <CAGua6m10va0+x3x=BAc-daMDmif9n0ndXJYaTUk-bfdX86i5pg@mail.gmail.com> (raw)
In-Reply-To: <20200711111400.a4f538669d375d5714cad3f1@gmail.com>
Intersting discussion, thanks. Was able to fix a bug thanks to you.
On Sat, Jul 11, 2020 at 12:14 PM Chris Vine <vine35792468@gmail.com> wrote:
> On Sat, 11 Jul 2020 02:34:22 +0200
> Zelphir Kaltstahl <zelphirkaltstahl@posteo.de> wrote:
> > The comments about exception handling also reminded me of the following
> > blog post:
> >
> > https://blog.sulami.xyz/posts/common-lisp-restarts/
> >
> > Pretty cool concept as well.
> >
> > If there anything like it in Guile or is something like it possible
> > (probably, right?)?
>
> I think common lisp restarts are by and large useless. They rely on
> the assumption that the caller of a procedure which throws knows better
> how to handle an exception arising in that procedure than the procedure
> itself. That is rarely the case. Usually the code at the site of the
> error should do what it can to remedy the problem and then (if it cannot
> be fully rectified) throw an exception which unwinds the stack, for the
> exception to be picked up elsewhere.
>
> That is how most exception systems work. Scheme's continuable
> exceptions are analogous to restarts (albeit only having the exception
> site as their destination) and suffer from the same problem in my
> view. The only place I have seen restarts used in action are in
> building REPLs.
>
>
next prev parent reply other threads:[~2020-07-11 13:45 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.75.1594224014.21222.guile-user@gnu.org>
2020-07-08 18:22 ` "Missing" libraries/concepts found in other languages/ecosystems? Zelphir Kaltstahl
2020-07-09 18:12 ` Leo Butler
2020-07-09 19:34 ` Zelphir Kaltstahl
2020-07-10 7:39 ` Aleix Conchillo Flaqué
2020-07-10 8:14 ` Alex Sassmannshausen
2020-07-10 8:49 ` Catonano
2020-07-10 10:21 ` Chris Vine
2020-07-10 11:20 ` Catonano
2020-07-11 0:19 ` Zelphir Kaltstahl
2020-07-11 0:34 ` Zelphir Kaltstahl
2020-07-11 10:14 ` Chris Vine
2020-07-11 13:45 ` Stefan Israelsson Tampe [this message]
2020-07-11 14:46 ` Linus Björnstam
2020-07-11 10:13 ` Chris Vine
2020-07-11 18:20 ` John Cowan
2020-07-11 22:39 ` Chris Vine
2020-07-11 22:41 ` John Cowan
2020-07-11 23:09 ` Chris Vine
2020-07-12 1:52 ` John Cowan
2020-07-12 20:26 ` Chris Vine
2020-07-13 10:10 ` Chris Vine
2020-07-12 16:08 ` Catonano
2020-07-12 16:10 ` Catonano
2020-07-12 17:46 ` John Cowan
2020-07-12 19:14 ` Chris Vine
2020-07-12 19:32 ` Chris Vine
2020-07-14 10:32 ` Catonano
2020-07-14 11:06 ` Catonano
2020-07-14 16:21 ` Chris Vine
2020-07-12 20:33 ` Zelphir Kaltstahl
2020-07-08 7:38 Simen Endsjø
2020-07-08 8:15 ` Vladimir Zhbanov
2020-07-08 10:08 ` Catonano
2020-07-08 11:29 ` Chris Vine
2020-07-10 12:15 ` Christopher Lam
2020-07-10 15:52 ` Chris Vine
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='CAGua6m10va0+x3x=BAc-daMDmif9n0ndXJYaTUk-bfdX86i5pg@mail.gmail.com' \
--to=stefan.itampe@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).