Did I understood correctly, that the data file (xson config) is the part that is parsed offline and will dictates what the actual structures will look like ?
In the past I used the opposite way: I defined the "config.inc" file ( XSON_VALUE(...), XSON_STRUCT(name) ... ) manually and use the macro to generate the default config file and parsing code. The other way doesn't make sens to me as adding fields using the config file isn't useful if the game code doesn't use it.
Ah, interesting. I suppose that works just as well, though I felt more comfortable writing the xon/json format than the macros (and so it didn't occur to me to do that way).
A side note: the code samples display on your site could be better. At the moment every line is gray and underline with gray.
Thank you, I wholeheartedly agree (and hate the template I'm using)... I'll see what I can do to improve it, though removing the damn underline should be easy enough.