I was mislead by the same thing when I started to examine Glaurung's source. However the answer is trivial. Ucioptions shall always (whether they are modified by user or not) override the ones hardcoded in source.
The bad thing here is that people examining source for first time almost certainly read wrong values for the default extensions
zamar wrote:I was mislead by the same thing when I started to examine Glaurung's source. However the answer is trivial. Ucioptions shall always (whether they are modified by user or not) override the ones hardcoded in source.
The bad thing here is that people examining source for first time almost certainly read wrong values for the default extensions
I think that what "uci" is reporting as the defaults aren't really the defaults.
Hi Gian-Carlo,
Joona is right: The values of the UCI options always override the default values of the variables in search.cpp. Sometimes I am just too lazy to update both places. In one sense, this isn't a bug, because the program uses the default values I intend for the above extensions. From another perspective, it is a bug, because readability of the code for new users is just as important as how the program plays.
I should probably fix this somehow. Just changing the initial values of the variables in search.cpp would be easy, but in that case I would certainly make a similar mistake some time in the future. It's probably better to just leave the variables uninitialized in search.cpp, and add a comment explaining that they are read from UCI parameters.