From: Zelphir Kaltstahl <zelphirkaltstahl@posteo.de>
To: divoplade <d@divoplade.fr>
Cc: guile-user <guile-user@gnu.org>
Subject: Re: Example of defining and using exceptions
Date: Sat, 24 Oct 2020 20:07:54 +0200 [thread overview]
Message-ID: <384f358f-f8a8-4011-2760-42bf11b6db94@posteo.de> (raw)
In-Reply-To: <3866ed5d0547922d0752e553b25016b419f379ac.camel@divoplade.fr>
Hi divoplade,
although this might be incomplete, I hope this can help you:
https://notabug.org/ZelphirKaltstahl/guile-examples/src/master/exception-handling.
Best regards,
Zelphir
On 10/24/20 10:48 AM, divoplade wrote:
> Dear guile hackers,
>
> I would like to use the "new" exception style in guile, i.e. define-
> exception-type and friends. However, I don't understand how compound
> exceptions work. Do you have an example of using exceptions, showing
> what compound exceptions can bring?
>
> Best regards,
>
> divoplade
>
>
--
repositories: https://notabug.org/ZelphirKaltstahl
prev parent reply other threads:[~2020-10-24 18:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-24 8:48 Example of defining and using exceptions divoplade
2020-10-24 18:07 ` Zelphir Kaltstahl [this message]
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=384f358f-f8a8-4011-2760-42bf11b6db94@posteo.de \
--to=zelphirkaltstahl@posteo.de \
--cc=d@divoplade.fr \
--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).