Syntax check config files

[robojumper]

There are a bunch of pitfalls regarding config files that people seem to fall into very often, such as:

• Section headers with trailing whitespace [...] (causes it to be interpreted as no section header at all)
• Multiline entries with trailing whitespace , \\ (causing the line to be ended early)
• Illegal commented lines within multiline comments

Catching these at build time would help.

[Iridar]

I've also had a case where having a = on a config line with nothing else beside that single character would prevent the mod from building without a meaningful message. It was effectively an accidental typo, so was pretty hard to catch.

[Xymanek]

I've also had a case where having a = on a config line with nothing else beside that single character would prevent the mod from building without a meaningful message. It was effectively an accidental typo, so was pretty hard to catch.

I guess this was in XComEngine.ini? Can you also provide a reproduction example (e.g. in an empty mod)