[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: computer-go: Most simple Go rules



Nick is right, its not a rule. You have to allow for long games. As long as no actual rule (superko) is violated, the game must be allowed to continue. I see no reason why it wouldn't be able to. Time will run out long before any data type overflows or storage medium is filled.

At 07:20 PM 6/26/2001, you wrote:
> -----Original Message-----
> From: Nick Wedd [mailto:nick@xxxxxxxxxxxxxxxxx]
> Sent: Tuesday, 26 June, 2001 16:18
> To: computer-go@xxxxxxxxxxxxxxxxx
> Subject: Re: computer-go: Most simple Go rules

> I think this [Tom's]code assumes that the referee program and both
> competitors
> will all be running on the same PC.  There are various snags
> with this.

It doesn't have to run on the same compuer. The player * could point to some
proxy that talks to the player running on a different machine. In fact, not
only it could but it should, for exactly the reasons Nick outlined.

> I don't like
>    const MAXMOVES=500;// a draw will be declared after this many moves
> This is not like anything in any published rule set.  It does
> not solve
> any problem.  It encourages unsporting behaviour.

Still Nick, what would you do if the players would want to run forever.
Current professional programs won't, but I may enter into a competition two
programs that I wrote and they would tend to do that. How would you want to
have it handled? Personally I'm neither for nor against the MAXMOVES=500,
just looking for your oppinion.

Adrian