Paul wrote: > > I object. In a future multithreaded version one would probably want to > > use multiple boards within a single engine instance, e.g. to make > > parallell tactical reading. Then this naming wouldn't make much sense. > > OK, what names do you propose?
Although it's already in use, I think "struct board_state" is a fairly good name. As for the name of the pointer being passed around I prefer something short since it's going to be typed a lot, maybe even just "b". /Gunnar _______________________________________________ gnugo-devel mailing list [email protected] http://lists.gnu.org/mailman/listinfo/gnugo-devel
