From 87139d018c86211a0636cb1bcedf9572670d9ba6 Mon Sep 17 00:00:00 2001 From: Marco Costalba Date: Sat, 31 Jul 2010 07:29:29 +0100 Subject: [PATCH] Always use ss->bestMove to store ply best move Instead of ss->currentMove. It is more consistent and clear to understand. Remark by Ralph Stoesser. No functional change. Signed-off-by: Marco Costalba --- src/search.cpp | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/src/search.cpp b/src/search.cpp index 588f76f3..66b1d65d 100644 --- a/src/search.cpp +++ b/src/search.cpp @@ -1062,7 +1062,7 @@ namespace { // Refresh tte entry to avoid aging TT.store(posKey, tte->value(), tte->type(), tte->depth(), ttMove, tte->static_value(), tte->king_danger()); - ss->currentMove = ttMove; // Can be MOVE_NONE + ss->bestMove = ttMove; // Can be MOVE_NONE return value_from_tt(tte->value(), ply); } @@ -1176,7 +1176,7 @@ namespace { if (nullValue == value_mated_in(ply + 2)) mateThreat = true; - threatMove = (ss+1)->currentMove; + threatMove = (ss+1)->bestMove; if ( depth < ThreatDepth && (ss-1)->reduction && connected_moves(pos, (ss-1)->currentMove, threatMove)) @@ -1460,7 +1460,7 @@ namespace { if (!PvNode && tte && ok_to_use_TT(tte, depth, beta, ply)) { - ss->currentMove = ttMove; // Can be MOVE_NONE + ss->bestMove = ttMove; // Can be MOVE_NONE return value_from_tt(tte->value(), ply); } -- 2.39.2