unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: Zelphir Kaltstahl <zelphirkaltstahl@posteo.de>
To: Maxime Devos <maximedevos@telenet.be>
Cc: guile-user <guile-user@gnu.org>
Subject: Re: Exception handling - symbol for encoding exception type?
Date: Thu,  7 Apr 2022 21:39:07 +0000	[thread overview]
Message-ID: <90acfe56-eb85-47f4-a981-5346cdf8f739@posteo.de> (raw)
In-Reply-To: <dadf836c018bdaf364d2653da6252c301459deae.camel@telenet.be>

Hi Maxime!

On 3/8/22 19:20, Maxime Devos wrote:
> Zelphir Kaltstahl schreef op di 08-03-2022 om 17:11 [+0000]:
>>         (make-non-continuable-error)
> IIRC, 'make-non-continuable-error' indicates that someone tried to
> continue into a raise-exception that wasn't continuable.  It does not
> make things non-continuable, it just states that someone tried to
> continue anyway.
>
> What you seem to need is (raise-exception ... #:continuable? #false).
> However, #:continuable? #false is the default.
>
> Greetings,
> Maxime.

I am late, but I finally get around to it: Thanks for this hint and explanation.

Best regards,
Zelphir

-- 
repositories: https://notabug.org/ZelphirKaltstahl




  reply	other threads:[~2022-04-07 21:39 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-08 17:11 Exception handling - symbol for encoding exception type? Zelphir Kaltstahl
2022-03-08 17:48 ` Vivien Kraus
2022-03-08 18:18 ` Maxime Devos
2022-03-08 18:20 ` Maxime Devos
2022-04-07 21:39   ` Zelphir Kaltstahl [this message]
2022-03-08 18:22 ` Maxime Devos
2022-03-08 19:07 ` Olivier Dion via General Guile related discussions

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=90acfe56-eb85-47f4-a981-5346cdf8f739@posteo.de \
    --to=zelphirkaltstahl@posteo.de \
    --cc=guile-user@gnu.org \
    --cc=maximedevos@telenet.be \
    /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).