From: Marco Costalba <mcostalba@gmail.com>
Date: Mon, 10 Nov 2008 18:04:15 +0000 (+0100)
Subject: Fix in ok_to_history(): castle move is not a capture
X-Git-Url: https://git.sesse.net/?p=stockfish;a=commitdiff_plain;h=2d4e2bc62a4ee3fa93004755d4b93fa466d1e93e

Fix in ok_to_history(): castle move is not a capture

It is erroneusly considered a capture because king
moves on the same square of the rook.

Use the correct function Position::move_is_capture()
instead of the open coded (and buggy) one.

Signed-off-by: Marco Costalba <mcostalba@gmail.com>
---

diff --git a/src/search.cpp b/src/search.cpp
index 5b4913c3..e28b866e 100644
--- a/src/search.cpp
+++ b/src/search.cpp
@@ -2155,13 +2155,11 @@ namespace {
 
 
   // ok_to_history() returns true if a move m can be stored
-  // in history. Should be a non capturing move.
+  // in history. Should be a non capturing move nor a promotion.
 
   bool ok_to_history(const Position& pos, Move m) {
 
-    return    pos.square_is_empty(move_to(m))
-          && !move_promotion(m)
-          && !move_is_ep(m);
+    return !pos.move_is_capture(m) && !move_promotion(m);
   }