Path: ...!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail
From: Mikko <mikko.levanto@iki.fi>
Newsgroups: comp.theory
Subject: Re: Sequence of sequence, selection and iteration matters -- Professor Hehner
Date: Mon, 15 Jul 2024 10:25:14 +0300
Organization: -
Lines: 72
Message-ID: <v72isq$jqao$1@dont-email.me>
References: <v6e7va$c4sv$1@dont-email.me> <v6g444$pdc2$1@dont-email.me> <v6go4d$sg7f$1@dont-email.me> <v6ikv5$19h6q$1@dont-email.me> <v6jguf$1ctoi$5@dont-email.me> <v6ji1d$1dpoc$1@dont-email.me> <v6jig0$1ctoi$11@dont-email.me> <v6jkib$1e3jq$1@dont-email.me> <v6jpe5$1eul0$1@dont-email.me> <v6jpqo$1e3jq$2@dont-email.me> <v6jqfg$1eul0$2@dont-email.me> <v6k6md$1h3a7$1@dont-email.me> <v6k9ef$1hicb$1@dont-email.me> <v6lc9v$1q8jn$1@dont-email.me> <v6lva1$1tj30$1@dont-email.me> <v6m4nk$1uean$1@dont-email.me> <v6m53s$1ugv5$1@dont-email.me> <v6m6i9$1uean$3@dont-email.me> <v6m78d$1uq86$1@dont-email.me> <v6o17i$2bu9u$1@dont-email.me> <v6ordc$2fuva$9@dont-email.me> <v6qrq1$2v5cr$1@dont-email.me> <v6rbf7$30qtt$10@dont-email.me> <v6tcth$3gm3g$1@dont-email.me> <v6tss2$3imib$10@dont-email.me> <v702nt$2kut$1@dont-email.me> <v70pa9$61d8$11@dont-email.me>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Injection-Date: Mon, 15 Jul 2024 09:25:15 +0200 (CEST)
Injection-Info: dont-email.me; posting-host="eb7bc3c094cc39ab136406329ffd9913";
	logging-data="649560"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX1+0PTweJMGu9c5R5KKWKeab"
User-Agent: Unison/2.2
Cancel-Lock: sha1:+S1N55RW0d8TdtNXvpqxQQ4+Pm8=
Bytes: 3780

On 2024-07-14 15:02:33 +0000, olcott said:

> On 7/14/2024 3:37 AM, Mikko wrote:
>> On 2024-07-13 12:44:50 +0000, olcott said:
>> 
>>> On 7/13/2024 3:12 AM, Mikko wrote:
>>>> On 2024-07-12 13:35:34 +0000, olcott said:
>>>> 
>>>>> On 7/12/2024 4:08 AM, Mikko wrote:
>>>>>> 
>>>>>> In that situation you should use the symobls HHH₁, HHH₂, HHH₃, ...
>>>>>> so that you can use HHHᵢ when you say aothing about every one of them.
>>>>>> And the one more symbols for the one that runs forever.
>>>>> 
>>>>> I did not want to say it as verbosely as that, yet your suggestion
>>>>> would be clearer.
>>>> 
>>>> For honest purposes clearer would be better. But understand that
>>>> different purposes mean different priorities.
>>> 
>>> I made it clearer using your suggestions.
>> 
>> Where is that clearer presentations?
>> 
>>>>>> And they should
>>>>>> not be defined to run DDD but whatever input is given.
>>>>> 
>>>>> I certainly can't do that. People here use every excuse
>>>>> they can to change the subject and then stay on this
>>>>> changed subject and never get back to the point.
>>>> 
>>>> Of course you can and should. No reason to expect them to protest less
>>>> if you make more errors.
>>>> 
>>> 
>>> My current paper examines these three inputs at the C
>>> source-code level in the simplest one first order.
>>> 
>>> void Infinite_Loop()
>>> {
>>>    HERE: goto HERE;
>>> }
>>> 
>>> void Infinite_Recursion()
>>> {
>>>    Infinite_Recursion();
>>> }
>>> 
>>> void DDD()
>>> {
>>>    HHH(DDD);
>>> }
>>> 
>>> It then examines the simplest possible pathological input
>>> above at the assembly language level.
>> 
>> Going to the assembly langage level does not add anything if the code
>> of HHH is not shown.
> 
> Going to the assembly language level provides a directed
> graph of control flow.

So does the C level.

> It also shows the final state that
> is not shown at the C level.

How is that different from the final state that is shown at the C level?

-- 
Mikko