FGCOM/jansson
2
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

doc: Copying doesn't preserve key insertion order

Browse Source 
Fixes #237.
This commit is contained in:
Petri Lehtinen 2015-05-19 08:48:52 +03:00
parent d384acd706
commit 69678aaa35
1 changed files with 4 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
doc/apiref.rst
View File

@ -1510,6 +1510,10 @@ the same child values in the copied value. Deep copying makes a fresh
copy of the child values, too. Moreover, all the child values are deep copy of the child values, too. Moreover, all the child values are deep
copied in a recursive fashion. copied in a recursive fashion.
Copying objects doesn't preserve the insertion order of keys. Deep
copying also loses the key insertion order of any objects deeper in
the hierarchy.
.. function:: json_t *json_copy(json_t *value) .. function:: json_t *json_copy(json_t *value)
.. refcounting:: new .. refcounting:: new