Arend Bayer wrote:
"qGo only supports GTP, not GMP. GTP looks much better and was very easy to implement." Peter Strempel, author of qgo, gGo, glGo.
I'd write this again exactly this way. :) For a client programmer, GTP simply is the easier way to go and involves much less work. I wouldn't understand why anyone wanted to use GMP anymore today.
Additionally maybe mention that GMP is a binary protocol (if I understand it right, I never used it myself) and GTP is text based. To any programmer it will be instantly obvious that the text based solution is more convinient.
- Windows.
There are several options for the communication stream under Windows.
a) Stdin/Stdout. It is not very widely known that Windows GUI programs can use console stdin and stdout, too. See
This Q&A set makes no sense to me. I am absolutely no capable Win32 API programmer, but with my mere knowledge I did know that you can grab stdin/out to a processes on Windows just like you can do on Unix. A Win32 guru who has never programmed on Unix would rather ask "How can I do it on Unix?" Your writing suggests Unix is the norm and Windows is something special. I'd suggest to keep that sort of stuff out of a GTP FAQ.
I'd remove this whole Q&A set and maybe replace it with something like:
How can I connect a client to the GTP engine?
a) Start a process and grab stdin/out b) Named pipes c) TCP/IP socket
Peter