search for: json_object_get

Hi, recently, there was a discussion in the development list of libvirt on switching to a different JSON library than YAJL [1]. Since we use YAJL, and the points there IMHO apply to libguestfs as well, I decided to give a try in switching to Jansson [2]. The result IMHO is nice, with the additional APIs of Jansson that simplify some of our code. Unlike with YAJL, I did not set a minimum

...h a very liberal license, and a much nicer API. Hence, switch all of libguestfs from YAJL to Jansson: - configure checks, and buildsystem in general - packages pulled in the appliance - actual implementations - contrib scripts - documentation This also makes use of the better APIs available (e.g. json_object_get, json_array_foreach, and json_object_foreach). This does not change the API of our OCaml Yajl module. --- appliance/packagelist.in | 13 ++-- builder/Makefile.am | 4 +- builder/yajl-c.c | 66 ++++++++++----------- contrib/p2v/aux-scripts/do-build...

Hi, recently, there was a discussion in the development list of libvirt on switching to a different JSON library than YAJL [1]. Since we use YAJL, and the points there IMHO apply to libguestfs as well, I decided to give a try in switching to Jansson [2]. The result IMHO is nice, with the additional APIs of Jansson that simplify some of our code. Unlike with YAJL, I did not set a minimum

...h a very liberal license, and a much nicer API. Hence, switch all of libguestfs from YAJL to Jansson: - configure checks, and buildsystem in general - packages pulled in the appliance - actual implementations - contrib scripts - documentation This also makes use of the better APIs available (e.g. json_object_get, json_array_foreach, and json_object_foreach). This does not change the API of our OCaml Yajl module. The only behaviour change is that Jansson by default accepts only objects and arrays as input (even though it has a flag to make it accept anything). Since this seems a good idea anyway, and as...

...I. > > Hence, switch all of libguestfs from YAJL to Jansson: > - configure checks, and buildsystem in general > - packages pulled in the appliance > - actual implementations > - contrib scripts > - documentation > > This also makes use of the better APIs available (e.g. json_object_get, > json_array_foreach, and json_object_foreach). This does not change the > API of our OCaml Yajl module. > > The only behaviour change is that Jansson by default accepts only > objects and arrays as input (even though it has a flag to make it accept > anything). Since this see...

...) + return; + + tree = json_loads (json, 0, &err); + if (tree == NULL) { + if (strlen (err.text) > 0) + debug (g, "QMP parse error: %s (ignored)", err.text); + else + debug (g, "QMP unknown parse error (ignored)"); + return; + } + + return_node = json_object_get (tree, "return"); + if (!json_is_object (return_node)) { + debug (g, "QMP query-kvm: no \"return\" node (ignored)"); + return; + } + enabled_node = json_object_get (return_node, "enabled"); + if (!enabled_node || !json_is_boolean (enabled_node)) { +...

...nicer API. > >Hence, switch all of libguestfs from YAJL to Jansson: >- configure checks, and buildsystem in general >- packages pulled in the appliance >- actual implementations >- contrib scripts >- documentation > >This also makes use of the better APIs available (e.g. json_object_get, >json_array_foreach, and json_object_foreach). This does not change the >API of our OCaml Yajl module. > >The only behaviour change is that Jansson by default accepts only >objects and arrays as input (even though it has a flag to make it accept >anything). Since this seems a g...