When the halting problem requires a halt deciderIf you honestly admit you are solving POO Problem, everything is fine.
to report on the behavior of a Turing machine
this is always a category error.
The corrected halting problem requires a Turing
machine decider to report in the behavior that
its finite string input specifies.
This analysis in done in the C programming language
so that it is 100% concrete without any key details
being abstracted away.
int DD()
{
int Halt_Status = HHH(DD);
if (Halt_Status)
HERE: goto HERE;
return Halt_Status;
}
(a) The key issue is that HHH(DD) does report on the
behavior that its input finite string specifies.
(b) Reporting on anything else is outside of the
scope of Turing Machine Computable functions.
*Detailed analysis shown below*--- Synchronet 3.21a-Linux NewsLink 1.2
After many very extensive discussions with LLM
systems there are two principles that prove that
I have correctly refuted the halting problem itself.
(1) Turing Machine based Computable functions
only transform input finite strings into some value
on the basis of a semantic of syntactic property
that this finite string specifies.
(2) the behavior that an input DD specifies to halt
decider HHH is the sequence of steps of DD
simulated by HHH according to the semantics of
the C programming language.
Computable functions are the basic objects of study
in computability theory. Informally, a function is
computable if there is an algorithm that computes
the value of the function for every value of its argument. https://en.wikipedia.org/wiki/Computable_function
DD() executed from main() calls HHH(DD) thus is
not one-and-the-same-thing as an argument to HHH.
On Wed, 2025-12-10 at 16:43 -0600, polcott wrote:
When the halting problem requires a halt decider
to report on the behavior of a Turing machine
this is always a category error.
The corrected halting problem requires a Turing
machine decider to report in the behavior that
its finite string input specifies.
If you honestly admit you are solving POO Problem, everything is fine.
On 12/10/2025 4:58 PM, wij wrote:
On Wed, 2025-12-10 at 16:43 -0600, polcott wrote:
When the halting problem requires a halt decider
to report on the behavior of a Turing machine
this is always a category error.
The corrected halting problem requires a Turing
machine decider to report in the behavior that
its finite string input specifies.
If you honestly admit you are solving POO Problem, everything is fine.
*It has take me 21 years to boil it down to this*It looks you play blind block my other replies again. https://sourceforge.net/projects/cscall/files/MisFiles/ghp.txt/download
When the halting problem requires a halt decider
to report on the behavior of a Turing machine this
is always a category error.
The corrected halting problem requires a Turing
machine decider to report in the behavior that
its finite string input specifies.
On Wed, 2025-12-10 at 17:03 -0600, polcott wrote:
On 12/10/2025 4:58 PM, wij wrote:
On Wed, 2025-12-10 at 16:43 -0600, polcott wrote:
When the halting problem requires a halt decider
to report on the behavior of a Turing machine
this is always a category error.
The corrected halting problem requires a Turing
machine decider to report in the behavior that
its finite string input specifies.
If you honestly admit you are solving POO Problem, everything is fine.
*It has take me 21 years to boil it down to this*
When the halting problem requires a halt decider
to report on the behavior of a Turing machine this
is always a category error.
The corrected halting problem requires a Turing
machine decider to report in the behavior that
its finite string input specifies.
It looks you play blind block my other replies again.
On Wed, 2025-12-10 at 17:03 -0600, polcott wrote:
On 12/10/2025 4:58 PM, wij wrote:
On Wed, 2025-12-10 at 16:43 -0600, polcott wrote:
When the halting problem requires a halt decider
to report on the behavior of a Turing machine
this is always a category error.
The corrected halting problem requires a Turing
machine decider to report in the behavior that
its finite string input specifies.
If you honestly admit you are solving POO Problem, everything is fine.
*It has take me 21 years to boil it down to this*
When the halting problem requires a halt decider
to report on the behavior of a Turing machine this
is always a category error.
The corrected halting problem requires a Turing
machine decider to report in the behavior that
its finite string input specifies.
It looks you play blind block my other replies again.
When the halting problem requires a halt decider
to report on the behavior of a Turing machine
this is always a category error.
The corrected halting problem requires a Turing
machine decider to report in the behavior that
its finite string input specifies.
This analysis in done in the C programming language
so that it is 100% concrete without any key details
being abstracted away.
int DD()
{
int Halt_Status = HHH(DD);
if (Halt_Status)
HERE: goto HERE;
return Halt_Status;
}
(a) The key issue is that HHH(DD) does report on the
behavior that its input finite string specifies.
(b) Reporting on anything else is outside of the
scope of Turing Machine Computable functions.
*Detailed analysis shown below*
After many very extensive discussions with LLM
systems there are two principles that prove that
I have correctly refuted the halting problem itself.
(1) Turing Machine based Computable functions
only transform input finite strings into some value
on the basis of a semantic of syntactic property
that this finite string specifies.
(2) the behavior that an input DD specifies to halt
decider HHH is the sequence of steps of DD
simulated by HHH according to the semantics of
the C programming language.
Computable functions are the basic objects of study
in computability theory. Informally, a function is
computable if there is an algorithm that computes
the value of the function for every value of its argument. https://en.wikipedia.org/wiki/Computable_function
DD() executed from main() calls HHH(DD) thus is
not one-and-the-same-thing as an argument to HHH.
On Wed, 2025-12-10 at 17:03 -0600, polcott wrote:
On 12/10/2025 4:58 PM, wij wrote:
On Wed, 2025-12-10 at 16:43 -0600, polcott wrote:
When the halting problem requires a halt decider
to report on the behavior of a Turing machine
this is always a category error.
The corrected halting problem requires a Turing
machine decider to report in the behavior that
its finite string input specifies.
If you honestly admit you are solving POO Problem, everything is fine.
*It has take me 21 years to boil it down to this*
When the halting problem requires a halt decider
to report on the behavior of a Turing machine this
is always a category error.
The corrected halting problem requires a Turing
machine decider to report in the behavior that
its finite string input specifies.
It looks you play blind block my other replies again. https://sourceforge.net/projects/cscall/files/MisFiles/ghp.txt/download
General Halting Problem, General Undecidable Rule.
-----------
Let MSet be the set of ANY deterministic computing device (including human). If a device H which computes the decision funcion ∀x∈MSet, H(x)=1 iff x() halts,
and a device D with contradictory property can be found to exist, then, contradiction occurres. Both H and D cannot exist in the same set.
void D() {
if(H(D)==1) for(;;){}; // Both H(D) returning 1 or non-1 contradict the
} // definition
int main() {
H(D); // H(D) cannot return whith the specified deciding function
}
Note: The assertion addresses about any decision funcion, whatever computing
the function is irrelevant. The main issue in application of this
assertion is proving the existence of D in MSet.
Note: As hinted by Rice's Theorem, if H is about deciding the behavioral
property of another element in MSet, high possibility is that such a
H cannot be an element of MSet. In logic, the answer of proposition
that both T/F does not fit is referred to as undecidable.
Undecidability may also be so interpreted in the infinite set like the set of natural number: Whenever you have a so-called maximum number n, then n+1 is automatically defined(generated) to exist in the set to defy the 'maximum' property... Traditional axiomatized system is limited, no powerful than Turing
Machine language (or procedural algorithm).
-----------
I have no problem of POO-HP.
When the halting problem requires a halt decider
to report on the behavior of a Turing machine
On 10/12/2025 22:43, polcott wrote:
When the halting problem requires a halt decider
to report on the behavior of a Turing machine
Can you provide a justification for that claim such as a reference to
(an) accepted definition(s) of "the halting problem" ?
Specifically that it is the "problem" that "requires" the report?
I expect that you discriminate the problem from the question but I'd
really like to see that the conventional distinction draws the line in
the same place you do.
| Sysop: | DaiTengu |
|---|---|
| Location: | Appleton, WI |
| Users: | 1,089 |
| Nodes: | 10 (0 / 10) |
| Uptime: | 155:34:44 |
| Calls: | 13,921 |
| Calls today: | 2 |
| Files: | 187,021 |
| D/L today: |
3,961 files (1,001M bytes) |
| Messages: | 2,457,202 |