• Nikias Bassen's avatar
    plist_data_compare: Make sure to compare the node sizes for integer nodes · acd226d1
    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.
    acd226d1
Name
Last commit
Last update
..
Array.cpp Loading commit data...
Boolean.cpp Loading commit data...
Data.cpp Loading commit data...
Date.cpp Loading commit data...
Dictionary.cpp Loading commit data...
Integer.cpp Loading commit data...
Key.cpp Loading commit data...
Makefile.am Loading commit data...
Node.cpp Loading commit data...
Real.cpp Loading commit data...
String.cpp Loading commit data...
Structure.cpp Loading commit data...
Uid.cpp Loading commit data...
base64.c Loading commit data...
base64.h Loading commit data...
bplist.c Loading commit data...
bytearray.c Loading commit data...
bytearray.h Loading commit data...
hashtable.c Loading commit data...
hashtable.h Loading commit data...
libplist++.pc.in Loading commit data...
libplist.pc.in Loading commit data...
plist.c Loading commit data...
plist.h Loading commit data...
ptrarray.c Loading commit data...
ptrarray.h Loading commit data...
xplist.c Loading commit data...