On 12/30/21 10:58 AM, olcott wrote:H and embedded_H are able to give a different halt status determinations
On 12/30/2021 9:48 AM, Richard Damon wrote:
We don't care if embedded_H is 'Correct', we care that it give the
same answer as H.
If it is correct and gives a different answer than H then it remains
correct even if it gives a different answer than H.
But since it IS a copy of H, then if it gives a different answer than
'H' does, it shows that H fails to be a Computation, and thus Can't be a Decider, and thus can't be a Halt Decider.
On 2021-12-30 09:54, olcott wrote:
On 12/30/2021 10:11 AM, Richard Damon wrote:
On 12/30/21 10:58 AM, olcott wrote:H and embedded_H are able to give a different halt status
On 12/30/2021 9:48 AM, Richard Damon wrote:
We don't care if embedded_H is 'Correct', we care that it give the
same answer as H.
If it is correct and gives a different answer than H then it remains
correct even if it gives a different answer than H.
But since it IS a copy of H, then if it gives a different answer than
'H' does, it shows that H fails to be a Computation, and thus Can't
be a Decider, and thus can't be a Halt Decider.
determinations on the basis that embedded_H had its copy of H
corrupted by the appended infinite loop.
This means that a finite string comparison performed by H will
determine that embedded_H is not identical to H.
And which two strings are being compared here? H hasn't been provided a string describing itself nor a string describing embedded_H as part of
its input. All it has is a string describing Ĥ. What does it compare
this string to?
André
When embedded_H is about to simulate embedded_H with identical inputs
it terminates this simulation as matching the infinitely nested
simulation infinite behavior pattern.
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 379 |
Nodes: | 16 (2 / 14) |
Uptime: | 66:44:06 |
Calls: | 8,084 |
Calls today: | 2 |
Files: | 13,068 |
Messages: | 5,849,424 |