summaryrefslogtreecommitdiff
path: root/json-glib/json-node.c
diff options
context:
space:
mode:
authorEmmanuele Bassi <ebassi@linux.intel.com>2011-02-06 11:34:22 +0000
committerEmmanuele Bassi <ebassi@linux.intel.com>2011-02-06 11:34:22 +0000
commitb2880f5a4dad07ff96a9b6578ffc5d677f75eb94 (patch)
tree190539e002e746274e8e3f21661ac343aed679c5 /json-glib/json-node.c
parent74ed11db6da9839ce17b448d6d17103ea0734dda (diff)
downloadjson-glib-b2880f5a4dad07ff96a9b6578ffc5d677f75eb94.tar.gz
reader: Allow using read_element() on objects
If we assume that a JSON object is just an array with a named mapping then the JsonReader API should be able to descend into objects using the same API used for arrays. This obviously is less useful than it sounds if we take a very strict interpretation of JSON objects as unordered string-to-value mappings; as the ordering is not guaranteed to be stable, parsers would be fairly weak against various JSON definitions. If the JSON format parsed is guaranteed to be stable then an integer offset might be an easy (albeit slightly less performant) way to access data.
Diffstat (limited to 'json-glib/json-node.c')
0 files changed, 0 insertions, 0 deletions