Re: computer-go: gnugoclient 2.0

[Daniel Bump <bump@xxxxxxxxxxxxxxxxxx>]

> Is  there  agreement that  if  your  Go  engine  does not implement  a
> command, it should return something like "not_implemented" ?
> 
> The idea of a minimal set is  guaranteed compatibility.  I can't write
> a good interface  without 'undo', but I  at least could write one that
> reports back  to  me that "undo"  is not  supported by the  underlying
> engine.
> 
> How difficult is it to get undo into play_gtp?

I think undo should be part of the irreducible set of commands.

I discussed how undo should be implemented in GNU Go's gtp
with Gunnar today and he suggested a scheme that was simpler
than the one I was thinking of. I think it should be easy
to do. He wants to keep a stack of all moves that are
played, just as I did. While I wanted to also keep track
of captures, his idea was that if undo is called you just
go back to the beginning of the stack and play each move.
That should be fast enough.

My guess is that we can get this into 3.0.0.

Dan