[gnugo-devel] TRACE_READ_RESULTS

[bump]

The current CVS version

hash.c:87:5: warning: "TRACE_READ_RESULTS" is not defined

TRACE_READ_RESULTS was added by arend_5_5.13. It is
defined to be zero in cache.h. 

TRACE_READ_RESULTS is consulted in board.c, cache.c,
cache.h, hash.c and hash.h. Since cache.h includes
hash.h, it seems this parameter should be moved to
hash.h, then it will be defined in all included files.

Dan

Index: engine/cache.h
===================================================================
RCS file: /cvsroot/gnugo/gnugo/engine/cache.h,v
retrieving revision 1.46
diff -u -r1.46 cache.h
--- engine/cache.h      12 Apr 2004 15:28:22 -0000      1.46
+++ engine/cache.h      15 Apr 2004 00:32:31 -0000
@@ -115,9 +115,6 @@
 /*                    The old transposition table                   */
 
 
-/* Dump (almost) all read results. */
-#define TRACE_READ_RESULTS 0
-
 /*
  * This struct contains the attack / defense point and the result.
  * It is kept in a linked list, and each position has a list of 
Index: engine/hash.h
===================================================================
RCS file: /cvsroot/gnugo/gnugo/engine/hash.h,v
retrieving revision 1.25
diff -u -r1.25 hash.h
--- engine/hash.h       8 Feb 2004 00:30:08 -0000       1.25
+++ engine/hash.h       15 Apr 2004 00:32:31 -0000
@@ -58,6 +58,9 @@
 /* for testing: Enables a lot of checks. */
 #define CHECK_HASHING 0
 
+/* Dump (almost) all read results. */
+#define TRACE_READ_RESULTS 0
+
 /* How many bits should be used at least for hashing? Set this to 32 for
  * some memory save and speedup, at the cost of occasional irreproducable
  * mistakes (and possibly assertion failures).