NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

## All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.

Full
Abbreviated
Hidden
• #### Sudoku and Quantum::Superpositions(Score:1)

My family is also in thrall of Sudoku and I also have the same feeling about it being more fun to write a Perl script to solve them. I was thinking more along the lines of a branch-and-bound algorithm (e.g. the Knapsack problem) but Q::S looks even more fun.
• #### Q::S is iterative for some time now(Score:1)

What exactly did you mean by the recursive nature? Not knowing what you might have in mind for the solver, it still may be recursive but normal use has been iterative for some time now.
• #### Re:Q::S is iterative for some time now(Score:1)

According to the documentation (2.02):

More interestingly, since the individual states of a superposition are scalar values and a superposition is itself a scalar value, a superposition may have states that are themselves superpositions:

``` \$ideal = any( all("tall", "rich", handsome"), all("rich", "old"), all("smart", "Australian", "rich")); ```

Operations involving such a composite superposition operate recursively and in parallel on each its states individually and then recompose the result.

I thought to

--
-QM

Quantum Mechanics: The dreams stuff is made of

• #### Sudoku and Quantum::Superpositions(Score:1)

I thought about the same thing a while ago. I didn't manage to code it using Q::S, so I ended up writing a simple implementation i.e. guessing and checking the constraints.

If you got an implementation using Q::S I'd really like to see it; maybe you could post it here.

PS: Could you post a link to the solver using bit vectors? That one sounds interesting too.

Thanks
Martin
• #### Re: Sudoku and Quantum::Superpositions(Score:1)

The Q::S implementation that I qualified as "just a bit vector": SuDoKu Solver [perlmonks.org]. I don't know if you agree with that. A literal `vector` implementation could be faster than Q::S, as there'd be less overhead, etc.

I haven't worked on this much since my original post, and I haven't made any breakthroughs with Q::S on it. I got distracted into AI::Prolog, which also looks interesting. I guess I'm more interested in how to ask the question (ala Prolog) than what the answer actually looks like.