Add line number to .plist errors

Nemoricus · Post by **Nemoricus** » Sun Jun 14, 2009 2:34 am

Exactly as the topic says.

I'm currently trying to hunt down an error in a .plist file, here, but without the line number, finding it is proving to be an exercise in futility.

For .js errors, the line number and the text in that line is given, which makes finding and fixing typos and syntax errors much easier. .plist doesn't have that.

Lestradae · Post by **Lestradae** » Sun Jun 14, 2009 7:10 am

Oh yes, please, seconded.

JensAyton · Post by **JensAyton** » Sun Jun 14, 2009 10:08 am

The bad news is that this isn’t under our control. The parsing of plists is handled by the Foundation framework – part of the system on Mac OS X, part of GNUstep on other platforms. The Mac implementation reports line numbers, but the GNUstep version does not.

The good news is that the current version of GNUstep appears to report line numbers.

The question, then, is why you have an old version of GNUstep. If you’re using Linux, it’s because Linux distros tend to distribute old versions by default. If you’re using Windows, it’s because Oolite is built against slightly hacked versions of GNUstep libraries and upgrading has been problematic. I don’t know the details of that, though; you’ll have to ask another_commander.