TalkChess.com

Should be

r3rbk1/1q1b1ppp/3ppB2/1p6/p3P3/PB2R1Q1/1PP2PPP/4R1K1 w

Written by France's Fabien Letouzey in object-oriented C++ Actually the Fruit code is not object oriented by the common definition of that term (not a single class is used). Furthermore it uses only very few features of C++ and might as well have been written in C. I tend to think of the Fruit sour...

I wonder why it was necessary to design a new protocol for this server. FICS works fine and is well tested. Furthermore it is cross platform and supported by many clients both closed and open source ones. What is the advantage of a new protocol for which there is only a proprietary windows client? M...

Linux version of 1.0a3 seems to work fine on dual core 64bit

I only tried a gcc compile.

with winboard/polyglot on a core2 duo, there's no way to prevent grapefruit from using both cores.

In polyglot you can set UCI options.

About Polyglot book format:i dont have any idea,i will think about it.

Well if you think about it I am curious to learn about practical obstacles. I am fairly ignorant about testing myself.

Best regards,
Michel

Hi Sedat, Are your tournaments only open to ctg books? I am asking since some people are trying to promote the completely free and open Polyglot book format. This format is easy to implement and is already understood by a number of programs (most recently Hamsters). There are a number of publicly av...

BTW running way more threads than processors is not a good way to debug. You burn 90% of the total time spinning on locks which is a total waste We all know that running more active threads than processes costs performance. But we are talking about testing here. Running an engine with debug code en...

But you will _never_ with any chess program run more processes than you have processors. And I do mean _never_.

I do not agree. This is very useful for testing.

Threads doesn't work, not all programs use threads I know you'd say that :) But processes and threads are basically the same thing. On Linux threads are created by the clone call which is a sort of fork except that all memory is (or can be) shared. Internally everything is managed by the scheduler....