Permalink
Browse files

Order bad captures by SEE value

We have already calculated it, so just sorting the
moves adds a very little overhead.

Signed-off-by: Marco Costalba <mcostalba@gmail.com>
  • Loading branch information...
mcostalba committed May 28, 2009
1 parent 738bf66 commit bafb9f1a25204d06960a44f0637736edce233629
Showing with 3 additions and 1 deletion.
  1. +3 −1 src/movepick.cpp
View
@@ -162,7 +162,9 @@ Move MovePicker::get_next_move() {
break;
case PH_BAD_CAPTURES:
- // It's probably a good idea to use SEE move ordering here. FIXME
+ // Bad captures SEE value is already calculated by score_captures()
+ // so just sort them to get SEE move ordering.
+ std::sort(badCaptures, badCaptures + numOfBadCaptures);
movesPicked = 0;
break;

0 comments on commit bafb9f1

Please sign in to comment.