Re: FruitFly 1.1
Posted: Tue Jul 24, 2012 10:32 pm
nice job , aggressive bold moves
Since when are you in a position to criticize the Smash author? It's pretty strong and SMP, which is no easy task.(I still have no idea how the author got it to play chess, for instance it has switch...cases in the search. Huge bottle neck)
switch/case can be fast, for many elements it's very fast because the compiler generates a jump table. From my experiments some time ago in a specific case switch/case outperformed virtual methods in C++. So I don't see a "huge bottleneck".ZirconiumX wrote:(I still have no idea how the author got it to play chess, for instance it has switch...cases in the search. Huge bottle neck)
Haven't looked at Smash's code so don't know what switch you're referring to, but e.g. Scorpio has an iterative search rather than recursive (atleast had), that is lots of switches and gotos in the search. In theory it's actually a performance boost, not a bottle neck. If you can do it right that is, makes for completely unreadable code...ZirconiumX wrote:(I still have no idea how the author got it to play chess, for instance it has switch...cases in the search. Huge bottle neck)
Sorry, I did not know.Richard Allbert wrote:Since when was switch a bottleneck? Crafty has a big switch in MakeMove.
It is a technical masterpiece. How it manages to do so, I do not know, because the code is rather hard on the eyes.Smash is a really good job imho.
I made my decision based on a) the ease of getting its source, and b) strength.Since when are you in a position to criticize the Smash author? It's pretty strong and SMP, which is no easy task.(I still have no idea how the author got it to play chess, for instance it has switch...cases in the search. Huge bottle neck)
Fine. Everyone in the world can be harsh on me.Agree with Lucas, patience has run out.