"Richard A. O'Keefe"
TL;DR - Haskell mistaken for pseudo-code, a case study on machine- checked specification for use in standards can't or won't be read by the people who need it (who aren't the people in this mailing list). My problem: I can't get this published.
The backhanded compliment: the last reviewer excoriated me for having too much pseudocode in my paper. (Despite the paper stating explicitly that ALL code in the paper was real code that had been executed.) You got it: Haskell doesn't look like a "real" programming language, but like something written for human comprehension during design.
Just a shot in the dark: would it help to put all the braces and semicolons in explicitly? :-) -- Jón Fairbairn Jon.Fairbairn@cl.cam.ac.uk