7 Mar
2007
7 Mar
'07
10:18 p.m.
Gunnar Farneback wrote:
Example 3: Like example 2, but abort command comes too late. Controller: 1 async_genmove black 2 abort_async_genmove 3 play black C3
Engine: =1
!1 E5
=2
=3
Maybe it should then read
?2 not in progress
It also makes sense to forbid an async_genmove (or simple genmove for that matter) until the previous genmove/async_genmove has finished. The engine should just fail with a predefined error string; I think it is really cumbersome for the engine to try synchronization here and serves little purpose.
Paul