Sujet : Re: Can D simulated by H terminate normally?
De : polcott333 (at) *nospam* gmail.com (olcott)
Groupes : comp.theoryDate : 02. May 2024, 05:55:21
Autres entêtes
Organisation : A noiseless patient Spider
Message-ID : <v0v2ra$3l29l$1@dont-email.me>
References : 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22
User-Agent : Mozilla Thunderbird
On 5/1/2024 9:30 PM, André G. Isaak wrote:
On 2024-05-01 19:44, olcott wrote:
On 5/1/2024 7:44 PM, André G. Isaak wrote:
On 2024-05-01 18:16, Richard Damon wrote:
On 5/1/24 11:26 AM, olcott wrote:
>
It is a termination analyzer thus is not required to be infallibly
correct on every possible input. It must get at least one input
correctly.
>
In other words, it is a TOY.
>
By your definition:
>
H(ptr m, ptr d) {
return 1;
}
>
is a correct termination analyzer, as it will get at least one input correctly.
>
Actually, by the metric which he gives, every single decider in existence is a correct termination analyzer, which tends to suggest this metric is relatively useless.
>
André
>
>
Try and back that up with reasoning anchored in quotes from my paper.
>
https://www.researchgate.net/publication/369971402_Termination_Analyzer_H_is_Not_Fooled_by_Pathological_Input_D
I was commenting on the line which you wrote here in this group, not a line from the above 'paper'.
That is even better those words were tested experts on the C
programming language. Four of the agreed and thought the question
was very clear and easy to answer. Two of these experts have
masters degrees in computer science.
*Even Richard just agreed to this*
Paul was the first one to agree.
On 6/14/2022 6:47 AM, Paul N wrote:
> Yes, it is clear to us humans watching it that the
> program is repeating itself. Thus we can appreciate
> that it will never reach the final "ret" - indeed,
> it won't even get to the infinite loop identified above.
Since the above paper talks about "termination analyzers" without offering any definition of what is meant by this term, I can only go by your comment in this group where you write that "a termination analyzer thus is not required to be infallibly correct on every possible input. It must get *at least one* input correctly." [emphasis mine].
I used to call it a {simulating halt decider} where the
term-of-the-art: decider overrode its conventionally meaning
anything that decides to mean anything that always decides
correctly all the time.
That means that any decider which correctly accepts *one* terminating program as terminating is a "termination analyzer" (unless, of course, you mean something entirely different by "termination analyzer". But this would require you to supply an actual definition.)
It correct accepts at least one and correctly reject at least one.
My system actually works on an infinite set of each.
It can do any simple:
(a) infinite loop
(b) infinite recursion
(c) recursive simulation
And every decider will accept at least *one* terminating program description, regardless of what it is that that decider was actually intended to decide. That follows from the simple fact that it is no more possible to construct a decider which gets every instance of the halting problem* wrong than it is to construct one that gets every instance right.
André
[*] Here talk about 'halting' as if it is the same thing as 'terminating'. Since you've switched from talking about halt deciders to 'termination analyzers', perhaps you think these mean different things. But that again would require you to actually define what you think this difference is. Otherwise we're left simply trying to guess the meanings of your terms, as usual.
Basically we have five people including Richard that disagree
with you on the point of the original post.
-- Copyright 2024 Olcott "Talent hits a target no one else can hit; Geniushits a target no one else can see." Arthur Schopenhauer