Re: computer-go: unmake move?

["Vlad Dumitrescu" <vladdu@xxxxxxxxxxx>]

> What I should probably do is  to profile my  code and measure the time
> spent making a move  and how much of  this  time is spent  copying the
> state.  Whether this turns out good for me or not  though, it would be
> no guarantee that others would get the same  results.
Hi

Just my 2 pence worth... In my experience, there is a programming proverb 
that is just as valid as any Go proverb:

Don't bother with performance from the beginning; keep the code clean and 
easily debuggable and maintainable. When you have a working program, then 
you can start profiling - in most cases the time hogs are not the ones one 
would expect!

Good luck!
/Vlad

________________________________________________________________________
Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com