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>
mcostalba · May 29, 2009 · bafb9f1 · bafb9f1
1 parent 738bf66
commit bafb9f1
Showing 1 changed file with 3 additions and 1 deletion.
diff --git a/src/movepick.cpp b/src/movepick.cpp
@@ -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;