- 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
How do I start a process? What is a named pipe? Etc. These are not the answers you need to implement gtp.
The purpose of a FAQ is that *the most ignorant person* who reads it should be able to get answers from it. This happens to be me (or was before I did implement gtp by trial and error).
I have programmed in Windows for almost 10 years using Delphi. The nice thing with Delphi is that you are Win32 is encapsulated in a way so for me low level windows programming is completely abstracted away. Unfortunately this made it very difficult for me to initially even have an idea how to do things right.
The kind of information included by Arend is exactly what I would have needed in order to avoid trial and error and searching for help in the blind.
Best wishes Magnus -- Magnus Persson Center for Adaptive Behavior and Cognition