From 3189fb484dcfe4efe42b2b30e529389db9dd0d00 Mon Sep 17 00:00:00 2001 From: Simon Tatham Date: Tue, 6 Nov 2018 18:34:47 +0000 Subject: [PATCH] Fix an inaccurate comment. latin_solver_diff_set takes a boolean input parameter to indicate whether the 'Extreme'-level variant of set elimination is permitted. But it's commented in the header file as having a boolean _output_ parameter which it sets if it _ended up_ using that variant. Probably the latter was how it worked in an early draft, and I changed my mind later without changing the comment. --- latin.h | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/latin.h b/latin.h index e13050e..747cfb6 100644 --- a/latin.h +++ b/latin.h @@ -78,8 +78,8 @@ void latin_solver_free_scratch(struct latin_solver_scratch *scratch); /* Looped positional elimination */ int latin_solver_diff_simple(struct latin_solver *solver); -/* Looped set elimination; *extreme is set if it used - * the more difficult single-number elimination. */ +/* Looped set elimination; extreme permits use of the more difficult + * single-number elimination. */ int latin_solver_diff_set(struct latin_solver *solver, struct latin_solver_scratch *scratch, int extreme);