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

Re: [computer-go] Modern brute force search in go

To: computer-go@xxxxxxxxxxxxxxx
Subject: Re: [computer-go] Modern brute force search in go
From: Don Dailey <drd@xxxxxxx>
Date: Sun, 7 Nov 2004 19:05:21 -0500
Cc: computer-go@xxxxxxxxxxxxxxx
Delivered-to: computer-go@xxxxxxxxxxxxxxxxx
In-reply-to: <3.0.32.20041108003837.0112eab0@xxxxxxxxxxxxxxxxx> (message fromVincent Diepeveen on Mon, 08 Nov 2004 00:38:38 +0100)
List-archive: <http://computer-go.org/pipermail/computer-go>
List-help: <mailto:computer-go-request@xxxxxxxxxxxxxxxxx?subject=help>
List-id: computer-go <computer-go.computer-go.org>
List-post: <mailto:computer-go@xxxxxxxxxxxxxxxxx>
List-subscribe: <http://hosting.midvalleyhosting.com/mailman/listinfo/computer-go>,<mailto:computer-go-request@xxxxxxxxxxxxxxxxx?subject=subscribe>
List-unsubscribe: <http://hosting.midvalleyhosting.com/mailman/listinfo/computer-go>,<mailto:computer-go-request@xxxxxxxxxxxxxxxxx?subject=unsubscribe>
References: <3.0.32.20041108003837.0112eab0@xxxxxxxxxxxxxxxxx>
Reply-to: drd@xxxxxxx,computer-go <computer-go@xxxxxxxxxxxxxxx>
Sender: computer-go-bounces@xxxxxxxxxxxxxxx

> In chess we do not allow nullmove when side to move is in check.

But in principle we  are.  When a king is in check,  a null move would
prove  the king  is threatened,  but we  know that.   So  not allowing
nullmove in  check is just  an implementation shortcut, not  a special
case distinction of any kind.

- Don
_______________________________________________
computer-go mailing list
computer-go@xxxxxxxxxxxxxxxxx
http://www.computer-go.org/mailman/listinfo/computer-go/

References:
- RE: [computer-go] Modern brute force search in go
  - From: Vincent Diepeveen

Prev by Date: Re: [computer-go] Pattern Matcher
Next by Date: Re: [computer-go] Pattern Matcher
Previous by thread: RE: [computer-go] Modern brute force search in go
Next by thread: Re: [computer-go] Modern brute force search in go
Index(es):
- Date
- Thread