unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Richard Stallman <rms@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: acm@muc.de, emacs-devel@gnu.org
Subject: Re: New(?) idea for making backtraces usable: condition-case*
Date: Tue, 18 Jul 2023 22:19:17 -0400	[thread overview]
Message-ID: <E1qLwmb-0003dH-NH@fencepost.gnu.org> (raw)
In-Reply-To: <83ttu27c0w.fsf@gnu.org> (message from Eli Zaretskii on Mon, 17 Jul 2023 19:12:15 +0300)

[[[ 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. ]]]

  > > My idea here is to write a new special form, condition-case*.  This would
  > > behave the same as condition-case unless a signal is signalled.  In that
  > > case the error handler forms would evaluate _before_ the specpdl gets
  > > unwound.  This unwinding would take place on exiting an error handler in
  > > the form.  The unwinding would NOT happen if the error handler is exited
  > > with, say, signal.  This would give nested condition-case*'s the chance
  > > to output a full backtrace.

I thinmk it is unclean for `condition-case' (or a variant of it) to run
its cleanups in a context other than its own.  We have ways to get
backtraces from where the error was signaled, and if other ways
to do that would be useful we can add them, but I think they should
not resemble `condition-case'.
-- 
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)





  reply	other threads:[~2023-07-19  2:19 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-17 13:52 New(?) idea for making backtraces usable: condition-case* Alan Mackenzie
2023-07-17 16:12 ` Eli Zaretskii
2023-07-19  2:19   ` Richard Stallman [this message]
2023-07-19 20:35   ` Alan Mackenzie
2023-07-20  4:41     ` Eli Zaretskii
2023-07-21  2:42     ` Richard Stallman
2023-07-21  5:55       ` Eli Zaretskii
2023-07-21  5:59         ` Ihor Radchenko
2023-07-19  2:19 ` Richard Stallman
  -- strict thread matches above, loose matches on Subject: below --
2023-07-18  4:38 Gerd Möllmann

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=E1qLwmb-0003dH-NH@fencepost.gnu.org \
    --to=rms@gnu.org \
    --cc=acm@muc.de \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@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.
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).