Deutsch   English   Français   Italiano  
<vvkh14$2m36t$7@dont-email.me>

View for Bookmarking (what is this?)
Look up another Usenet article

Path: ...!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!eternal-september.org!.POSTED!not-for-mail
From: "Fred. Zwarts" <F.Zwarts@HetNet.nl>
Newsgroups: comp.theory
Subject: Re: Incorrect requirements --- Computing the mapping from the input
 to HHH(DD)
Date: Fri, 9 May 2025 11:14:12 +0200
Organization: A noiseless patient Spider
Lines: 69
Message-ID: <vvkh14$2m36t$7@dont-email.me>
References: <vv97ft$3fg66$1@dont-email.me> <vvgq6o$1acph$1@dont-email.me>
 <vvgqgl$15i5e$27@dont-email.me> <vvgr22$1ag3a$2@dont-email.me>
 <vvgt36$1auqp$2@dont-email.me> <vvgtbe$1b0li$1@dont-email.me>
 <vvguot$1auqp$3@dont-email.me> <vvh0t2$1b939$1@dont-email.me>
 <vvhap5$1hp80$1@dont-email.me> <vvhf20$1ihs9$1@dont-email.me>
 <vvhfnd$1hvei$3@dont-email.me> <vvil99$1ugd5$1@dont-email.me>
 <vvinvp$1vglb$1@dont-email.me> <vviv75$222r6$1@dont-email.me>
 <vvj1fp$22a62$1@dont-email.me> <vvj2j6$23gk7$1@dont-email.me>
 <as9TP.251456$lZjd.93653@fx05.ams4> <87msbmeo3b.fsf@nosuchdomain.example.com>
 <vvjcge$27753$2@dont-email.me> <87a57mek8r.fsf@nosuchdomain.example.com>
 <vvjgh7$28g5i$4@dont-email.me> <87seled0zy.fsf@nosuchdomain.example.com>
 <vvjobj$28g5i$11@dont-email.me>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Injection-Date: Fri, 09 May 2025 11:14:13 +0200 (CEST)
Injection-Info: dont-email.me; posting-host="effaaa99691bef49d0e396f91c654de7";
	logging-data="2821341"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX1+nIlaCPtA+gOSZuwnBv9dO"
User-Agent: Mozilla Thunderbird
Cancel-Lock: sha1:wt7YV9qmWpEZlc3jQ+n4y27NNyY=
In-Reply-To: <vvjobj$28g5i$11@dont-email.me>
Content-Language: nl, en-GB
Bytes: 4381

Op 09.mei.2025 om 04:13 schreef olcott:
> On 5/8/2025 8:30 PM, Keith Thompson wrote:
>> olcott <polcott333@gmail.com> writes:
>>> On 5/8/2025 6:49 PM, Keith Thompson wrote:
>>>> olcott <polcott333@gmail.com> writes:
>>>> [...]
>>>>> void DDD()
>>>>> {
>>>>>     HHH(DDD);
>>>>>     return;
>>>>> }
>>>>>
>>>>> If you are a competent C programmer then you
>>>>> know that DDD correctly simulated by HHH cannot
>>>>> possibly each its own "return" instruction.
>>>> "cannot possibly each"?
>>>> I am a competent C programmer (and I don't believe you can make
>>>> the same claim).  I don't know what HHH is.  The name "HHH" tells
>>>> me nothing about what it's supposed to do.  Without knowing what
>>>> HHH is, I can't say much about your code (or is it pseudo-code?).
>>>>
>>>
>>> For the purpose of this discussion HHH is exactly
>>> what I said it is. It correctly simulates DDD.
>>
>> Does HHH correctly simulate DDD *and do nothing else*?
>>
>> Does HHH correctly simulate *every* function whose address is passed
>> to it?  Must the passed function be one that takes no arguments
>> and does not return a value?
>>
>> Can HHH just *call* the function whose address is passed to it?
>> If it's a correct simulation, there should be no difference between
>> calling the function and "correctly simulating" it.
>>
>> My knowledge of C tells me nothing about *how* HHH might simulate
>> DDD.
>>
> 
> HHH can only simulate a function that take no arguments
> and has no return value. HHH also simulates the entire
> chain of functions that this function calls. These can
> take arguments or not and have return values or not.
> 
> Thus HHH ends up simulating itself (and everything
> that HHH calls) simulating DDD in an infinite
> sequence of recursive emulation until OOM error.
> 
>>> We need not know anything else about HHH to
>>> know that DDD correctly simulated by HHH cannot
>>> possibly REACH its own "return" instruction.
>>
>> Assuming that HHH(DDD) "correctly simulates" DDD, and assuming it
>> does nothing else, your code would be equivalent to this:
>>
>>      void DDD(void) {
>>          DDD();
>>          return;
>>      }
>>
> 
> Exactly. None of these people on comp.theory could
> get that even after three years.
> 
Only if you forget that your proposed HHH aborts and returns.
The whole discussion is about that proposed HHH, not the hypothetical 
HHH that does not abort.
You try to get people to agree with you by using the same name for very 
different things.