[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [gnugo-devel] owl stack
From: |
Paul Pogonyshev |
Subject: |
Re: [gnugo-devel] owl stack |
Date: |
Sat, 10 May 2003 14:27:49 -0400 |
User-agent: |
KMail/1.5.9 |
Arend wrote:
> Gunnar wrote:
> > Paul wrote:
> > > before i go deeper into the matter i want to ask: what for do we
> > > push the complete local_owl_data structure each time owl makes a
> > > move? from a quick glance it seems to me that at least my_eye[],
> > > half_eye[], lunch*[], inessential[] and safe_move_cache[] are
> > > recomputed from scratch at each move (and they probably take over
> > > 90% of the structure).
> >
> > Because we need them after the recursive owl call has returned. Notice
> > that most of the constraint evaluation is done "just in time" in order
> > to avoid doing computations we don't need.
>
> But that is only sufficient reason to store them in separate places.
> No need to copy the eye data of (stackp) to the eye data of (stackp+1).
yes, maybe i should have asked "why do we copy" instead of "why do
we push" (and this is what i meant).
so i'll make a patch (and if anything is wrong i'll see it :).
Paul