On 2025-11-19, olcott <polcott333@gmail.com> wrote:
On 11/18/2025 7:01 PM, Kaz Kylheku wrote:
On 2025-11-18, olcott <polcott333@gmail.com> wrote:
On 11/18/2025 3:21 PM, Kaz Kylheku wrote:
On 2025-11-18, olcott <polcott333@gmail.com> wrote:
If you ask a decider to determine if my
sister's name is "Sally" and I don't tell
it who I am then the information contained
in the input is insufficient. This does not
in any way limit computation itself.
The problem is that UTM(D) can work out the fact that
D halts. Why is it that UTM knows that D's sister's
name is Sally, but H does not?
UTM(D) is answering a different question.
(a) It is not providing any answer at all.
Well, of course, by "UTM" we mean a /decider/ that purely simulates:
bool UTM(ptr P) {
sim S = sim_create(P);
sim_step_exhaustively(S);
return true;
}
All deciders applied to D are tasked with answering exactly the same
question.
Pretending that a different question was asked is nonproductive;
the answer will be interpreted to the original question.
All the information needed to answer is positively contained in D.
It is just too complex relative to H.
What The F does UTM decide when DD calls UTM(DD)?
That doesn't happen; DD calls HHH(DD).
A diagonal functon set against UTM, call it DDUTM,
cannot be decided by UTM(DDUTM).
That call simply does not return.
On 11/18/2025 8:53 PM, Kaz Kylheku wrote:
On 2025-11-19, olcott <polcott333@gmail.com> wrote:
On 11/18/2025 7:01 PM, Kaz Kylheku wrote:
On 2025-11-18, olcott <polcott333@gmail.com> wrote:
On 11/18/2025 3:21 PM, Kaz Kylheku wrote:
On 2025-11-18, olcott <polcott333@gmail.com> wrote:
If you ask a decider to determine if my
sister's name is "Sally" and I don't tell
it who I am then the information contained
in the input is insufficient. This does not
in any way limit computation itself.
The problem is that UTM(D) can work out the fact that
D halts. Why is it that UTM knows that D's sister's
name is Sally, but H does not?
UTM(D) is answering a different question.
(a) It is not providing any answer at all.
Well, of course, by "UTM" we mean a /decider/ that purely simulates:
bool UTM(ptr P) {
sim S = sim_create(P);
sim_step_exhaustively(S);
return true;
}
All deciders applied to D are tasked with answering exactly the same
question.
Pretending that a different question was asked is nonproductive;
the answer will be interpreted to the original question.
All the information needed to answer is positively contained in D.
It is just too complex relative to H.
What The F does UTM decide when DD calls UTM(DD)?
That doesn't happen; DD calls HHH(DD).
A diagonal functon set against UTM, call it DDUTM,
cannot be decided by UTM(DDUTM).
That call simply does not return.
Yes, and the other one does return proving the
whole point that I have been making for three
years that everyone (besides Ben) was too damned
dishonest to acknowledge has been true all along.
D simulated by H cannot possibly reach its own
simulated final halt state.
I am not going to talk about any non-nonsense of
resuming a simulation after we already have this
final answer.
We just proved that the input to H(D) specifies
non-halting. Anything beyond this is flogging a
dead horse.
news://news.eternal-september.org/20251104183329.967@kylheku.com
On 11/4/2025 8:43 PM, Kaz Kylheku wrote:
On 2025-11-05, olcott <polcott333@gmail.com> wrote:
The whole point is that D simulated by H
cannot possbly reach its own simulated
"return" statement no matter what H does.
Yes; this doesn't happen while H is running.
So while H does /something/, no matter what H does,
that D simulation won't reach the return statement.
Am 06.11.2025 um 21:48 schrieb olcott:
D simulated by H cannot possibly reach its ownWhat you do is like thinking in circles before falling asleep.
simulated final halt state.
I am not going to talk about any non-nonsense of
resuming a simulation after we already have this
final answer.
We just proved that the input to H(D) specifies
non-halting. Anything beyond this is flogging a
dead horse.
news://news.eternal-september.org/20251104183329.967@kylheku.com
On 11/4/2025 8:43 PM, Kaz Kylheku wrote:
On 2025-11-05, olcott <polcott333@gmail.com> wrote:
The whole point is that D simulated by H
cannot possbly reach its own simulated
"return" statement no matter what H does.
Yes; this doesn't happen while H is running.
So while H does /something/, no matter what H does,
that D simulation won't reach the return statement.
It never ends. You're gonna die with that for sure sooner or later.
On 11/25/2025 9:20 AM, Bonita Montero wrote:It don't matters if you're correct. There's no benefit in discussing
What you do is like thinking in circles before falling asleep.
It never ends. You're gonna die with that for sure sooner or later.
I now have four different LLM AI models that prove
that I am correct on the basis that they derive the
proof steps that prove that I am correct.
Even Kimi that was dead set against me now fully
understands my new formal foundation for correct
reasoning.
On 11/25/2025 9:20 AM, Bonita Montero wrote:
Am 06.11.2025 um 21:48 schrieb olcott:
D simulated by H cannot possibly reach its ownWhat you do is like thinking in circles before falling asleep.
simulated final halt state.
I am not going to talk about any non-nonsense of
resuming a simulation after we already have this
final answer.
We just proved that the input to H(D) specifies
non-halting. Anything beyond this is flogging a
dead horse.
news://news.eternal-september.org/20251104183329.967@kylheku.com
On 11/4/2025 8:43 PM, Kaz Kylheku wrote:
On 2025-11-05, olcott <polcott333@gmail.com> wrote:
The whole point is that D simulated by H
cannot possbly reach its own simulated
"return" statement no matter what H does.
Yes; this doesn't happen while H is running.
So while H does /something/, no matter what H does,
that D simulation won't reach the return statement.
It never ends. You're gonna die with that for sure sooner or later.
I now have four different LLM AI models that prove
that I am correct on the basis that they derive the
proof steps that prove that I am correct.
Even Kimi that was dead set against me now fully
understands my new formal foundation for correct
reasoning.
On 2025-11-06, olcott <polcott333@gmail.com> wrote:
D simulated by H cannot possibly reach its own
simulated final halt state.
It has been shown /wth code/ that D simulated by H reaches its return, possible even in your horribly incorrect program that fails to conform
to the requirements for exploring the halting problem.
On 2025-11-05, olcott <polcott333@gmail.com> wrote:
The whole point is that D simulated by H
cannot possbly reach its own simulated
"return" statement no matter what H does.
Yes; this doesn't happen while H is running.
So while H does /something/, no matter what H does,
that D simulation won't reach the return statement.
On 2025-11-25, olcott <polcott333@gmail.com> wrote:
On 11/25/2025 11:42 AM, Kaz Kylheku wrote:
On 2025-11-06, olcott <polcott333@gmail.com> wrote:
D simulated by H cannot possibly reach its own
simulated final halt state.
It has been shown /wth code/ that D simulated by H reaches its return,
Liar, Liar Pants on Fire !!!
I made the code public; another person was able to build and get the
same results.
On 2025-11-05, olcott <polcott333@gmail.com> wrote:
The whole point is that D simulated by H
cannot possbly reach its own simulated
"return" statement no matter what H does.
Yes; this doesn't happen while H is running.
So while H does /something/, no matter what H does,
that D simulation won't reach the return statement.
On 2025-11-05, olcott <polcott333@gmail.com> wrote:
The whole point is that D simulated by H
cannot possbly reach its own simulated
"return" statement no matter what H does.
Yes; this doesn't happen while H is running.
So while H does /something/, no matter what H does,
that D simulation won't reach the return statement.
On 2025-11-05, olcott <polcott333@gmail.com> wrote:
The whole point is that D simulated by H
cannot possbly reach its own simulated
"return" statement no matter what H does.
Yes; this doesn't happen while H is running.
So while H does /something/, no matter what H does,
that D simulation won't reach the return statement.
On 2025-11-05, olcott <polcott333@gmail.com> wrote:
The whole point is that D simulated by H
cannot possbly reach its own simulated
"return" statement no matter what H does.
Yes; this doesn't happen while H is running.
So while H does /something/, no matter what H does,
that D simulation won't reach the return statement.
On 2025-11-05, olcott <polcott333@gmail.com> wrote:
The whole point is that D simulated by H
cannot possbly reach its own simulated
"return" statement no matter what H does.
Yes; this doesn't happen while H is running.
So while H does /something/, no matter what H does,
that D simulation won't reach the return statement.
| Sysop: | DaiTengu |
|---|---|
| Location: | Appleton, WI |
| Users: | 1,089 |
| Nodes: | 10 (0 / 10) |
| Uptime: | 153:54:15 |
| Calls: | 13,921 |
| Calls today: | 2 |
| Files: | 187,021 |
| D/L today: |
3,760 files (944M bytes) |
| Messages: | 2,457,163 |