A van Kessel wrote:
*) Semantics. *) should the aborted command ("genmove", in most cases) report the best move found sofar ? *) if so, should it also have "committed" the move to it's internal state ? *) if it doen not have any move yet, what should the reply be ? *) should the abort also undo the aborted command's side-effects ?
I still think that there is no need to specify, if the engine should return success or error to an aborted genmove. Both can make sense depending on the kind of engine and its easy for an interactive controlling program to handle both cases correctly.
So I wouldn't overspecify things or complicate the protocol with a whole set of new commands.
Also there is a problem if the user sends an abort, but the engine already sent a success in the short time between the user clicked and the abort is sent.
- Markus