🚀 go-pugleaf

After more experiments regarding the different node counts issue, this
is what I discovered.  Of course, the first thing that causes a difference
is the cache.  I agree that this shouldn't, but haven't been able to 
figure out why it did.

Even after disabling the cache, Tom Vijlbrief reported that nodes counts
are still differing after an "undo" and a "go".  This time the difference
arises only if a capture is undo (non captures will give the same node 
count).  The reason is because the PieceList array is now arranged 
differently.  (This array contains the pieces that are remaining on the
board.  Undoing a capture will yield a piecelist array that has the
captured piece in a new location in the array then the original array).
With a slightly different PieceList array, the move generation order is 
changed.  Subsequently a difference sequence of moves will give rise
to different node counts during the search.

If we were to change genmoves.c MoveList() routine to search the board
rather than the PieceList during the move generation, the nodes counts
report will now be correct.

Once I figure out why having cache and not having cache gives rise to
different node counts, I will report the finding.

Regards.

Kong Sian