all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Dmitry Gutov <dgutov@yandex.ru>
To: Philipp Stephani <p.stephani2@gmail.com>
Cc: help-gnu-emacs <help-gnu-emacs@gnu.org>
Subject: Re: How to test for native JSON support?
Date: Tue, 4 May 2021 17:41:12 +0300	[thread overview]
Message-ID: <6e5917e4-8aa5-9630-2f5c-737a3ac01ae0@yandex.ru> (raw)
In-Reply-To: <CAArVCkSDOFU2oaGMOyHSV0B3Sx3CTnKEqgCa2HXTtPPewqMzJA@mail.gmail.com>

On 04.05.2021 17:32, Philipp Stephani wrote:

> Can you make this signal a specific error symbol so that callers can
> catch the error and react accordingly, e.g. by falling back to
> json.el?

I almost certainly can, and it does sound like a good idea.

I can't test the resulting patch, though (having no access to a Windows 
machine), and our Windows developers can better choose the symbol to use 
(AFAICT the situation with libraries possibly being absent at runtime is 
solely Windows-specific).

Step 2 might be to propagate the same error-signaling behavior to other 
features, like xml.c.



  reply	other threads:[~2021-05-04 14:41 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-02 12:09 How to test for native JSON support? Joost Kremers
2021-05-03  0:20 ` Nikolay Kudryavtsev
2021-05-03  8:21   ` Joost Kremers
2021-05-03 14:38     ` Nikolay Kudryavtsev
2021-05-03 18:59       ` Joost Kremers
2021-05-03 19:42   ` Dmitry Gutov
2021-05-03 22:33     ` Nikolay Kudryavtsev
2021-05-03 22:39       ` Dmitry Gutov
2021-05-04 11:40       ` Tim Landscheidt
2021-05-04 12:16         ` Eli Zaretskii
2021-05-04 12:29           ` Joost Kremers
2021-05-04 12:50             ` Eli Zaretskii
2021-05-04 13:06               ` Joost Kremers
2021-05-04 13:17               ` Dmitry Gutov
2021-05-04 14:01                 ` Eli Zaretskii
2021-05-04 14:30                   ` Dmitry Gutov
2021-05-04 14:32                     ` Philipp Stephani
2021-05-04 14:41                       ` Dmitry Gutov [this message]
2021-05-04 15:16                     ` Eli Zaretskii

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=6e5917e4-8aa5-9630-2f5c-737a3ac01ae0@yandex.ru \
    --to=dgutov@yandex.ru \
    --cc=help-gnu-emacs@gnu.org \
    --cc=p.stephani2@gmail.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.
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.