From: Richard Stallman <rms@gnu.org>
To: "Mattias Engdegård" <mattiase@acm.org>
Cc: larsi@gnus.org, stefan@marxist.se, monnier@iro.umontreal.ca,
47677@debbugs.gnu.org
Subject: bug#47677: [PATCH] condition-case success continuation
Date: Fri, 23 Apr 2021 00:18:06 -0400 [thread overview]
Message-ID: <E1lZnGY-0003BC-5u@fencepost.gnu.org> (raw)
In-Reply-To: <B37675E0-3530-4238-AE41-9133C61F0A28@acm.org> (message from Mattias Engdegård on Thu, 22 Apr 2021 15:58:10 +0200)
[[[ To any NSA and FBI agents reading my email: please consider ]]]
[[[ whether defending the US Constitution against all enemies, ]]]
[[[ foreign or domestic, requires you to follow Snowden's example. ]]]
> There's the business of fixing `catch` in the same way. (A new bug could be opened for it, but since it's intimately related we might as well do it here.) As mentioned, `catch` has three problems:
> - no way to execute code when a throw is caught
> - no way to execute code when the body terminates normally
> - no way to catch both throws and errors
I do not agree that these are problems. catch and throw are ok
as they are, and we should leave them alone.
catch is meant for intentional exits, and condition-case is meant for
catching errors. If you want to handle both in one place, use both
constructs there.
If you want to do something after catch catches a throw, it is not hard
to implement that using the existing constructs.
(if (catch 'foo
(prog1 nil
...do stuff...)) ;; use (throw 'foo t) to exit
do-if-throw
do-if-no-throw)
given how rarely this is used, it's as easy as it needs to be, and
avoids making catch complicated.
--
Dr Richard Stallman (https://stallman.org)
Chief GNUisance of the GNU Project (https://gnu.org)
Founder, Free Software Foundation (https://fsf.org)
Internet Hall-of-Famer (https://internethalloffame.org)
next prev parent reply other threads:[~2021-04-23 4:18 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 [this message]
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
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=E1lZnGY-0003BC-5u@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=47677@debbugs.gnu.org \
--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).