- 29 Jun, 2016 1 commit
-
-
Nikias Bassen authored
Without this check, e.g. the values -1 and 18446744073709551615 would yield in a match, since the comparison will just compare the uint64_t values. However, any value >= 9223372036854775808 and <= 18446744073709551615 is stored as a 128 bit value in binary plist format to make sure it is recognized as an unsigned value. We store it internally as a uint64_t value, but we set the size to 16 vs. 8 accordingly; so this commit will make sure the binary plist optimization will not re-use matching uint64_t values of actually mismatching signed/unsigned values.
-
- 12 May, 2016 2 commits
-
-
Christophe Fergeau authored
Rather than having everyone reimplement binary/XML plist detection by looking at the first bytes of the plist content, it's better to do this detection in libplist and hide that internal detail from library users.
-
Christophe Fergeau authored
It can be useful if one needs to know what type of plist a memory buffer contains.
-
- 20 Apr, 2016 1 commit
-
-
Frederik Carlier authored
-
- 23 Jan, 2015 1 commit
-
-
Martin Szulecki authored
-
- 03 Oct, 2014 1 commit
-
-
Nikias Bassen authored
-
- 20 May, 2014 2 commits
-
-
Nikias Bassen authored
-
Martin Szulecki authored
-
- 02 Apr, 2014 1 commit
-
-
Nikias Bassen authored
-
- 19 Mar, 2014 2 commits
-
-
Nikias Bassen authored
-
Nikias Bassen authored
-
- 12 Dec, 2013 1 commit
-
-
Nikias Bassen authored
-
- 16 Sep, 2012 2 commits
-
-
Nicolás Alvarez authored
-
Nikias Bassen authored
-
- 23 Apr, 2012 1 commit
-
-
Nikias Bassen authored
-
- 27 May, 2011 1 commit
-
-
Nikias Bassen authored
-
- 21 Jan, 2010 1 commit
-
-
Jonathan Beck authored
-
- 19 Nov, 2009 2 commits
-
-
Christophe Fergeau authored
Before recursing over its children, plist_free_node started by detaching the current GNode from its parent which means that calling g_node_destroy on the root of the tree was freeing only the top-level GNode while what was intended was to free the whole tree. Don't leak memory by not detaching children GNodes from their parents so that g_node_destroy on the toplevel GNode can clean everything.
-
Christophe Fergeau authored
The 2nd missing break was harmless since it fell through the default: case which has a break, but it makes things more robust if we were ever to add new cases to this switch. The 1st missing break; was causing warnings in valgrind since we ended up calling strdup on a memory zone not containing a \0 character.
-
- 10 Nov, 2009 1 commit
-
-
Jonathan Beck authored
-
- 28 Oct, 2009 2 commits
-
-
Jonathan Beck authored
-
Jonathan Beck authored
-
- 17 Oct, 2009 1 commit
-
-
Jonathan Beck authored
-
- 13 Oct, 2009 1 commit
-
-
Jonathan Beck authored
-
- 11 Oct, 2009 5 commits
-
-
Jonathan Beck authored
-
Jonathan Beck authored
-
Jonathan Beck authored
-
Jonathan Beck authored
-
Jonathan Beck authored
-
- 10 Oct, 2009 5 commits
-
-
Jonathan Beck authored
-
Jonathan Beck authored
-
Jonathan Beck authored
-
Jonathan Beck authored
-
Jonathan Beck authored
-
- 18 Jul, 2009 2 commits
-
-
Jonathan Beck authored
-
Jonathan Beck authored
-
- 14 Jul, 2009 1 commit
-
-
Martin Szulecki authored
-
- 09 Jul, 2009 1 commit
-
-
Jonathan Beck authored
-
- 08 Jul, 2009 2 commits
-
-
Jonathan Beck authored
-
Jonathan Beck authored
-