Troubles with the stdin in own Windows compiles

[OliverBr]

Maybe someone knows of this issue:

When you open the Windows executable on CMD and then enter “uci” (3-character), the answer won’t show until the next command.
"uci " with space works fine, also "go", "stop", "ponder", "quit" as they have all "even" chars.
This issue has been reported/verified by others on their Windows PC.

I don’t think the problem lies in the code, because the linux/macosx executables work fine.
My own Windows compilations show this strange behaviour.
The problem does not appear with Jim Ablett's Windows compiles.

Code: Select all

	char line[8192];
	while(fgets(line, sizeof(line), stdin)) {