nando_3_9.4b (was: RE: [gnugo-devel] nando_3_9.4)

[Portela Fernand]

Dan wrote:

> The alternative is to run cvs update before you make the patch,
> then you will have to resolve the conflicts yourself.

Ok, I did it this way.

- includes and supercedes nando_3_9.4 and nando_3_9.4a
- dragon status is set to ALIVE in case of GAIN/LOSS attack/defense
  codes
- .what field for OWL_ATTACK_MOVE_GAIN and OWL_DEFEND_MOVE_LOSS is now
  an index into the either_data array, which is reused for its .what1
  and .what2 fields. These moves are similar to EITHER_MOVE, so this is
  logical. And in case it's needed, it will be easy to create a separate
  array.
- added a couple supporting functions : add_gain_move(), add_loss_move()
  and find_pair_data()
- extended and renamed catalog_worm() to something else to prevent
  confusion. The older code is kept as it was, i.e. disabled by a #if 0
  directive.

I haven't run the full set of regression tests yet (right now, my box is
doing trevorc.tst) So far, the blunder:12, blunder:20 and trevor:290 passes
are still there.

/nando

nando_3_9.4b.diff
Description: Binary data