On 2025-11-20, olcott <polcott333@gmail.com> wrote:
On 11/19/2025 10:42 PM, Kaz Kylheku wrote:
On 2025-11-20, olcott <polcott333@gmail.com> wrote:
On 11/19/2025 3:41 PM, Kaz Kylheku wrote:
On 2025-11-19, olcott <polcott333@gmail.com> wrote:that you dishonestly erased most of the context
The sound basis of this reasoning is the
semantics of the C programming language.
... and, note,
That's just the same pseudo-code snppet you've posted
hundreds of times.
The idea is that I will keep repeating this
until you pay attention
int DD()
{
int Halt_Status = HHH(DD);
if (Halt_Status)
HERE: goto HERE;
return Halt_Status;
}
int main()
{
HHH(DD);
}
I've given ths an incredible amount of attention.
HHH simulates DD that calls HHH(DD)
that simulates DD that calls HHH(DD)...
If HHH(DD) returns 0, it's this;
HHH simulates DD that calls HHH(DD)
- that simulates DD that calls HHH(DD)...
- that simulates DD that calls HHH(DD)...
- but only partially, returning 0.
- such that DD terminates.
- but only partially, returning 0.
- such that DD terminates.
Adding another level:
HHH simulates DD that calls HHH(DD)
- that simulates DD that calls HHH(DD)...
- that simulates DD that calls HHH(DD)...
- that simulates DD that calls HHH(DD)...
- that ...
- that ...
- that ...
I don't think that is the shell game. PO really /has/ an H
(it's trivial to do for this one case) that correctly determines
that P(P) *would* never stop running *unless* aborted.
- but only partially, returning 0.
- such that DD terminates.
- but only partially, returning 0.
- such that DD terminates.
- but only partially, returning 0.
- such that DD terminates.
Infinite simulation tower: finite DD's.
Since you don't grok this but I do, obviously the one who has
paid more attention is me.
| Sysop: | Amessyroom |
|---|---|
| Location: | Fayetteville, NC |
| Users: | 54 |
| Nodes: | 6 (1 / 5) |
| Uptime: | 20:59:53 |
| Calls: | 742 |
| Files: | 1,218 |
| D/L today: |
6 files (8,794K bytes) |
| Messages: | 185,811 |
| Posted today: | 1 |