On Wednesday 07 March 2007, Don Dailey wrote:
That's not useful however unless it's part of the standard.
interrupting commands was a feature that I needed personally, and I think that it could be useful for other people, too. I agree that it would be preferable to have such a feature included in future versions of the standard.
Support for interrupting is enabled in GtpEngine only, if it is compiled with GTPENGINE_INTERRUPT=1. You can view it as a reference implementation of a proposal for an extension to the GTP standard. This extension is already used in practice in some Go engines (like Explorer, NeuroGo and Crazy Stone).
The way, in which GtpEngine implements interrupting, is by receiving a special comment line "# interrupt". This is non-intrusive and does not create problems with GTP version 1 and 2. Engines that do not understand it will simply ignore it as any other comment lines.
Also, to my knowledge, the only GTP controllers who presently use interrupting are GoGui (http://gogui.sf.net) and some tools of the GoGui package. They will only use it, if the GTP engine indicates that it supports interrupting by implementing the GTP extension command gogui-interrupt.
- Markus