From: dsmich@roadrunner.com
To: "'Vijay Marupudi'" <vijay@vijaymarupudi.com>
Cc: 'guile-devel' <guile-devel@gnu.org>
Subject: Re: a cookbook
Date: Fri, 18 Feb 2022 14:32:04 +0000 [thread overview]
Message-ID: <d6bc98bfdf98f6d293afb82684c036cb8bebfe80@webmail> (raw)
[-- Attachment #1: Type: text/plain, Size: 689 bytes --]
> From: "Vijay Marupudi"
> To: "Catonano"
> Subject: Re: a cookbook
>> I'd like to have continuable exceptions covered, though
>>
>> Those are the main departure of Guile from more widespread
exception
>> handling solutions and as far as I can tell something similar is
available
>> only in Common Lisp so drawing experience/intuition from other
languages is
>> more difficult/rare
>
>Sure. I've added new text covering those as well. If you refresh the
>page, it should appear:
>https://vijaymarupudi.com/blog/2022-02-13-error-handling-in-guile.html
This is *really* good. Pull in all the separate pieces and how they
fit together. Great job!
-Dale
[-- Attachment #2: Type: text/html, Size: 887 bytes --]
next reply other threads:[~2022-02-18 14:32 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-18 14:32 dsmich [this message]
2022-02-20 0:48 ` a cookbook Vijay Marupudi
-- strict thread matches above, loose matches on Subject: below --
2022-02-14 22:00 dsmich
2022-02-14 23:06 ` Vijay Marupudi
2022-02-14 6:44 Catonano
2022-02-14 15:47 ` Max Brieiev
2022-02-14 16:56 ` Olivier Dion via Developers list for Guile, the GNU extensibility library
2022-02-16 7:12 ` Catonano
2022-02-14 17:01 ` Vijay Marupudi
2022-02-16 7:21 ` Catonano
2022-02-16 9:54 ` Neil Jerram
2022-02-16 21:13 ` Catonano
2022-02-19 13:18 ` Neil Jerram
2022-02-20 11:07 ` Catonano
2022-02-16 14:19 ` Olivier Dion via Developers list for Guile, the GNU extensibility library
2022-02-17 2:11 ` Vijay Marupudi
2022-02-17 7:00 ` Catonano
2022-02-17 17:34 ` Vijay Marupudi
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=d6bc98bfdf98f6d293afb82684c036cb8bebfe80@webmail \
--to=dsmich@roadrunner.com \
--cc=guile-devel@gnu.org \
--cc=vijay@vijaymarupudi.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).