>> particular scenario, a basic file compare would be fine. (We would 
>> probably have to formally test the correctness of the compare program 
>> though!)
> 
> You could probably do that if you wrote it in Haskell. ;-)

I *have*, in fact, written such a program in Haskell. We're currently in 
the process of formally testing it. For something completely different, 
as it happens...

(And yes, it had a bug. I forgot to open the files in binary mode, so it 
was doing line end conversions. It also stopped processing the file when 
it reached a certain octet sequence. I wonder what other bugs we'll find?)

> Ask to clarify. Or guess, and ask them to confirm.
> 
> Not that it helps. I once spent a couple weeks and did 30 pages of UI 
> design, showed it to the person in charge, had her initial each page as 
> being right, and when the program was all done, she comes back with "OK, 
> now let's work out what the screens should look like."  Hey, b___h, if I 
> hadn't hardcoded the screens, I wouldn't be asking you to read them, now 
> would I?  (And yes, everyone thought she was a b___h, but she was 
> sleeping with the CEO, so...)

Damn. I'm not sleeping with anybody. :-(

-- 
http://blog.orphi.me.uk/
http://www.zazzle.com/MathematicalOrchid*

Post a reply to this message