Re: [racket] A puzzle

2011-01-20 Thread Gregory Cooper
If you need to examine a large set of execution sequences, a debugger wouldn't really help. I think you want a custom evaluator written to explore exhaustively the space of possible context switches (e.g., via backtracking). Greg On Wed, Jan 19, 2011 at 4:26 PM, Mark Engelberg wrote: > Hmm, I d

Re: [racket] This is not a solution! Re: A puzzle

2011-01-20 Thread engineer
Part of what makes MIT Mystery Hunt puzzles so hard is that even the questions aren't often obvious. > I see a lot of code, but what's the puzzle. Presumably > there's some kind of question that has to be answered about it? > > -- hendrik > _ >

Re: [racket] A puzzle

2011-01-20 Thread Matthias Felleisen
Anyone up for a dissertation? Multi-stepping debugging is, eh, pushing it. On Jan 19, 2011, at 2:43 PM, Doug Orleans wrote: > The following program was a puzzle in the 2011 MIT Mystery Hunt held last > weekend. (I'm not linking directly to the site because they posted a > solution and I