rvida wrote:Btw it is hard to explain (at least for me with my poor english) without giving out my source code...rvida wrote:I do...mcostalba wrote:But why when you receive a ponder hit you don't simply switch to normal search ? SF stops on ponder hit only if the flag stopOnPonderhit is raised.rvida wrote: Without the delay the engine does nothing because the search is stopped before it has started:
Just curious.
But there is a case when 'go ponder' command signals the "thinking" thread that we've got I job, but before the OS scheduler wakes the thread we already cancel the request because of a subsequent ponderhit
Now I've got an idea... If you are interested enough, we can exchange our source codes. (I already have the sources of SF 2.0 but I am ready for an upgrade)
I can send you my sources in the hope that we can share in the spirit of Fabien's "readme.txt"
Anyway, I have decided to launch a new initiative. What's more boring
than reading one's own code at 3am tracking down a bug that might not
even exist, know what I mean? I have the solution: let's fix
each others bugs!
The new operation is called "Fix my Bugs and I Fix Yours!" (patent
pending). It works as follows:
1) You fix one of my bugs (excluding null move) before 2005/09/01
00:00 UTC (the acronym that does not mean anything in either
English or French, so that both parties are equally disappointed).
2) I select the most artistic bug fix after the date limit. A jury
will be nominated if necessary.
3) I fix a bug of your choice in your program (excluding "it plays bad
moves"), it's that simple!
+1