Take Two

I have been meaning to address the warts of GGTL, my generic game-tree library, for some time. Firstly, it has no business dictating how users define their datastructures. Secondly, it is not flexible enough.

I am also wondering if GGTL is currently trying to do too much. Should GGTL2 also worry about save and resume, or should it focus only on the game-tree search? I am currently in favour of dropping those particular features. If that happens I will probably end up renaming the project to reflect the narrower focus.

I plan to use Test-Driven Development (TDD) to develop GGTL2 (or whatever the name will be) using. Unfortunately, the C implementations of xUnit I have seen all suck; there is too much work writing the damn tests.

Luckily, there are alternatives; Nik Clayton has written libtap, a C library implementing the Test Anything Protocol (TAP) as used by Perl’s Test::Harness.