4. Keep a singly linked list of stones for each group and keep an
additional pointer for each group to the last element of the list. This is
what I do in Many Faces.
David
> -Original Message-
> From: computer-go-boun...@computer-go.org [mailto:computer-go-
> boun...@computer-go.org] On
On Sat, 2009-07-11 at 08:57 -0700, David Fotland wrote:
> 4. Keep a singly linked list of stones for each group and keep an
> additional pointer for each group to the last element of the list. This is
> what I do in Many Faces.
5) Use a bitmap. This costs a bit more memory (if one bitmap is
allo
Isn't 4. similar to doubly linked lists? You have to keep almost as
many pointers as there are points on the board at most. How do you
effectively store the pointers to only use as few as possible?
I don't see how 5) is good for removing groups. Are there other uses
for the bitmaps?
Am 11
computer-go.org] On Behalf Of Isaac Deutsch
> Sent: Saturday, July 11, 2009 9:46 AM
> To: computer-go
> Subject: Re: [computer-go] Keep lists of stones in a group?
>
> Isn't 4. similar to doubly linked lists? You have to keep almost as
> many pointers as there are points on t
