jasder
/
simdjson
1
0
Fork 0
Code Issues Pull Requests Releases 2 Wiki Activity

Documenting the limits of move_to_key with respect to Unicode Equivalence.

This commit is contained in:
Daniel Lemire 2019-08-20 17:10:30 -04:00
parent fb920bba62
commit a1bff85263
1 changed files with 5 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
include/simdjson/parsedjsoniterator.h
View File

@ -111,12 +111,16 @@ public:
// We seek the key using C's strcmp so if your JSON strings contain // We seek the key using C's strcmp so if your JSON strings contain
// NULL chars, this would trigger a false positive: if you expect that // NULL chars, this would trigger a false positive: if you expect that
// to be the case, take extra precautions. // to be the case, take extra precautions.
// Furthermore, we do the comparison character-by-character
// without taking into account Unicode equivalence.
inline bool move_to_key(const char *key); inline bool move_to_key(const char *key);
// when at {, go one level deep, looking for a given key // when at {, go one level deep, looking for a given key
// if successful, we are left pointing at the value, // if successful, we are left pointing at the value,
// if not, we are still pointing at the object ({) // if not, we are still pointing at the object ({)
// (in case of repeated keys, this only finds the first one). // (in case of repeated keys, this only finds the first one).
// The string we search for can contain NULL values. // The string we search for can contain NULL values.
// Furthermore, we do the comparison character-by-character
// without taking into account Unicode equivalence.
inline bool move_to_key(const char *key, uint32_t length); inline bool move_to_key(const char *key, uint32_t length);
// when at a key location within an object, this moves to the accompanying // when at a key location within an object, this moves to the accompanying