I do agree that Loop should be examined at least in the interest of fairness. However, I don't have it, and I have no interest in buying it or obtaining it illegally.Uri Blass wrote:1)I think that loop list may be a derivative of fruit.
The only evidence that I have is the correlation table from the ccrl
that shows higher correlation between fruit and list relative to other pair of programs.
I do not know know about people who tried to reverse engineer loop list
and report their results.
I remember that Fritz made a significant improvement at the fruit time from Fritz8 to Fritz9 so I suggest to check Fritz9 and later Fritz versions.
I think that doing "drug test" only to rybka is simply unfair.
I also will note that reverse engineering is very hard. Completely dissecting a program would take a very long time, and I'm afraid I don't have the skill. I was able to find what I did in Rybka in large part due to Strelka and the disassembly posted by Rick Fadden.
I was also under the impression from somewhere that Tord Romstad had seen the source. I can't remember why though, so I could very well be wrong.
Like it or not, those are the rules of the GPL. I agree that it's kind of silly to get in a rut over some 10 line function, but we're not just discussing the input_available function. The very first post in this thread doesn't mention any of that--only things that are directly related to choosing moves. Looking at the input_available function is just another drop of water in the pond. Though it is true that very many engines will have similar functions (even ZCT looks pretty similar), the probability is not 100%. So each little piece that we show to be the same between Fruit and Rybka 1.0 is just reducing the probability that Rybka is not a derivative.2)I also think that all the rules about GPL are unfair if rybka can be considered to be a derivative of fruit based on code that is not relevant to geneate moves like input_available() and they were part of the functions that were used as evidence.
Really though, this thread is getting pretty ridiculous. The issue isn't just a few lines of unimportant code. The original post showed areas where Rybka 1.0 has semantically identical code in the search logic. How many engines do you know limit the depth to 4 when there is only one legal move? How many do you know that mark a move as easy when at a certain depth it is more than 150 cp better than the next move? There are many more questions I could ask, and I will continue to until I get answers.