[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [gnugo-devel] use of LOSE in reading.c
From: |
Gunnar Farneback |
Subject: |
Re: [gnugo-devel] use of LOSE in reading.c |
Date: |
Wed, 18 Sep 2002 23:14:29 +0200 |
User-agent: |
EMH/1.14.1 SEMI/1.14.3 (Ushinoya) FLIM/1.14.2 (Yagi-Nishiguchi) APEL/10.3 Emacs/20.7 (sparc-sun-solaris2.7) (with unibyte mode) |
Teun wrote:
> > Sorry, but we're quite happy to use 0 in this context.
>
> Who is we? Doesn't include me apparently.
You're right that I should only have spoken for myself. I was thinking
of me and Dan who have done most of the work on the reading code. When
these symbolic codes were first introduced, Dan wrote a message (dated
May 25, 2001) saying:
| These changes have been discussed in this list since
| Monday. Look for the thread ``A reading nuance.''
|
| Old scheme New scheme
|
| 1 WIN = 3
| 2 KO_A = 2
| 3 KO_B = 1
| 0 0
|
| There are symbolic names for the nonzero return
| codes. If failure had a symbolic name it would
| be LOSE but I thought it was better just to
| call it 0.
> What is the point of the #define LOSE in gnugo.h then?
Not much at all, as far as I can tell.
/Gunnar