[PR #56] NSNumber: support some exotic formats #90

New Issue

claunia · 2026-01-30T21:27:04Z

claunia commented

2026-01-30 21:27:04 +00:00

Original Pull Request: https://github.com/claunia/plist-cil/pull/56

State: closed
Merged: Yes

According to the Apple implementation (see __CFBinaryPlistCreateObjectFiltered and _getSizedInt):

Binary property lists can contain NSNumber values which are 128-bit (16-byte) long, even though the first 64 bits (8 bytes) will be ignored.
You can encounter non-power-of-2 length (e.g. 3-byte) NSNumber-values

I've managed to encounter a property list which contains a 128-bit NSNumber value, so this PR adds support for them (and a bunch of unit tests, too)

**Original Pull Request:** https://github.com/claunia/plist-cil/pull/56 **State:** closed **Merged:** Yes --- According to [the Apple implementation](https://opensource.apple.com/source/CF/CF-1153.18/CFBinaryPList.c.auto.html) (see `__CFBinaryPlistCreateObjectFiltered` and `_getSizedInt`): - Binary property lists can contain NSNumber values which are 128-bit (16-byte) long, even though the first 64 bits (8 bytes) will be ignored. - You can encounter non-power-of-2 length (e.g. 3-byte) NSNumber-values I've managed to encounter a property list which contains a 128-bit NSNumber value, so this PR adds support for them (and a bunch of unit tests, too)

claunia added the pull-request label 2026-01-30 21:27:04 +00:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: claunia/plist-cil#90