On Fri, Sep 10, 2004 at 05:07:21PM -0400, Daniel Martin wrote:
> The problem with his code was that when Matthew Walton posted it to
> the mailing list, an extra space was inserted into the source. Since
> haskell is (or at least, is usually) a language where indentation is
> significant, this meant it didn't compile.
Thanks for the debugging. I suspected it was something like that, but
didn't know where to start, except to start learning Haskell.
Suggestions for future solution submitters:
1. If you're going to submit a solution in a format-sensitive language
e.g. python, submit it as an attachment, for obvious reasons.
2. Extra "debug" output from your script is great, but (a) send it to
STDERR and/or (b) use a "--verbose" option to your script to enable it.
There were a few solutions that I ignored because their output had extra
lines (messing up the string count) or because the output lines had
comments or extra data (confusing the code checking for balanced
strings).
3. If an output format is specified, adhere to it reasonably closely.
One great solution I saw displayed matching parens in matching colors; I
would have been grateful if they had keyed that functionality to a
"--color" command-line option, so I didn't have to write code to filter
out ANSI control sequences.
--
The obvious mathematical breakthrough [to break modern encryption]
would be development of an easy way to factor large prime numbers.
-- Bill Gates, _The Road Ahead_
|
