Path: ...!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail From: Mikko Newsgroups: comp.theory Subject: Re: DDD correctly emulated by HHH is correctly rejected as non-halting. Date: Thu, 11 Jul 2024 09:25:09 +0300 Organization: - Lines: 37 Message-ID: References: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Injection-Date: Thu, 11 Jul 2024 08:25:09 +0200 (CEST) Injection-Info: dont-email.me; posting-host="d915db998623bee0999786efb2838ac1"; logging-data="2472054"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1/zXV4OCcMKRB2Zo8QmpJUn" User-Agent: Unison/2.2 Cancel-Lock: sha1:mZSuWX/dfZ6WhhO8BxvbRiJ/l2M= Bytes: 1821 On 2024-07-10 17:53:38 +0000, olcott said: > On 7/10/2024 12:45 PM, Fred. Zwarts wrote: >> Op 10.jul.2024 om 17:03 schreef olcott: >>> typedef void (*ptr)(); >>> int HHH(ptr P); >>> >>> void DDD() >>> { >>>    HHH(DDD); >>> } >>> >>> int main() >>> { >>>    HHH(DDD); >>> } >> >> Unneeded complexity. It is equivalent to: >> >>        int main() >>        { >>          return HHH(main); >>        } >> > > > Every time any HHH correctly emulates DDD it calls the > x86utm operating system to create a separate process > context with its own memory virtual registers and stack, > thus each recursively emulated DDD is a different instance. However, each of those instances has the same sequence of instructions that the x86 language specifies the same operational meaning. -- Mikko