Age | Commit message (Collapse) | Author | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
|
The parsing logic for binary dictionaries wrongly enforced the key type even
on nodes that were already parsed as value nodes. This caused the resulting
plist_t node tree to have key nodes instead of value nodes within dictionaries
for some valid binary plists. This commit should also generally fixes parsing
of binary plist files which use an efficient dictionary reference table.
|
|
|
|
|
|
|
|
non-gcc/clang compilers happy
|
|
|
|
binary plist
|
|
strings
|
|
|
|
references and a const GetValue().
|
|
|
|
|
|
mismatch
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
output
|
|
|
|
|
|
|
|
ownership/responsibility.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
AC_C_BIGENDIAN should do its job already.
|
|
On debian-mips, neither __LITTLE_ENDIAN__ nor __BIG_ENDIAN__ are defined
anywhere, so PLIST_BYTE_ORDER defaults to PLIST_LITTLE_ENDIAN when it should
really be PLIST_BIG_ENDIAN on this architecture.
This fixes issue #13.
|