Liste des Groupes | Revenir à theory |
void DDD()BUt ONLY the DDD that calls the HHH that ACTUALLY correct simulates it input, and thus never aborts.
{
HHH(DDD);
return;
}
int main()
{
HHH(DDD);
}
Understanding that DDD correctly simulated by HHH cannot
possibly reach its own "return" instruction is a mandatory
prerequisite to further discussion.
I can't imagine that anyone having sufficient understandingBut ONLY for the HHH that ACTUALLY correctly simulates its input, and thus does not abort it.
of C would not agree that DDD correctly simulated by HHH
cannot possibly reach its own "return" instruction. Several
C experts already agreed to this two of them having masters
in computer science: MSCS.
People are either disagreeing for trollish pleasure or haveNo, just pointing out that you are then trying to CHANGE you HHH to break your own definition of what HHH is.
woefully insufficient expertise in the C programming language.
*Either one of these is a deal killer*
Once they understand this we need to add one more pointRight, they compute the answer of what the input actually maps to.
that the "return" instruction of DDD is its halt state.
=== *Here is the last actual sticking point*
Computable functions are the formalized analogue of the intuitive
notion of algorithms, in the sense that a function is computable
if there exists an algorithm that can do the job of the function, i.e.
given an input of the function domain it can return the corresponding
output. https://en.wikipedia.org/wiki/Computable_function
A halt decider computes the mapping from an input finite string
to the behavior that this finite string specifies. No halt decider
ever reports on the actual behavior of the computation that itself
is contained within. This has been a very persistent false assumption.
For the three years that my work has been extensively reviewedBecause you insist that an INCORECT (because it is partial) simulation of the input defines what the program does
this has been the most difficult point for people to understand.
Everyone remains convinced that HHH must report on the behaviorBecause that *IS* what its input ask it.
of the computation that itself is contained within and not the
behavior that its finite string input specifies.
Simulating Termination Analyzer H is Not Fooled by Pathological Input DBut the input DDD includes the HHH that it calls, or it isn't a full description of the program DDD. (As you say, you can't ask about "the simulator deciding you" only about a specific decider, which might be the one you are given to).
https://www.researchgate.net/publication/369971402_Simulating_Termination_Analyzer_H_is_Not_Fooled_by_Pathological_Input_D
Les messages affichés proviennent d'usenet.