summaryrefslogtreecommitdiff
path: root/chess-none.el
diff options
context:
space:
mode:
authorMario Lang <mlang@delysid.org>2014-04-18 13:32:04 +0200
committerMario Lang <mlang@delysid.org>2014-04-18 13:32:04 +0200
commita21f71e45ebf234601b01d0121d067f14a6b848c (patch)
tree63f03ed6404c66366cc3528b477d2d3f3694a537 /chess-none.el
parentb66e365a32c042a62311e614db25a807b6022302 (diff)
chess-pos-move: Really remove castling ability if rook has been moved.
This one was *very subtle. Looking at the code, we already tried to prevent this case, and it evenw orked for *some* instances. The problem is that castling flags are boolean in the position structure, chess-pos-can-castle determines the rook location from the position if castling flag is true. But we have already moved the rook around in chess-pos-move before we do the fixup stuff, so chess-pos-can-castle is just wrong in some cases. Fix is simple, call chess-pos-can-castle before we modify the position, and use these values later. This fixes the remaining perft mixmatches.
Diffstat (limited to 'chess-none.el')
0 files changed, 0 insertions, 0 deletions