all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Stefan Monnier via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Ihor Radchenko <yantar92@posteo.net>
Cc: Eli Zaretskii <eliz@gnu.org>, 68075@debbugs.gnu.org
Subject: bug#68075: 30.0.50; New special form `handler-bind`
Date: Thu, 28 Dec 2023 17:04:45 -0500	[thread overview]
Message-ID: <jwvil4idn6f.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <87bkaa6v68.fsf@localhost> (Ihor Radchenko's message of "Thu, 28 Dec 2023 18:25:51 +0000")

>> I'm trying to explain that when looking for a handler, we look both for
>> condition-case handler and handler-bind handlers and we use whichever is
>> "closest", i.e. more deeply nested.  So just like a local
>> `condition-case` overrides temporarily an outer one, the same holds not
>> only among `handler-bind`s but also between `condition-case` and
>> `handler-bind` as well.
>
> Then, it would also make sense to make `condition-case' and
> `handler-bind' refer to each other from the docstrings.

BTW, `condition-case` can be implemented as a macro on top of
`handler-bind` and `catch`, e.g.

    (condition-case ERR FORM (error HANDLER))

can become something like:

    (let* ((tag (cons nil nil))
           (ERR (catch tag
                  (handler-bind ((error (lambda (err) (throw tag err))))
                    (cons 'noerror FORM)))))
      (if (eq 'noerror (car ERR))
          (cdr ERR)
        HANDLER))

:-)


-- Stefan






  reply	other threads:[~2023-12-28 22:04 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-28  6:33 bug#68075: 30.0.50; New special form `handler-bind` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-12-28  8:03 ` Eli Zaretskii
2023-12-28 18:12   ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-12-28 18:14     ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-12-30  7:50       ` Eli Zaretskii
2023-12-28 18:25     ` Ihor Radchenko
2023-12-28 22:04       ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2023-12-30  7:52     ` Eli Zaretskii
2023-12-31 19:07       ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-12-31 19:36         ` Eli Zaretskii
2024-01-01 15:37           ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-01-01 16:06             ` Eli Zaretskii
2024-01-01 16:55               ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-01-01 17:35                 ` Eli Zaretskii
2024-01-02  4:56                   ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-01-04 23:57                     ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-01-05  0:38                       ` Stefan Kangas
2024-01-05  0:50                     ` Stefan Kangas
2024-01-05  2:57                       ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=jwvil4idn6f.fsf-monnier+emacs@gnu.org \
    --to=bug-gnu-emacs@gnu.org \
    --cc=68075@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    --cc=yantar92@posteo.net \
    /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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.