Author: Alessandro Scotti
Date: 23:30:34 07/26/05
Go up one level in this thread
On July 27, 2005 at 01:05:33, Reinhard Scharnagl wrote: >SMIRF though using TMCI is showing by doing that it is possible to support a lot >of variants WITHOUT SWITCHING the engine's mode simply by communicating with >compatible FEN strings and encoded moves. This idea also could have been >applicated to a UCI protocol extension. But actually that switches an engine >into an FRC mode forcing the engine to different encoding of moves and FEN >strings, e.g. generating different FENs for identic positions (where castling >rights are based on traditional K+R placements only). Hi Reinhard, I would not say that engine is "switched into FRC mode". Communication protocol and engine interface should be completely separated, although they usually aren't for practical reasons. Also, why not telling the engine it's going to play FRC? Having more information at hand is rarely going to hurt, and you can always throw it away. A protocol adaptor, which you would have to write for TMCI anyway, can easily translate FEN and adjust castling moves before passing them to the engine if needed. P.S. I really like SMIRF and your ideas on chess programming, so I hope development may restart soon!
This page took 0.02 seconds to execute
Last modified: Thu, 15 Apr 21 08:11:13 -0700
Current Computer Chess Club Forums at Talkchess. This site by Sean Mintz.