unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Philipp Stephani <p.stephani2@gmail.com>
To: "Mark Oteiza" <mvoteiza@udel.edu>,
	"Clément Pit--Claudel" <cpitcla@mit.edu>
Cc: Eli Zaretskii <eliz@gnu.org>, emacs-devel@gnu.org
Subject: Re: JSON encoding and decoding performance
Date: Thu, 20 Apr 2017 10:50:20 +0000	[thread overview]
Message-ID: <CAArVCkQcsViRnZA1xHcw+BP4VAjm08aG2ZoD+_mErQNK+Campw@mail.gmail.com> (raw)
In-Reply-To: <87pogc1dvs.fsf@holos>

[-- Attachment #1: Type: text/plain, Size: 888 bytes --]

Mark Oteiza <mvoteiza@udel.edu> schrieb am So., 16. Apr. 2017 um 19:06 Uhr:

>
> Clément Pit--Claudel <cpitcla@mit.edu> writes:
> >>> Would there be strong objections to supporting a C JSON library in
> >>> addition to the current ELisp implementation?  This was suggested
> >>> at one point in
> >>> https://lists.gnu.org/archive/html/bug-gnu-emacs/2015-03/msg00770.html
> >>> .  It would be similar in spirit to supporting libxml-parse-region
> >>> along xml-parse-region, and it could provide nice speed boosts to
> >>> json-heavy ELisp programs.
> >>
> >> Since we have modules now, something that wasn't available back
> >> then, you could roll your own library, right?
> >
> > That's right! I forgot about these. Let me try :)
>
> Here's one: https://github.com/syohex/emacs-parson


Thanks. I think the performance gain measured for that is quite convincing.

[-- Attachment #2: Type: text/html, Size: 1544 bytes --]

  reply	other threads:[~2017-04-20 10:50 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-15  5:35 JSON encoding and decoding performance Clément Pit--Claudel
2017-04-15  7:59 ` Eli Zaretskii
2017-04-16 15:43   ` Clément Pit--Claudel
2017-04-16 17:05     ` Mark Oteiza
2017-04-20 10:50       ` Philipp Stephani [this message]
2017-04-16 17:12     ` Eli Zaretskii
2017-04-20 10:45 ` Philipp Stephani

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=CAArVCkQcsViRnZA1xHcw+BP4VAjm08aG2ZoD+_mErQNK+Campw@mail.gmail.com \
    --to=p.stephani2@gmail.com \
    --cc=cpitcla@mit.edu \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=mvoteiza@udel.edu \
    /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).