Re: D simulated by H never halts no matter what H does

Liste des GroupesRevenir à c theory 
Sujet : Re: D simulated by H never halts no matter what H does
De : richard (at) *nospam* damon-family.org (Richard Damon)
Groupes : comp.theory sci.logic
Date : 27. Apr 2024, 02:26:11
Autres entêtes
Organisation : i2pn2 (i2pn.org)
Message-ID : <v0hgn3$2a19s$7@i2pn2.org>
References : 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28
User-Agent : Mozilla Thunderbird
On 4/26/24 8:02 PM, olcott wrote:
On 4/26/2024 12:05 PM, olcott wrote:
On 4/26/2024 11:19 AM, Richard Damon wrote:
On 4/26/24 11:34 AM, olcott wrote:
On 4/26/2024 3:32 AM, Mikko wrote:
On 2024-04-25 14:15:20 +0000, olcott said:
01 int D(ptr x)  // ptr is pointer to int function
02 {
03   int Halt_Status = H(x, x);
04   if (Halt_Status)
05     HERE: goto HERE;
06   return Halt_Status;
07 }
08
09 void main()
10 {
11   D(D);
12 }
>
That H(D,D) must report on the behavior of its caller is the
one that is incorrect.
>
What H(D,D) must report is independet of what procedure (if any)
calls it.
>
>
Thus when H(D,D) correctly reports that its input D(D) cannot possibly
reach its own line 6 and halt no matter what H does then H can abort its
input and report that its input D(D) does not halt.
>
But since the program D(D) DOES reach its own line 6 when run, because H aborts its simulation and return 0 (since that is what you say this H will do), your statement is PROVEN TO BE A LIE, and you "logic" just a collection of contradictions.
>
>
D simulated by H cannot possibly reach its own line 06 thus when we do
not use the strawman deception to refer to a different D then we know
that D simulated by H never halts.
>
>
The fact that the D(D) executed in main does halt is none of H's
business because H is not allowed to report on the behavior of its
caller.
>
>
In other words, H doesn't need to report on the Behavior of the Program described by its input because it isn't actually a Halt Decider, because you are just a LIAR.
>
>
>
Anyone knowing the theory of computation knows that H is not allowed to
report on the behavior of its caller.
>
In computability theory and computational complexity theory, an
undecidable problem is a decision problem for which it is proved to be
impossible to construct an algorithm that always leads to a correct yes-
or-no answer. https://en.wikipedia.org/wiki/Undecidable_problem
>
The behavior of the simulated D(D) before H aborts its simulation is
different than the behavior of the executed D(D) after H has aborted
its simulation.
>
Every time that a simulated input would never stop running unless
aborted the simulating termination analyzer must abort this simulation
to prevent its own infinite execution.
>
H(D,D) is a case of this H1(D,D) is not a case of this even though
the only difference between H and H1 is that D calls H and D does
not call H1.
>
D simulated by H would never stop running unless aborted and cannot
possibly reach its own line 06 and halt no matter what H does.
>
Thus whenever we do not use the strawman deception to refer to a
different D we know that D simulated by H specifies a non-halting
sequence of configurations to H.
>
 *This might be a more succinct way of summing that up*
When you understand that D simulated by H cannot possibly reach past its own line 03 (thus cannot possibly halt) no matter what H does and
But since H does whatever H does, if H aborts and returns 0, the the direct execution of D, which is what actually matters, DOES get to that point.

 you understand that it is incorrect for H to report on the behavior of its caller: void main() { D(D); } then this necessitates
But it MUST report on the program described to it, which is a call to D(D), and it doesn't matter if that is what calls H.
So, your claim is just a STUPID LIE.
Yes, you can't ask "What is the behavior of the program that called you?"
But you CAN ask what is the behavior of M(d) even if M(d) happens to call you.
You are just proving you total lack of understand of the nature of the problem.

 H can abort its simulation of D and correctly report that D specifies a non-halting sequence of configurations.
 
Nope, it CAN'T correctly say that a program that will halt when run is none halting.
Your claiming it can just proves that you are just a STUPID LIAR.
You seem to believe it is correct to give wrong answer, but I suppose that should be expected from someone who doesn't understand the basic nature of truth and who has been shown to be a pathological liar.
You have probabably doomed to oblivian any piece of your ideas that might have some usefulness by the taint of your illogical stupidity that you have been spewing.

Date Sujet#  Auteur
10 Nov 24 o 

Haut de la page

Les messages affichés proviennent d'usenet.

NewsPortal