Your security-sensitive parser should not attempt to tolerate invalid input.
Probably you should not have multiple separate implementations of it, either.
By the time stuff like JSON started popping up, plists were pervasive all throughout OS X. Typical legacy problem!
https://developer.apple.com/library/archive/documentation/Co...
I dislike XML and would not chose it for my projects. But... in this case, it does seem like a good idea to require explicitly closed tags. Seems like it could remove 1000 error potentials for every 1 parser error.
[1] It's very clearly stated as item 2, in a 2-item list for well-formed-ness of documents: https://www.w3.org/TR/xml/#sec-well-formed
IOS was released last week by mental accounting standards.
To hear both be branded as ‘legacy’ is, frankly... well, it makes me feel ancient.