Quote:
CJN said:
How about:
Line 1: Name, id
Line 2: Terrain
Line 3: Neighbours
Line 4: NOSTART, START, VP, etc.
Line 5->: commanders, features, population, buildings
|
Oohhh name of the province? Much variable there. That is difficult to parse. How about if as much as possible, which can easily be parsed, be on one line. Then the difficult to parse can be seperated by "newline" as long as they always can be found on that line each time. Such as...
Line 1: Name
Line 2: id, Terrain, NOSTART, VP, etc
Line 3: Neighbors
That way even if there are no Neighbors it should still have a line which says Neighbors with no other output.
Quote:
There is also the problem that there are two ways to add nostart. As a terrain flag and as a separate command. Should the output differ for them?
|
Well the purpose I see is either for Users/map-makers who want readable info.. or for people who want to include it into a scripting pipe as an easy way to get info they didnt want to figure out how to extract. So Id say just put NOSTART when applicable no matter how its generated.
Quote:
Line 5->: commanders, features, population, buildings
|
OUCH that puts a wrench into the whole thing. It means that I cant just count lines and say "if line 2 has NOSTART skip next 2 lines and check again".
OK now Im thinking there are two ways to go. One is to have a unique character or Groups of characters flagging the begining of each province output. Such as -=- which can be used to count from or jump to the next province. The problem is finding something which in a script environment such as linux doesnt mean something special already. OR add a switch such as -v for more verbose output and have two outputs. One for all info, and the other for easy-parse info. Hmmm wait, the more casual user should always be considered for defaults. So maybe have the fully englished curious-user output be default with a -s short-Version for script programmers.