4 ms·
One way to satisfy AlanT's spec is to choose a "non-standard" language to write this this "Bug Finder" for. If the language has the strong normalization proper
by vegashacker 18y ago
One way to satisfy AlanT's spec is to choose a "non-standard" language to write this this "Bug Finder" for. If the language has the strong normalization property (http://en.wikipedia.org/wiki/Normalization_property http://en.wikipedia.org/wiki/Normalization_property), then the requested debugger is quite simple:
(define (halt? p) #t)
(As for error checking, assuming this means, say, type errors, I think if you choose a language like the typed lambda calculus that's easy too.)
- icky 18y agoIf you look at "sleep"'s response: Dear Sir, You have found the right person to do the job. I am a representative of a company that has recently completed a large enterprise commercial project related to the development of a HaltLib.NET library that is meant specifically to solve the problem of interest to you, and I am ready to share my experiences and code. Note that our library works for a wide variety of programming languages, including, but not limited to, HTML, XML, PNG, CSV, SQL, BNF, Regular Expressions and even "Field=Value" .property file formats. I guarantee you maximally efficient and clean code on this project. You'll note that he doesn't list any Turing-complete languages. (The implementation will almost certainly look like yours). :P