From: "Herman, Géza" <geza.herman@gmail.com>
To: Drew Adams <drew.adams@oracle.com>
Cc: "Herman, Géza" <geza.herman@gmail.com>,
"Eli Zaretskii" <eliz@gnu.org>,
"Mattias Engdegård" <mattiase@acm.org>,
"emacs-devel@gnu.org" <emacs-devel@gnu.org>
Subject: Re: [External] : Re: [PATCH] Implement fast verisons of json-parse functions
Date: Sat, 30 Mar 2024 21:51:49 +0100 [thread overview]
Message-ID: <87sf07mnmx.fsf@gmail.com> (raw)
In-Reply-To: <SJ0PR10MB54889122CC57EA0C543ECA7AF3392@SJ0PR10MB5488.namprd10.prod.outlook.com>
Drew Adams <drew.adams@oracle.com> writes:
>> >> 2. Handling of a single \0 byte
>> >
>> > Does JSON allow null bytes in its strings?
>
> Strict JSON doesn't allow null characters (U+0000).
> But does this parser only support strict JSON?
This parser only accepts JSONs which are according to the spec (in
theory). But this is not different from the libjansson based
parser in this regard. That also doesn't allow null characters in
JSON.
Just to be sure that we're on the same page: this means that the
parser doesn't support actual null bytes in the stream. But if a
user wants to put a U+0000 character in a string, they can do that
by using "\u0000".
next prev parent reply other threads:[~2024-03-30 20:51 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-19 18:23 [PATCH] Implement fast verisons of json-parse functions Herman, Géza
2024-03-19 18:47 ` Eli Zaretskii
2024-03-19 18:50 ` Herman, Géza
2024-03-19 19:28 ` Eli Zaretskii
2024-03-19 19:50 ` Herman, Géza
2024-03-20 3:37 ` Eli Zaretskii
2024-03-23 10:40 ` Herman, Géza
2024-03-23 11:11 ` Eli Zaretskii
2024-03-30 7:43 ` Eli Zaretskii
2024-03-30 10:50 ` Herman, Géza
2024-03-30 13:00 ` Eli Zaretskii
2024-03-30 18:36 ` Herman, Géza
2024-03-30 20:18 ` [External] : " Drew Adams
2024-03-30 20:51 ` Herman, Géza [this message]
2024-03-30 23:28 ` Drew Adams
2024-03-31 5:08 ` Eli Zaretskii
2024-03-31 14:51 ` Mattias Engdegård
2024-03-31 15:44 ` Eli Zaretskii
2024-04-01 8:48 ` Mattias Engdegård
2024-04-01 16:54 ` Herman, Géza
2024-03-31 17:48 ` Adam Porter
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=87sf07mnmx.fsf@gmail.com \
--to=geza.herman@gmail.com \
--cc=drew.adams@oracle.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=mattiase@acm.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).