[gnugo-devel] worm patch

[Gunnar Farneback]

I've put up a big patch at
http://www.lysator.liu.se/~gunnar/gnugo/patches/gunnar_1_10.1.gz

This primarily changes the handling of attack, defense, attack threat,
and defense threat points by allowing up to MAX_TACTICAL_POINTS
(currently 10) of each kind to be stored in the worm[] array, together
with result codes (0, KO_A, KO_B, WIN). Previously only one of each of
these could be stored in the worm[] array and additional moves had to
be handled by the move_reason code. This arrangement was kind of
unwieldy and by doing this change I could eliminate some code pieces.
I have also made a cleanup of the patterns in attack.db and
defense.db. The latter in particular had a lot of redundancy, a
remnant from the 2.6 days. There are a few additional spinoff
improvements as well, but nothing significant. The regressions should
be okay with one failure and a few passes.

- new function count_common_libs() in board.c
- struct worm_data now keeps track of all attack, defense, attack threat,
  and defense threat points
- remove_attack_move() and remove_defense_move() removed
- attack_move_known(), defense_move_known(), attack_threat_move_known(),
  and defense_threat_move_known() moved from move_reasons.c to worm.c
- change_attack() and change_defense() moved from utils.c to worm.c
- new function change_attack_threat() and change_defense_threat() in
  worm.c
- new function worm_reasons() in worm.c
- trace messages in worm.c changed to DEBUG_WORMS messages
- remove_opponent_attack_and_defense_moves() and
  do_remove_false_attack_and_defense_moves() removed from move_reasons.c
- NON_ATTACK_MOVE and NON_DEFEND_MOVE move reasons removed
- try a little harder to find attack threats
- attack.db and defense.db revised
- indirect_helper() removed from helpers.c
- tuning

I've added this to CVS.

/Gunnar