Author: Tom Kerrigan
Date: 01:17:32 05/11/03
Go up one level in this thread
On May 09, 2003 at 19:44:52, Zach Wegner wrote: >I had the same problems, but what I did was instead of making another function >for making/unmaking nullmoves, I set a flag so that I can make/unmake nullmoves >with the normal make/unmake functions. This way it never tries to move pieces >around when unmaking nullmoves. Also, you need to add a parameter to search() to >set when a line contains a nullmove. > >Zach This makes the most sense to me--treat null moves just like any other moves (have an entry in hist_dat, change ply, naturally change the side to move) except that no pieces are moved. Minimal code change + conceptually clear. You can have a global variable, e.g., "nullmoves", to indicate how many null moves are in the current line. Add 1 when makemove makes a nullmove, subtract... well, you get the idea. The parameter to search should indicate if a null move has JUST been played... most people will agree that it's a bad idea to try two null moves in a row. -Tom
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.