Hi Jon, nice work. I really don't have the to do any real testing until next week. So for now just a couple of short comments:
a) have you compared the sgf files of analyzed matches between the 0.15 and current branches? b) from a code maintenance point of view having only one thread implementation would be best. Are there any advantage of windows threads over gthreads? If you really have to use functions from pthreads I think it would be better not to mix them with glib. c) lets remove the REDUCTION code. My guess is that it is largely unused and at some point will stop working anyway. d) gnubg compiles with minor changes on linux with or without changes, but there is a problem with makebearoff and the other utility programs: when multithread in config.h is enabled eval.c implies multithread.c, which implies gnubg.c and gnubg.c has it's own main function. e) when the code becomes stable I think it would be nice to be able to compile threads in always and to enable them at startup or when the user wishes to. Then on both windows and in linux distributions only one binary would be needed. Christian. _______________________________________________ Bug-gnubg mailing list [email protected] http://lists.gnu.org/mailman/listinfo/bug-gnubg
