unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: Chris Vine <vine35792468@gmail.com>
To: guile-user@gnu.org
Subject: Re: "Missing" libraries/concepts found in other languages/ecosystems?
Date: Sun, 12 Jul 2020 21:26:14 +0100	[thread overview]
Message-ID: <20200712212614.78e411c11099106311b294bb@gmail.com> (raw)
In-Reply-To: <CAD2gp_QV5fvhZ+adx9FXTVGngxpx7b15GK3RS334NrsHyauC2w@mail.gmail.com>

On Sat, 11 Jul 2020 21:52:17 -0400
John Cowan <cowan@ccil.org> wrote:
> On Sat, Jul 11, 2020 at 7:10 PM Chris Vine <vine35792468@gmail.com> wrote:
> 
> So when you said "continuable and non-continuable in Scheme are exactly
> > like CL [signal] and error (and its variants)" are you then saying that
> > SIGNAL == continuable (ie raise-continuable in R6RS) and ERROR ==
> > non-continuable (ie raise in R6RS)?
> 
> That is what I meant.
> 
> > In what way do you say that continuable exceptions are not in some sense
> > analogous to common lisp restarts (noting the "in some sense"?
> 
> Well, okay, but in *what* sense?  You made the claim in the first place; I
> think the burden of persuasion lies with you.

I am not sure that burdens is the best way of looking at it.  But my
point of analogy was that with either restarts or continuable
exceptions, the stack is not unwound to the dynamic context in which
with-exception-handler was called, which is the norm in conventional
stack unwinding exception handling systems.  Control returns to (for
continuable exceptions) the point at which the exception was raised or
(for restarts) the relevant restart.



  reply	other threads:[~2020-07-12 20:26 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
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 [this message]
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=20200712212614.78e411c11099106311b294bb@gmail.com \
    --to=vine35792468@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).