Liste des Groupes | Revenir à c theory |
On 5/6/2025 6:00 PM, Richard Damon wrote:On 5/6/25 1:54 PM, olcott wrote:On 5/6/2025 6:06 AM, Richard Damon wrote:On 5/5/25 10:29 PM, olcott wrote:On 5/5/2025 8:06 PM, Richard Damon wrote:On 5/5/25 11:51 AM, olcott wrote:
Can't be, as the input needs to be about a program, which must, by>When HHH computes the mapping from *its input* to the behavior ofAnd *ITS INPUT*, for the HHH that answers 0, is the representation
DD emulated by HHH this includes HHH emulating itself emulating
DD. This matches the infinite recursion behavior pattern.
>
of a program
Not at all. This has always been stupidly wrong.
The input is actually a 100% perfectly precise sequence of steps.
With pathological self-reference some of these steps are inside the
termination analyzer.
>
the definition of a program, include all its algorithm.
Yes, there are steps that also occur in the termination analyzer, but
they have been effectively copied into the program the input
describes.
A correct simulation is one that produces the same behaviour as theRight, but a correct simulation of D does halt,What you forget is that the input program INCLUDES as its definiton,*would never stop running unless aborted*
all of the code it uses, and thus the call to the decider it is built
on includes that code into the decider, and that is a FIXED and
DETERMINDED version of the decider, the one that THIS version of the
input is designed to make wrong.
This doesn't change when you hypothosize a different decider looking
at THIS input.
>
Refers to a hypothetical HHH/DD pair of the same HHH that DD calls
except that this hypothetical HHH never aborts.
>
How the Hell is breaking the rules specified by the x86 languageThe rule that you may not abort? The rule that you may not simulate
possibly correct?
Les messages affichés proviennent d'usenet.