Computer Chess Club Archives


Search

Terms

Messages

Subject: Re: Reasons why an engine make a last move before resigning

Author: Andrew Dados

Date: 11:33:35 12/23/00

Go up one level in this thread


On December 23, 2000 at 12:37:00, Robert Hyatt wrote:

>On December 23, 2000 at 12:26:24, Ferdinand S. Mosca wrote:
>
>>What's the main idea why engines have to be like this.
>>
>>Regards,
>>Dinan
>
>
>I don't know that "all" are like that.  But it is very likely that they will
>both resign _and_ play a move, which is perfectly acceptable by normal chess
>rules...
>
>To not play a move would take some extra code, and it would be used only
>rarely.  Less code == fewer unexpected problems in the code...

That issue bothered me a bit, cause sending move and immediately resigning can
cause winboard timing problems. I myself don't see the reason why resign code
can't be  executed before 'sending move' code (which would be suppressed after
'resign' was send). However still many programs are written to make move, then
resign (crafty, arasan, comet to name a few).

-Andrew-



This page took 0 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.