Sujet : Re: Analysis of Flibble’s Latest: Detecting vs. Simulating Infinite Recursion ZFC
De : mikko.levanto (at) *nospam* iki.fi (Mikko)
Groupes : comp.theoryDate : 26. May 2025, 10:43:27
Autres entêtes
Organisation : -
Message-ID : <1011d3v$1uk9j$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 23 24 25 26 27 28 29 30
User-Agent : Unison/2.2
On 2025-05-25 15:55:42 +0000, olcott said:
On 5/25/2025 5:19 AM, Richard Heathfield wrote:
On 24/05/2025 17:13, olcott wrote:
No HHH can report on the behavior of its caller
From Halt7.c:
void DDD()
{
HHH(DDD);
return;
}
Since (as you say) no HHH can report on the behaviour of its caller, and since (as your code shows) DDD is HHH's caller, we deduce that HHH cannot report on DDD.
So HHH is not (according to you) a halt analyser for DDD.
I'm not sure you've left anything to discuss, have you?
HHH(DDD) does correctly reject
*ITS INPUT THUS NOT ITS CALLER*
as non-halting.
If the caller is DDD then the input specifies a halting behaviour because
DDD calls HHH with an input that specifies a halting behavour. But HHH
cannot correctly reject a halting input as non-halting.
The requirements of a halting decider cannot be met if the decider reports
differently dependig on who calls it. Consequently, HHH is required to
return true also when the following FFF calls it:
void FFF(void) {
HHH(DDD);
return;
}
-- Mikko