summaryrefslogtreecommitdiff
path: root/json-glib/json-node.c
diff options
context:
space:
mode:
authorEmmanuele Bassi <ebassi@openedhand.com>2008-04-19 23:09:20 +0100
committerEmmanuele Bassi <ebassi@openedhand.com>2008-04-19 23:09:20 +0100
commit676592cef006de16d966a1ca0469ccd0556f0e4b (patch)
tree5d1ca313cfa3105a4e2fab36c5441bfced98be43 /json-glib/json-node.c
parentbf2249a1855b6bebe0b3528b4d5321a1ebe4b9e7 (diff)
downloadjson-glib-676592cef006de16d966a1ca0469ccd0556f0e4b.tar.gz
Documentation fixes in JsonNode
Diffstat (limited to 'json-glib/json-node.c')
-rw-r--r--json-glib/json-node.c6
1 files changed, 3 insertions, 3 deletions
diff --git a/json-glib/json-node.c b/json-glib/json-node.c
index 035dd2e..b0f6bef 100644
--- a/json-glib/json-node.c
+++ b/json-glib/json-node.c
@@ -36,8 +36,8 @@
* When parsing a JSON data stream you extract the root node and walk
* the node tree by retrieving the type of data contained inside the
* node with the %JSON_NODE_TYPE macro. If the node contains a fundamental
- * type you can retrieve a copy of the GValue holding it with the
- * json_node_get_value() function, and then use the GValue API to extract
+ * type you can retrieve a copy of the #GValue holding it with the
+ * json_node_get_value() function, and then use the #GValue API to extract
* the data; if the node contains a complex type you can retrieve the
* #JsonObject or the #JsonArray using json_node_get_object() or
* json_node_get_array() respectively, and then retrieve the nodes
@@ -348,7 +348,7 @@ json_node_get_value (JsonNode *node,
g_return_if_fail (node != NULL);
g_return_if_fail (JSON_NODE_TYPE (node) == JSON_NODE_VALUE);
- if (G_VALUE_TYPE (&(node->data.value)) != 0)
+ if (G_VALUE_TYPE (&(node->data.value)) != G_TYPE_INVALID)
{
g_value_init (value, G_VALUE_TYPE (&(node->data.value)));
g_value_copy (&(node->data.value), value);