3 ms·
The main reason I've found for programs being 'correct' is that the range of actual inputs for programs is severely limited. Most programs see inputs that are
by buzzkillington 7y ago
The main reason I've found for programs being 'correct' is that the range of actual inputs for programs is severely limited.
Most programs see inputs that are similar enough to previous inputs that the latent bugs are never triggered, or at worst triggered one at a time.
Running programs far outside their expected parameters on the other hand has nearly always lead to disaster.
- amelius 7y agoWould you say that a typical web-browser (a complicated piece of software) always sees the same kind of input?
- buzzkillington 7y agoPretty much. Throwing [0] to chrome and firefox has made made them hang for 5 minutes so far. Generating the HTML took under a second and 13MB, large, but not larger than the fatter webpages out there. In terms of input browsers don't see but should be able to parse you can't get much simpler than this. [0] In Guile2.x: (define print (lambda (x) (display x) (newline))) (define div-hell (lambda (n) (cond ((eq? n 0) (print "TEXT")) (else (print "<div>") (div-hell (- n 1)) (print "</div>"))))) (print "<html><header><title>DIV HELL</title></header><body>") (div-hell 1000000) (print "</body></html>")