From: Gregory Heytings <gregory@heytings.org>
To: "Mattias Engdegård" <mattiase@acm.org>
Cc: Filipp Gunbin <fgunbin@fastmail.fm>,
Lars Ingebrigtsen <larsi@gnus.org>,
Stefan Kangas <stefan@marxist.se>,
Stefan Monnier <monnier@iro.umontreal.ca>,
47677@debbugs.gnu.org
Subject: bug#47677: [PATCH] condition-case success continuation
Date: Tue, 27 Apr 2021 19:00:53 +0000 [thread overview]
Message-ID: <fe6aee4ffd34e15fb051@heytings.org> (raw)
In-Reply-To: <A6CF88A5-CBD8-4691-A4D6-1255B098CC38@acm.org>
>
> Unrelated to your comment: since several people have misunderstood the
> proposal, I'm closing the bug
>
I guess you did not see my previous post in this bug thread.
This bug should not be closed. I agree with Richard and Eli, it is not
necessary to add that feature to Elisp, the more so as it can be
implemented with a short macro:
(defmacro if-success (var action continuation &rest handlers)
"Regain control when an error is signaled, otherwise continue.
Execute ACTION and, if no error happened, CONTINUATION, with VAR
bound to the return value of ACTION.
Otherwise, execute the appropriate HANDLER, with VAR bound to
(ERROR-SYMBOL . SIGNAL-DATA)."
`(catch 'success-case-failure
((lambda (,var) ,continuation)
(catch 'success-case-success
(throw 'success-case-failure
(condition-case ,var
(throw 'success-case-success ,action) ,@handlers))))))
next prev parent reply other threads:[~2021-04-27 19:00 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-09 20:26 bug#47677: [PATCH] condition-case success continuation Mattias Engdegård
2021-04-10 23:52 ` Stefan Monnier
2021-04-11 11:13 ` Mattias Engdegård
2021-04-12 8:49 ` Lars Ingebrigtsen
2021-04-12 15:10 ` Stefan Monnier
2021-04-12 19:20 ` Mattias Engdegård
2021-04-13 7:38 ` Lars Ingebrigtsen
2021-04-13 8:52 ` Mattias Engdegård
2021-04-14 9:29 ` Lars Ingebrigtsen
2021-04-15 13:54 ` Mattias Engdegård
2021-04-16 5:13 ` Richard Stallman
2021-04-16 5:13 ` Richard Stallman
2021-04-21 14:13 ` Stefan Kangas
2021-04-22 13:58 ` Mattias Engdegård
2021-04-23 4:18 ` Richard Stallman
2021-04-24 17:02 ` Mattias Engdegård
2021-04-25 4:44 ` Richard Stallman
2021-04-25 7:35 ` Eli Zaretskii
2021-04-25 18:21 ` bug#47677: [External] : " Drew Adams
2021-04-25 18:24 ` Eli Zaretskii
2021-04-26 4:40 ` Richard Stallman
2021-04-26 12:44 ` Eli Zaretskii
2021-04-27 3:46 ` Richard Stallman
2021-04-26 15:12 ` Filipp Gunbin
2021-04-27 15:31 ` Mattias Engdegård
2021-04-27 19:00 ` Gregory Heytings [this message]
2021-04-29 12:45 ` Filipp Gunbin
2021-04-25 16:45 ` Lars Ingebrigtsen
2021-04-26 11:53 ` Mattias Engdegård
2021-04-27 3:46 ` Richard Stallman
2021-04-26 21:57 ` Gregory Heytings
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/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=fe6aee4ffd34e15fb051@heytings.org \
--to=gregory@heytings.org \
--cc=47677@debbugs.gnu.org \
--cc=fgunbin@fastmail.fm \
--cc=larsi@gnus.org \
--cc=mattiase@acm.org \
--cc=monnier@iro.umontreal.ca \
--cc=stefan@marxist.se \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).