On Aug 15, 2009, at 8:52 AM, <w...@swcp.com> <w...@swcp.com> wrote:
You will just have to jump in and read some code or write your own to fully understand. I recommend reading the gnugo source, which is pretty darn good.
But that's exactly the kind of work you'd want to avoid if there's no reasonable grounds for believing it will gain any performance. Especially if it will clearly be very memory-inefficient.
Mark _______________________________________________ computer-go mailing list computer-go@computer-go.org http://www.computer-go.org/mailman/listinfo/computer-go/
