From b98bcf858ba0cac58d52b76eb1bea40e25adcaa1 Mon Sep 17 00:00:00 2001 From: Marco Costalba Date: Wed, 20 May 2009 14:40:50 +0200 Subject: [PATCH] Directly relate HistoryMax to OnePly This obsoletes some remainding comments. No functional change. Signed-off-by: Marco Costalba --- src/depth.h | 3 --- src/history.h | 6 +----- 2 files changed, 1 insertion(+), 8 deletions(-) diff --git a/src/depth.h b/src/depth.h index 9822289a..2e8e2179 100644 --- a/src/depth.h +++ b/src/depth.h @@ -35,9 +35,6 @@ enum Depth { //// Constants //// -/// Note: If OnePly is changed, the constant HistoryMax in history.h should -/// probably also be changed. - const Depth OnePly = Depth(2); diff --git a/src/history.h b/src/history.h index df56307b..ae834534 100644 --- a/src/history.h +++ b/src/history.h @@ -69,12 +69,8 @@ private: /// the effect that parts of the search tree which have been searched /// recently have a bigger importance for move ordering than the moves which /// have been searched a long time ago. -/// -/// Note that HistoryMax should probably be changed whenever the constant -/// OnePly in depth.h is changed. This is somewhat annoying. Perhaps it -/// would be better to scale down the history table at regular intervals? -const int HistoryMax = 50000; +const int HistoryMax = 25000 * OnePly; #endif // !defined(HISTORY_H_INCLUDED) -- 2.39.2