From: Eli Zaretskii <eliz@gnu.org>
To: rms@gnu.org
Cc: 55278@debbugs.gnu.org
Subject: bug#55278: 29.0.50; OSM package
Date: Sat, 07 May 2022 09:08:28 +0300 [thread overview]
Message-ID: <83mtftzxgj.fsf@gnu.org> (raw)
In-Reply-To: <E1nn7ES-0001jX-D1@fencepost.gnu.org> (message from Richard Stallman on Fri, 06 May 2022 19:19:32 -0400)
> From: Richard Stallman <rms@gnu.org>
> Cc: 55278@debbugs.gnu.org
> Date: Fri, 06 May 2022 19:19:32 -0400
>
> > No, it's implemented in json.c in the Emacs sources. But to have that
> > function defined, you need to build Emacs with libjansson, which is an
> > optional dependency of Emacs.
>
> That is strange. If the function json-parse-string is defined in the
> Emacs sources, why compile it only if something else is enabled?
Because the actual implementation is in the libjansson library; the
Emacs sources only wrap that by a glue to allow use to use JSON with
Emacs Lisp objects.
> Does OSM depend on anything about jansson other than json-parse-string?
> What does jansson do?
The library implements most of JSON handling.
next prev parent reply other threads:[~2022-05-07 6:08 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-05 18:38 bug#55278: 29.0.50; OSM package Richard Stallman
2022-05-05 19:15 ` Eli Zaretskii
2022-05-06 12:15 ` Lars Ingebrigtsen
2022-05-06 23:19 ` Richard Stallman
2022-05-07 3:32 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-05-07 6:08 ` Eli Zaretskii [this message]
2022-05-07 23:08 ` Richard Stallman
2022-05-08 8:42 ` bug#55278: json-parse-string Daniel Mendler
2022-05-08 23:39 ` Richard Stallman
2022-05-09 10:27 ` Lars Ingebrigtsen
2022-05-09 10:39 ` Daniel Mendler
2022-05-09 10:45 ` Lars Ingebrigtsen
2022-05-09 10:57 ` Daniel Mendler
2022-05-09 23:20 ` Richard Stallman
2022-05-16 23:25 ` Richard Stallman
2022-05-17 19:12 ` Philip Kaludercic
2022-05-18 22:20 ` Richard Stallman
2022-05-09 23:20 ` Richard Stallman
2022-05-09 23:20 ` Richard Stallman
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=83mtftzxgj.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=55278@debbugs.gnu.org \
--cc=rms@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).