Liste des Groupes | Revenir à theory |
On 10/9/2024 5:08 AM, Mikko wrote:Thus additting that each of those DDD are different, and that HHH must look at the exact DDD that calls it, which means that the HHH(DDD) that it sees being called will do what it does.On 2024-10-09 03:47:10 +0000, olcott said:An HHH/DDD pair such that DDD calls its own emulator.
>On 10/8/2024 7:49 AM, Andy Walker wrote:>
> Richard -- no-one sane carries on an extended discussion with
> someone they [claim to] consider a "stupid liar". So which are you?
> Not sane? Or stupid enough to try to score points off someone who is
> incapable of conceding them? Or lying when you describe Peter? You
> must surely have better things to do. Meanwhile, you surely noticed
> that Peter is running rings around you.
>
I am incapable of conceding this self-evident truth:
>
DDD emulated by each corresponding HHH that can possibly
exist never returns
That is not self-evident or even meaningful without a definition of
"each corresponding HHH".
>
HHH is an emulating termination analyzer that takes the machineOr a false pattern that you have put into the list.
address of DDD as input then emulates the x86 machine language
of DDD until a non-terminating behavior pattern is recognized.
HHH recognizes this pattern when HHH emulates itself emulating DDDWhich is the false pattern.
void DDD()
{
HHH(DDD);
return;
}
One cannot simply ignore the actual behavior specified by theRight, and that is that HHH(DDD) returns 0, and thus this string must represent a halting decider.
finite string x86 machine language of DDD such that
DDD emulated by each corresponding HHH that can possiblyExecpt that it does, proving you are just an idiotic liar.
exist never returns
thus each of the directly executed HHH emulators that doesWhich is a lie, since we showed that the above was NOT non-terminationg behavior, but the product of a liar that doesn't know what he is talking about.
return 0 correctly reports the above non-terminating behavior.
https://github.com/plolcott/x86utm x86utm operating systemYou are just showing that
Every executed HHH that returns 0 correctly reports that
DDD emulated by its corresponding HHH never returns.
Les messages affichés proviennent d'usenet.