Dangers of NeXTSTEP Plists
pewpewthespells.com
pewpewthespells.com
I don't know why they just don't upgrade to xml or binary.
https://gist.github.com/jevinskie/98a11023f4b561d36b26
P.S. Xcode plugins are "fun" to write!
EDIT: I believe that Xcode will load .xcspecs in any format. The .xcspec ends up getting fed into a TSPropertyListDictionary class which is backed by a plain NSDictionary. I'll test tonight. :)
In 20 years we'll say the same thing about json and yaml. In fact I say it about yaml now.
YAML and JSON and property lists are all terrible formats (inflexible and underpowered, forcing people to add half-baked ad hoc extensions on top to do almost anything). I wish they would all go die in a fire in favor of something with better data structures and support for extension such as e.g. EDN.
json or toml.
> The NeXT/OpenStep plist format assumes that strings are written as ASCII, whereas Cocoa assumes strings are written in Unicode
Do they mean "UTF-16" when they say "Unicode"? ASCII is an encoding but "unicode" is not, so I can't make sense of it.
On another note, it's fairly common that \U0000 style escapes are limited to FFFF. Would it work to use a surrogate pair for the non-BMP character?
I like most of Apple's products but I really wish other people didn't so they'd be compelled to fix these long running process failures (and give IT folks a little more love).
The process is just too rude and disrespectful to the submitter to participate in.
Apple behaves like it is Apple doing developers a favor by allowing them to submit bugs, rather than the other way around.
"File a Radar": http://openradar.appspot.com/23505531
I feel and have first hand knowledge of their frustration. On a pleasant note, I've also had a rdar report where I emailed an Apple dev out-of-band and he told me the bug was already fixed (thanks to my report) days before the rdar was updated.