| |||||||||||||
What every C Programmer should know about undefined behavior #2/3What every C Programmer should know about undefined behavior #2/3Posted May 18, 2011 11:34 UTC (Wed) by Wol (guest, #4433)In reply to: What every C Programmer should know about undefined behavior #2/3 by HelloWorld Parent article: What every C Programmer should know about undefined behavior #2/3
>This is, and has always been, a bullshit argument. The fact that we can't write a program that will tell us whether some program will halt doesn't mean that we can't prove it for some specific program we care about.
Just because you've proved it in the imaginary world of maths doesn't mean diddley-squat. The ONLY valid proof in the real world is "well, we haven't been wrong yet - but there's always a first time ...".
Cheers,
(Log in to post comments)
What every C Programmer should know about undefined behavior #2/3 Posted May 18, 2011 14:22 UTC (Wed) by jd (guest, #26381) [Link]
Well, all programs are equal to a set of mathematical expressions. That can be proven and may well form a part of the battle against software patents since you can't patent mathematical expressions.
|
|||||||||||||