On Fri, 9 May 2008 09:57:41 -0700 (PDT), Sanny
wrote:

Yes, I will see if that can be corrected. It is very difficult to
modify the code as changing one line of code brings new Bugs and then
a week is wasted in correcting the Bugs.

That statement tells me quite at least 2 things:

1) There's a lot of copy and paste in your code (parts tend to look
alike, with minor modifications... some question as to whether making
a change is the right one).
2) You're probably not using the benefits of Java. Your display might
be OO, but I doubt that your chess analysis part did. What I know
about some contemporary chess engines (the company I work for built
the boards for Deep Blue) is that they evaluate each space.

You can score the piece count, but you also can score position...
Simplistically by how many squares are controlled. You only have 3
different kind of squares.
Also I have to agree with what someone else said. For testing
purposes, you really should work on handling position notation. One of
the beauties of chess is the state of the game can store in so few
bytes (64 and be comfortable). If you have a position that is, say, a
mate in 5, you can try that position against different versions (and
load it against different opponents as well).
Checks and draws should be some sort of function... I forget whether
you play a particular sound when the person is in check, but you can
use it for that, and also to put a '+' in the notation (or '#' for
checkmate).



Its like when we fly Kites. When the threads messup how difficult it
is to correct the jumbeled threads.

This Program is so large that if I have to read whole program line by
line, it will take me full day. So its very difficult to go through
all the codes and correct them.

200K isn't that large, even for a one-person project.




Bye
Sanny