Path: news.eternal-september.org!eternal-september.org!.POSTED!not-for-mail
From: Mikko <mikko.levanto@iki.fi>
Newsgroups: comp.theory
Subject: Re: How could HHH report on the behavior of its caller?
Date: Thu, 15 May 2025 10:37:47 +0300
Organization: -
Lines: 24
Message-ID: <10045kb$314dt$1@dont-email.me>
References: <1003g30$2pfv4$1@dont-email.me>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Injection-Date: Thu, 15 May 2025 09:37:47 +0200 (CEST)
Injection-Info: dont-email.me; posting-host="1d3ea60c43909c97d925f5b2a4bb28e2";
	logging-data="3183037"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX19OuwfHF7AtyrT1OrcsI8zN"
User-Agent: Unison/2.2
Cancel-Lock: sha1:hdTVVy3P8rwcdD0o44UgeKLaCGQ=

On 2025-05-15 01:30:08 +0000, olcott said:

> void DDD()
> {
>    HHH(DDD);
>    return;
> }
> 
> int main()
> {
>    DDD();
> }
> 
> If HHH cannot report on the behavior of its caller
> because this is a ridiculous requirement then how
> can HHH report on the direct execution of DDD()
> (AKA its caller).

Your HHH can use all information that Flibble's decider can. Flibble's
decider can determine and report that DDD halts.

-- 
Mikko