Re: [computer-go] Data structures for Go

[Don Dailey <drd@xxxxxxx>]

Of course it's  also possible to push and pop  selective pieces of the
state and undo others.  It might even  be that some of you do that.  I
can imagine  that if I had  undo, but part  of my state was  small but
complex, I  might just  copy and push  that part  of the state  onto a
stack as is to avoid the complexity of undoing it.

The decision you make will tend to push you in certain directions.  In
my program I am pretty stingy  about adding extra state because I know
it gets  moved around a lot, whereas  I would be a  little more sloppy
and less  concerned if I had an  undo routine.  The other  side of the
coin  is  that  if  you  like   to  experiment  a  lot,  you  will  be
significantly  more  productive  without  undo.   In  fact,  you  will
probably  be   willing  to  try  things  you   might  otherwise  avoid
(especially if you are lazy like I am.)

Since  I am not  a Go  software professional,  I usually  won't bother
trying anything  that I  can't implement and  debug within a couple of
hours unless I have a good indication that it's a good thing.

Don

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