From the looks of the code, puzzle generation is dependent on a good solve
method:
[GNUDoku.C]
void GNUDoku::generatePuzzle(float const difficulty, int const seed){
...
Sudoku::solve(stack, top, flag_data, visited);
...
}
Glancing at the solve algorithm, it looks like the solve method
Package: gnudoku
Version: 0.93-1
Followup-For: Bug #351043
This is a report from my second Etch machine. As gnudoku is 9 days old
and about to enter testing but my bug hasn't been confirmed, I've tried
to reproduce here. I succeeded at the first attempt and am attaching the
following files:
Package: gnudoku
Version: 0.93-1
Followup-For: Bug #351043
Subject: gnudoku: Reproduced
Followup-For: Bug #351043
Package: gnudoku
Version: 0.93-1
This is a report from my second Etch machine. As gnudoku is 9 days old
and about to enter testing but my bug hasn't been confirmed, I've tried
to
Please excuse me if this message doesn't come through properly, I have
no idea how the debian bug tracker is meant to work, and no instructions
were prominent.
The generation of ambiguous puzzles is a known bug. None of the authors
has the time to do anything about it at this time.
However, I
tags 351043 +help
thanks
I don't know how to deal with this bug. I am quite surprised of its
severity since I totally agree with John.
Of course I don't want to start a severity war so I just mark the bug
with the help tag.
The generation of ambiguous puzzles is a known bug. None of the
Package: gnudoku
Version: 0.93-1
Severity: important
I have tried 2 puzzles in gnudoku generated with the defaults
(difficulty between Easy and Hard). Both puzzles generated have multiple
solutions. In the first case, I realized the problem 7 digits away from
completion, so the problem is pretty
6 matches
Mail list logo
