C++ should be good. But take it with double care. I would code a lot of unit tests. If test driven development is followed, I suppose it will be a good piece of software, and, at the end of the day, a pro product.
Test Driven Development, regression tests, profilling, code coverage, I would apply all that techniques to make it stable and solid. Java is a good alternative for testing algorithms, fast development, etc. But, I'm not sure at all, but I feel that a pro engine will never ends as a Java application. Perhaps, if you find out the way, you can use Java as a test bench, then code the final version on C++. Find out the way, in the sense of not adding a lot of overhead to maintain it. My 2 cents. --- Oliver Lewis <[EMAIL PROTECTED]> escribió: > Please go back to Java! Part of your initial aims > were to make good, well > commented code available to others. I was dismayed > when you started to > transition to C++, which may be the right choice if > you're working on your > own and happy to trade clarity / portability for > speed, but really detracts > from your other aims. Given you've got interns and > others coming in and out > of the project, I would have thought this would end > up being less > efficient. We're so far from strong amateur play in > Computer Go that it > seems much more important (and interesting) to focus > on implementing and > testing new ideas. > > _______________________________________________ > computer-go mailing list > computer-go@computer-go.org > http://www.computer-go.org/mailman/listinfo/computer-go/ __________________________________________________ Correo Yahoo! Espacio para todos tus mensajes, antivirus y antispam ¡gratis! ¡Abrí tu cuenta ya! - http://correo.yahoo.com.ar _______________________________________________ computer-go mailing list computer-go@computer-go.org http://www.computer-go.org/mailman/listinfo/computer-go/