Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • Mac::PropertyList definitely sucks for big files.

    In my implementation, I actually wanted to parse the files on a FreeBSD machine, so I didn't want to do any Mac-specific coding. For small files, which is whatI had to deal with, my approach was fine. Everyone seems to want to parse their iTunes Library file, and those are ridiculously huge. I tried to get around that with a iTunes Music Library binary parser and was most of the way there until they changed the format from odd to completely goofy.

    If anyone comes up with a better way to do it, I'll gladly patch Mac::PropertyList.

    Besides that, the interface to Mac::PropertyList isn't great. It simply creates a big data structure. I intended other people to write layers above that to get to the data, so I didn't do a lot to make the data access any easier.

    The situation is even worse now since Apple moved to a binary format for plist files. You can convert it to a plain text form, but that''s now an extra step.