After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 725507 - write a new JSON tokenizer
write a new JSON tokenizer
Status: RESOLVED OBSOLETE
Product: json-glib
Classification: Core
Component: Parser
git master
Other Linux
: Normal enhancement
: ---
Assigned To: json-glib-maint
json-glib-maint
Depends on:
Blocks: 725397
 
 
Reported: 2014-03-02 16:32 UTC by Emmanuele Bassi (:ebassi)
Modified: 2017-09-05 10:40 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Emmanuele Bassi (:ebassi) 2014-03-02 16:32:34 UTC 
JsonParser uses a fork of GScanner called JsonScanner for the tokenization of the input.

JsonScanner is generally okay-ish, but its implementation has quirks that make it harder to work with. the main stumbling block is error reporting: some errors in the tokenization (especially when it comes to Unicode parsing) result in assertions, and in other cases the flow bubbles up to the JsonParser, which can then correctly handle them as GError.

another issue with JsonScanner is the amount of code we string along from GScanner, and that we don't use.

we should drop our GScanner fork, and use an ad hoc tokenizer for JSON.
Comment 1 Emmanuele Bassi (:ebassi) 2017-09-05 10:40:33 UTC 
-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/json-glib/issues/11.