On 23/10/2025 20:53, Chris M. Thomasson wrote:
Olcott cherry picks a hyper simple program and says see, I can tell if
it halts or not! I am an genius. Ect... He can detect a non-
terminating condition! God be praised indeed.
If HHH(DD) returns non-zero it goes into an infinite GOTO loop. We can
say this is non-halting. If HHH(DD) returns zero, DD halts.
That is indeed the spec. for C function DD. It seems that the rest of
your post is some kind of attempt to verify that function DD is meeting
its spec; the sort of thing a developer might do who was schooled in test-driven development methodologies.
The question PO asks, is not about function DD's specification or its correctness - it's something like "What value should *HHH* return, given some "specification" PO has provided for HHH".
Mike.
On 10/23/2025 8:27 PM, Mike Terry wrote:
On 23/10/2025 20:53, Chris M. Thomasson wrote:
Olcott cherry picks a hyper simple program and says see, I can tell
if it halts or not! I am an genius. Ect... He can detect a non-
terminating condition! God be praised indeed.
If HHH(DD) returns non-zero it goes into an infinite GOTO loop. We
can say this is non-halting. If HHH(DD) returns zero, DD halts.
That is indeed the spec. for C function DD. It seems that the rest of
your post is some kind of attempt to verify that function DD is
meeting its spec; the sort of thing a developer might do who was
schooled in test-driven development methodologies.
The question PO asks, is not about function DD's specification or its
correctness - it's something like "What value should *HHH* return,
given some "specification" PO has provided for HHH".
Mike.
Dishonest people will ignore this spec and on the basis
of not paying attention denigrate my work such that this
is an act of defamation of character.
<analysis mode="simulation" rules="strict">
- You must simulate the input **exactly as written**,
step by step, without any external reasoning,
assumptions, or guesses.
- **Do not analyze, infer, or speculate**; only describe
what the simulation observes in execution.
- Report only the behavior that occurs in the simulation.
- Always follow the priority rules exactly:
1. (a) Detect non-terminating behavior → abort
simulation and return 0.
2. (b) Return statement reached → return 1.
3. (c) Neither (a) nor (b) → return -1.
- Do not include any commentary about halting
problem, contradictions, or theoretical reasoning.
- All output must be in terms of simulation observations only.
</analysis>
<Input>
Simulating Termination Analyzer HHH correctly simulates its input until:
(a) Detects a non-terminating behavior pattern:
abort simulation and return 0.
(b) Simulated input reaches its simulated "return" statement:
return 1.
(c) Neither (a) nor (b) is met return -1
typedef int (*ptr)();
int HHH(ptr P);
int DD()
{
int Halt_Status = HHH(DD);
if (Halt_Status)
HERE: goto HERE;
return Halt_Status;
}
int main()
{
HHH(DD);
}
What value should HHH(DD) correctly return?
</Input>
On 10/23/25 6:46 PM, olcott wrote:
On 10/23/2025 8:27 PM, Mike Terry wrote:
On 23/10/2025 20:53, Chris M. Thomasson wrote:
Olcott cherry picks a hyper simple program and says see, I can tell
if it halts or not! I am an genius. Ect... He can detect a non-
terminating condition! God be praised indeed.
If HHH(DD) returns non-zero it goes into an infinite GOTO loop. We
can say this is non-halting. If HHH(DD) returns zero, DD halts.
That is indeed the spec. for C function DD. It seems that the rest
of your post is some kind of attempt to verify that function DD is
meeting its spec; the sort of thing a developer might do who was
schooled in test-driven development methodologies.
The question PO asks, is not about function DD's specification or its
correctness - it's something like "What value should *HHH* return,
given some "specification" PO has provided for HHH".
Mike.
Dishonest people will ignore this spec and on the basis
of not paying attention denigrate my work such that this
is an act of defamation of character.
<analysis mode="simulation" rules="strict">
- You must simulate the input **exactly as written**,
step by step, without any external reasoning,
assumptions, or guesses.
- **Do not analyze, infer, or speculate**; only describe
what the simulation observes in execution.
- Report only the behavior that occurs in the simulation.
- Always follow the priority rules exactly:
1. (a) Detect non-terminating behavior → abort
simulation and return 0.
2. (b) Return statement reached → return 1.
3. (c) Neither (a) nor (b) → return -1.
- Do not include any commentary about halting
problem, contradictions, or theoretical reasoning.
- All output must be in terms of simulation observations only.
</analysis>
<Input>
Simulating Termination Analyzer HHH correctly simulates its input until:
(a) Detects a non-terminating behavior pattern:
abort simulation and return 0.
(b) Simulated input reaches its simulated "return" statement:
return 1.
(c) Neither (a) nor (b) is met return -1
typedef int (*ptr)();
int HHH(ptr P);
int DD()
{
int Halt_Status = HHH(DD);
if (Halt_Status)
HERE: goto HERE;
return Halt_Status;
}
int main()
{
HHH(DD);
}
What value should HHH(DD) correctly return?
</Input>
u keep giving an algorithm, but it's not the one anyone wants
| Sysop: | DaiTengu |
|---|---|
| Location: | Appleton, WI |
| Users: | 1,076 |
| Nodes: | 10 (1 / 9) |
| Uptime: | 28:56:37 |
| Calls: | 13,804 |
| Calls today: | 1 |
| Files: | 186,990 |
| D/L today: |
300 files (66,892K bytes) |
| Messages: | 2,441,602 |