Re: No one can correctly refute that simulating abort decider A(D,D) is correct

On 3/28/2024 9:22 PM, Richard Damon wrote:

On 3/28/24 10:01 PM, olcott wrote:

<snip>

Right, but as you have admitted, the behavior of that machine code CHANGES depending on what is at the location of H.
>

>
The behavior of D simulated by any H that can possibly exist
remains the same.

 Nope.
 The behavior of D CHANGES based on the H it attaches to.
 

The behavior of D simulated by any H that can possibly exist
remains the same.
The behavior of directly executed D(D) is not the behavior of D simulated by any H.

You are just PROVING that you are LYING about H.
 

No I am proving that your ADD is worse than you thought.
<snip>

IT IS AN ABORT DECIDER THAT GIVES NO ANSWER IT ONLY ABORTS
IT IS AN ABORT DECIDER THAT GIVES NO ANSWER IT ONLY ABORT

Then why does D use the answer?
 I guess you are just admitting that your setup is incoherent.
 

01 void D(ptr x) // ptr is pointer to void function
02 {
03   H(x, x);
04   return;
05 }
06
07 void main()
08 {
09   H(D,D);
10 }

And ALL Deciders give an answer.
 

If you need to then pretend that H(D,D) returns 1 for abort
and 0 for not aborted. Since this value is never used it
is irrelevant.

Maybe in your case, there is only one answer, I aborted.
 But then, the mapping it is deciding on must be a trivial mapping, so H might as well return.
 

It is not trivial, where the Hell did you get that?
It is the same H that we always had with the return
values swapped and ignored.
--
Copyright 2024 Olcott "Talent hits a target no one else can hit; Genius
hits a target no one else can see." Arthur Schopenhauer