Sujet : Re: Termination analyzer defined ---RICHARD IS WRONG !!!
De : polcott333 (at) *nospam* gmail.com (olcott)
Groupes : comp.theory sci.logicDate : 18. May 2024, 16:10:17
Autres entêtes
Organisation : A noiseless patient Spider
Message-ID : <v2agcp$2r74q$2@dont-email.me>
References : 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16
User-Agent : Mozilla Thunderbird
On 5/18/2024 3:52 AM, immibis wrote:
On 16/05/24 16:08, olcott wrote:
On 5/16/2024 4:59 AM, Mikko wrote:
It is easy to try a specifc program with a specific input and see
what happens,
>
*The prior answer from the "received view" has always been no one knows*
>
It has always been the case in the "received view" that because the
pathological input D was defined to contradict every value that its
termination analyzer H returns that both YES and NO are the wrong
answer from H.
You can run it and see.
If it halts, then the right answer to "does it halt?" is yes.
If it doesn't halt, then the right answer to "does it halt?" is no.
typedef int (*ptr)(); // ptr is pointer to int function
00 int H(ptr x, ptr y);
01 int D(ptr x)
02 {
03 int Halt_Status = H(x, x);
04 if (Halt_Status)
05 HERE: goto HERE;
06 return Halt_Status;
07 }
08
09 int main()
10 {
11 H(D,D);
12 return 0;
13 }
Explaining how this is incorrect requires the prerequisite knowledge
that no D correctly simulated by any H of every H/D pair specified by
the above template ever reaches its own line 06 and halts.
-- Copyright 2024 Olcott "Talent hits a target no one else can hit; Geniushits a target no one else can see." Arthur Schopenhauer