Liste des Groupes | Revenir à c theory |
On 6/30/25 9:26 PM, olcott wrote:Recursive emulation is not a loop.On 6/30/2025 8:10 PM, Richard Damon wrote:Except that isn't what you said HHH does!On 6/30/25 1:00 PM, olcott wrote:>>>
One line of C source-code is a C statement.
HHH simulates six statements of DDD.
No it doesn't, as that line of C refers to HHH, and to process that line, you need to process ALL the lines in HHH.
>
Yes this is true.
What the F did you think that I meant by:
>
HHH simulates DDD that calls HHH
that simulates DDD that calls HHH
that simulates DDD that calls HHH
that simulates DDD that calls HHH
that simulates DDD that calls HHH
that simulates DDD that calls HHH...
YOu said HHH simulated DDD until it recognizes a non-halting pattern.
You have omitted this in your "loop"
It should be:It is more precisely accurate the way that you
HHH simulated DDD that calls HHH, until it recognizes a non-halting pattern,
Which results in it simulating HHH simulating DDD until it recognizes a non-halting pattern...
Which results in it simulating HHH simulating DDD until it recognizes a non-halting pattern...
Which results in it simulating HHH simulating DDD until it recognizes a non-halting pattern...
Which results in it simulating HHH simulating DDD until it recognizes a non-halting pattern...
The problem is when you include that we KNOW that, since the outer HHH *WILL* at some point abort (since you assume that will happen) that this simulated HHH will also do that, and thus make the DDD that called it halting.If you are going to call impossibly reaching its final halt state
Your problem is you didn't CORRECTLY simulate the HHH that DDD calls, as you ERRONEOUSLY assumed that it will not halt in order to claim that you have a non-halting pattern.When N x86 instructions of DDD are simulated
THe problem is whatever criteria is used to abort, is part of the code that is being analyized, and thus you need to take that into account when you try to prove that the pattern is non-halting.Repeat this to yourself 500 times so that you will
Your "logic" doesn't understand how programs work and are defined, because your "logic" comes out of your own ignorance of the field.--
>Then why doesn't it show the x86 instuctions executed?
>You are just showing you don't understand the basics of how computers and programs work.>
>>>Note, "C" doesn't define "instructions", but operations as defined by the abstract machine.>
>
The operations defined in DDD:
>
Fetch the value of DDD
Pass that as a parameter to HHH
Call the funciton HHH,
Perform the operations of function HHH
Return
>
At the machine language level HHH correctly
simulated four x86 instructions of DDD six times.
Nope, doesn't simulate the CALL instruction.
>
Yes it does.
Of the sequence points inside of the HHH that it called?
>As I said, that isn't a simulation of HHH, as that isn't what HHH doess, because it LIES about the fact that HHH, as you have defined it, *WILL* abort and return 0, and thus every DDD will halt.
What the F did you think that I meant by:
HHH simulates DDD that calls HHH
that simulates DDD that calls HHH
that simulates DDD that calls HHH
that simulates DDD that calls HHH
that simulates DDD that calls HHH
that simulates DDD that calls HHH...
>
>
All you are doing is proving that you don't understand what you are talkinga about, and just refuse to look at the facts, because you are just a pathological liar that has been brainwashed by yourself into unconditionaly believing your own lies.
Les messages affichés proviennent d'usenet.