Liste des Groupes | Revenir à theory |
On 10/8/2024 7:49 AM, Andy Walker wrote:It isn't a "false assumption"... after a short break.Thanks for that part.
>
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.
>
Peter -- you surely have better things to do. No-one sensibleMost people that "try to help" do so only within the
is reading the repetitive stuff. Decades, and myriads of articles, ago
people here tried to help you knock your points into shape, but anything
sensible is swamped by the insults. Free advice, worth roughly what you
are paying for it: step back, and summarise [from scratch, not using HHH
and DDD (etc) without explanation] (a) what it is you think you are trying
to prove and (b) what progress you claim to have made. No more than one
side of paper. Assume that people who don't actively insult you are, in
fact, trying to help.
>
foundational false assumption that I must be incorrect.
The DDD / HHH model is the simplest essence of my key points.And your model of DDD and HHH is based on an incorrect definition of a Program, as you don't consider DDD to include the HHH that it calls.
It only requires knowledge of software engineering thus
requires no knowledge of computer science.
This is the foundational axiom of my proof:But it must be of the full program, which yours isn't.
*Terminating is a property of finite string machine descriptions*
When I make key clarifications as I have made below those onlyExcept that it doesn't detect a correct non-terminating behavior pattern, as that pattern exists in a terminating program, namely this DDD
glancing at what I say never notice these key clarifications.
*Simulating Termination Analyzer HHH(DDD) rejects input DDD*
HHH is an emulating termination analyzer that takes the machine
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 isn't a corrrect pattern, as since HHH *DOES* abort its emulation and return, so does DDD.
void DDD()Right, and since HHH(DDD) represents an actual call to HHH with the parameter of DDD, and since this actual HHH will return 0 for that parameter, the ONLY correct understanding of that call is that it returns 0.
{
HHH(DDD);
return;
}
*Terminating is a property of finite string machine descriptions*
One cannot simply ignore the actual behavior specified by the
finite string such that
DDD emulated by each corresponding HHH that can possiblyNo, again you are repeating you same idiotic mistake.
exist never returns.
Thus each of these HHH emulators that does return 0 correctlyNope, since the actual DDD will return, the only correct answer for HHH to return would be 1
reports the above non-terminating behavior.
https://github.com/plolcott/x86utm x86utm operating systemAnd is wrong, and the fact you repeat that claim after being shown this fact show that
Every executed HHH that returns 0 correctly reports that
no DDD emulated by its corresponding HHH ever returns.
Les messages affichés proviennent d'usenet.