Introducing: Communicate with a running spring

[Licho]

Yeah it should use text form probably and be specified in some doc beyond .h file.. but meanwhile this interface is fully useable.

Code is clean and simple and you get all you need to know by reading it.
There are no issues with numbers because all numbers are just 1 byte uchar.
Texts are encoded ascii because all spring uses is ascii.

And tbh lobby devs could have already implemented at least basic communication spring<->lobby the way springie did even without this interface.

[AF]

Actually lobby devs did try.

The main reason AFLobby does not do this is because at some point taking the chat and piping it to std::out was stopped. Raven iirc wrote code that read infolog.txt but that was hackish and I dint want to mess around with that. Spring lobby ppl iirc had similar results but I'm not sure on whether it was them or another project.

Thank you for the changes.

[Licho]

It still works (the piping) but I think you have to set debug flag (in registry)

[AF]

Yeah, at the time there was no unitsync interface for settings stuff though so it wasn't worth the bother.

[Tobi]

The 'int' datatype in C/C++ is 32 bit on both 32 bit and 64 bit Windows and Linux. 'long' is the one you don't want to touch because it's 32 bit on 32 bit and 64 bit on 64 bit.

(both Linux and Windows on x86-* architectures (x86-32 and x86-64 AKA amd64) use the LP64 model as opposed to ILP64.)