From: Drew Adams <drew.adams@oracle.com>
To: "Herman, Géza" <geza.herman@gmail.com>, "Eli Zaretskii" <eliz@gnu.org>
Cc: "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 20:18:03 +0000 [thread overview]
Message-ID: <SJ0PR10MB54889122CC57EA0C543ECA7AF3392@SJ0PR10MB5488.namprd10.prod.outlook.com> (raw)
In-Reply-To: <87wmpjmsie.fsf@gmail.com>
> >> 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?
Much JSON in the wild uses various forms of lax
syntax. There, null chars are often allowed.
> >> 3. Handling objects with duplicate keys.
The JSON standard _recommends_ that a JSON object
not have duplicate field names. But it doesn't
prohibit this, for a field name to be well-formed.
This is another case where feral JSON sometimes
departs from recommended syntax.
It's good if a JSON parser can use _either_ strict
or some version of a lax JSON syntax, au choix.
Lax-syntax support can be important for practical
(real world) reasons.
next prev parent reply other threads:[~2024-03-30 20:18 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 ` Drew Adams [this message]
2024-03-30 20:51 ` [External] : " Herman, Géza
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=SJ0PR10MB54889122CC57EA0C543ECA7AF3392@SJ0PR10MB5488.namprd10.prod.outlook.com \
--to=drew.adams@oracle.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=geza.herman@gmail.com \
--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).