Mac::Pr...eBinary(3)

🌸 NAME 🌸

okay so bestie, this is the Mac::Pr...eBinary(3) page from User Contributed Perl Documentation — yes, the manual name is a little cursed/truncated-looking, but the actual module is:

• Mac::PropertyList::WriteBinary — pack data into a Mac "binary property list".

---

✨ SYNOPSIS ✨

use Mac::PropertyList::WriteBinary;

my $data = Mac::PropertyList::dict->new( { ... => ... } );
my $buf  = Mac::PropertyList::WriteBinary::as_string($data);

🦋 DESCRIPTION 🦋

okay so the as_string function converts a property list structure (composed of instances of Mac::PropertyList::dict, Mac::PropertyList::integer, etc.) into a binary format compatible with the Apple CoreFoundation binary property list functions. periodt.

It takes a single argument — the top-level object to write — and returns a byte string. 💖

The property list can contain the following perl objects:

• Mac::PropertyList value objects — these are written according to their class. slay.
• Unblessed references to Perl lists and hashes — these are written as arrays and dictionaries, respectively.
• Perl scalars — all Perl scalars are written as strings; this is similar to the behavior of writing an oldstyle OpenStep property list, which does not distinguish between numbers and strings, and then reading it using CoreFoundation functions.
• undef — this is written as the null object. CoreFoundation will read this as kCFNull, but appears to be unable to write it. 😭

Strings are uniqued (two equal strings will be written as references to the same object). If the same reference appears more than once in the structure, it will likewise only be represented once in the output. no cap.

🚨 real talk: although the bplist format can represent circular data structures, they cannot be written by this module (they will be detected and result in an error — they wouldn't be read correctly by CoreFoundation anyway, so you aren't missing much).

💀 BUGS 💀

• Mac::PropertyList::date objects are not handled yet. sad but true.
• Objects other than strings (and null) are not uniqued by value, only by reference equality. This may change in a future version.
• Perl's dictionary keys can only be strings, but a bplist's can be any scalar object.
• There is no way to write the UID objects used by the keyed archiver.
• Perls that do not use IEEE-754 format internally for floating point numbers will produce incorrect output.

🎀 AUTHOR 🎀

Wim Lewis, "<wiml@cpan.org>"

Copyright © 2012-2024 Wim Lewis. All rights reserved.

Tom Wyant added support for UID types. iconic.

This program is free software; you can redistribute it and/or modify it under the same terms as Perl itself.

🌈 SEE ALSO 🌈

• Mac::PropertyList::ReadBinary — for the inverse operation.
• Apple's partial published CoreFoundation source code: http://opensource.apple.com/source/CF/

mwah 💋 this page was served with perl v5.42.0, dated 2024-07-27, under the manual name Mac::Pr...eBinary(3) — bye bestie! 💅✨