Re: Disproof of the Halting Problem's Conclusion
From: Isaac To (iketo2_at_netscape.net)
Date: 07/24/04
- Next message: Mitch Harris: "Re: Disproof of the Halting Problem's Conclusion"
- Previous message: Alex Vinokur: "Re: Disproof of the Halting Problem's Conclusion"
- In reply to: Peter Olcott: "Re: Disproof of the Halting Problem's Conclusion"
- Next in thread: Peter Olcott: "Re: Disproof of the Halting Problem's Conclusion"
- Reply: Peter Olcott: "Re: Disproof of the Halting Problem's Conclusion"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: 24 Jul 2004 23:04:38 +0800
>>>>> "Peter" == Peter Olcott <olcott@worldnet.att.net> writes:
Peter> Let's make a little analogy here. You can't ever make a
Peter> program that runs correctly because it is trivial to smash
Peter> the computer making the program not run correctly.
Smashing into a computer change the interpretation of the answers of
the computer. The modifications we talked about doesn't.
Peter> Exactly how does the fact that you can corrupt one program
Peter> in any way effect the capability of the original
Peter> uncorrupted program?
Your whole point is that "if you modify my halting solver to return a
boolean value, then your result about my halting solver can't exists
does not carry to my program, because it's a different program." This
would be correct if my modification make the programs answer
differently---i.e., some input that the original program would answer
"yes", say on the screen, would cause the modified program to return
"no"; or vice-versa.
But as long as you modify your program correctly, this is not the
case. That is, if your program has a reasonable notion of "printing
to the screen and terminate" to answer whether the input is a halting
instance. You simply modify any location of your program that prints
to screen to check what you are printing, and if it is "yes" then you
instead cause the WillHalt function return 1 using whatever mechanism
available, and if it is "no" then you makes it return 0. Then the
modified program can be proved to have equivalent behaviour to yours,
except that while your program would output to screen, the modified
program return boolean.
Then your whole argument breaks down. I don't have to attack your
program directly, but instead attack the modified version of your
program. Assume your program really exists, then the modified version
must also exist, and the modified program is proved to behave exactly
the same as your program apart from the way it outputs. Since I can
show you that the no program would exhibit that behaviour, this leads
to a contradiction. So your program cannot exist either.
This is the whole strategy of the proof of the impossibility of
Halting problem: once you know that the halting problem of Turing
machines cannot be solved in Turing machines itself, you also know
that the halting problem for any Turing equivalent machine (or
"Turing-capable" machine, i.e., able to express the computation of a
Turing machine) cannot be solved using anything with no stronger power
than a Turing machine.
Regards,
Isaac.
- Next message: Mitch Harris: "Re: Disproof of the Halting Problem's Conclusion"
- Previous message: Alex Vinokur: "Re: Disproof of the Halting Problem's Conclusion"
- In reply to: Peter Olcott: "Re: Disproof of the Halting Problem's Conclusion"
- Next in thread: Peter Olcott: "Re: Disproof of the Halting Problem's Conclusion"
- Reply: Peter Olcott: "Re: Disproof of the Halting Problem's Conclusion"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|