Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.theory > #135170 > unrolled thread
| Started by | olcott <polcott333@gmail.com> |
|---|---|
| First post | 2025-11-06 14:48 -0600 |
| Last post | 2025-11-26 00:45 +0000 |
| Articles | 20 on this page of 637 — 21 participants |
Back to article view | Back to comp.theory
D simulated by H cannot possibly reach its own simulated final halt state olcott <polcott333@gmail.com> - 2025-11-06 14:48 -0600
Re: D simulated by H cannot possibly reach its own simulated final halt state dbush <dbush.mobile@gmail.com> - 2025-11-06 15:55 -0500
Re: D simulated by H cannot possibly reach its own simulated final halt state Kaz Kylheku <643-408-1753@kylheku.com> - 2025-11-06 21:10 +0000
Re: D simulated by H cannot possibly reach its own simulated final halt state olcott <polcott333@gmail.com> - 2025-11-06 15:32 -0600
Re: D simulated by H cannot possibly reach its own simulated final halt state joes <noreply@example.org> - 2025-11-06 22:07 +0000
Re: D simulated by H cannot possibly reach its own simulated final halt state olcott <polcott333@gmail.com> - 2025-11-06 16:16 -0600
Re: D simulated by H cannot possibly reach its own simulated final halt state dbush <dbush.mobile@gmail.com> - 2025-11-06 17:26 -0500
Re: D simulated by H cannot possibly reach its own simulated final halt state olcott <polcott333@gmail.com> - 2025-11-06 16:32 -0600
Re: D simulated by H cannot possibly reach its own simulated final halt state dbush <dbush.mobile@gmail.com> - 2025-11-06 17:35 -0500
Re: D simulated by H cannot possibly reach its own simulated final halt state olcott <polcott333@gmail.com> - 2025-11-06 16:55 -0600
Re: D simulated by H cannot possibly reach its own simulated final halt state dbush <dbush.mobile@gmail.com> - 2025-11-06 18:00 -0500
Re: D simulated by H cannot possibly reach its own simulated final halt state olcott <polcott333@gmail.com> - 2025-11-06 17:12 -0600
Re: D simulated by H cannot possibly reach its own simulated final halt state dbush <dbush.mobile@gmail.com> - 2025-11-06 18:32 -0500
Re: D simulated by H cannot possibly reach its own simulated final halt state olcott <polcott333@gmail.com> - 2025-11-06 17:36 -0600
Re: D simulated by H cannot possibly reach its own simulated final halt state dbush <dbush.mobile@gmail.com> - 2025-11-06 18:43 -0500
Re: D simulated by H cannot possibly reach its own simulated final halt state olcott <polcott333@gmail.com> - 2025-11-06 17:59 -0600
Re: D simulated by H cannot possibly reach its own simulated final halt state dbush <dbush.mobile@gmail.com> - 2025-11-06 19:02 -0500
Re: D simulated by H cannot possibly reach its own simulated final halt state olcott <polcott333@gmail.com> - 2025-11-06 18:28 -0600
Re: D simulated by H cannot possibly reach its own simulated final halt state dbush <dbush.mobile@gmail.com> - 2025-11-06 19:37 -0500
Re: D simulated by H cannot possibly reach its own simulated final halt state olcott <polcott333@gmail.com> - 2025-11-06 18:45 -0600
Re: D simulated by H cannot possibly reach its own simulated final halt state dbush <dbush.mobile@gmail.com> - 2025-11-06 19:50 -0500
Re: D simulated by H cannot possibly reach its own simulated final halt state olcott <polcott333@gmail.com> - 2025-11-06 18:56 -0600
Re: D simulated by H cannot possibly reach its own simulated final halt state dbush <dbush.mobile@gmail.com> - 2025-11-06 19:57 -0500
Re: D simulated by H cannot possibly reach its own simulated final halt state Kaz Kylheku <643-408-1753@kylheku.com> - 2025-11-06 22:07 +0000
Re: D simulated by H cannot possibly reach its own simulated final halt state olcott <polcott333@gmail.com> - 2025-11-06 16:24 -0600
Re: D simulated by H cannot possibly reach its own simulated final halt state dbush <dbush.mobile@gmail.com> - 2025-11-06 17:27 -0500
Re: D simulated by H cannot possibly reach its own simulated final halt state olcott <polcott333@gmail.com> - 2025-11-06 16:52 -0600
Re: D simulated by H cannot possibly reach its own simulated final halt state dbush <dbush.mobile@gmail.com> - 2025-11-06 17:58 -0500
Re: D simulated by H cannot possibly reach its own simulated final halt state olcott <polcott333@gmail.com> - 2025-11-06 17:08 -0600
Re: D simulated by H cannot possibly reach its own simulated final halt state dbush <dbush.mobile@gmail.com> - 2025-11-06 18:35 -0500
Re: D simulated by H cannot possibly reach its own simulated final halt state olcott <polcott333@gmail.com> - 2025-11-06 17:45 -0600
Re: D simulated by H cannot possibly reach its own simulated final halt state dbush <dbush.mobile@gmail.com> - 2025-11-06 18:52 -0500
Re: D simulated by H cannot possibly reach its own simulated final halt state Kaz Kylheku <643-408-1753@kylheku.com> - 2025-11-07 00:00 +0000
Re: D simulated by H cannot possibly reach its own simulated final halt state olcott <polcott333@gmail.com> - 2025-11-06 18:16 -0600
Re: D simulated by H cannot possibly reach its own simulated final halt state Kaz Kylheku <643-408-1753@kylheku.com> - 2025-11-07 01:46 +0000
Re: D simulated by H cannot possibly reach its own simulated final halt state olcott <polcott333@gmail.com> - 2025-11-06 20:46 -0600
Re: D simulated by H cannot possibly reach its own simulated final halt state dbush <dbush.mobile@gmail.com> - 2025-11-06 22:01 -0500
Re: D simulated by H cannot possibly reach its own simulated final halt state Kaz Kylheku <643-408-1753@kylheku.com> - 2025-11-07 04:16 +0000
Re: D simulated by H cannot possibly reach its own simulated final halt state olcott <polcott333@gmail.com> - 2025-11-06 22:19 -0600
Re: D simulated by H cannot possibly reach its own simulated final halt state dbush <dbush.mobile@gmail.com> - 2025-11-06 23:27 -0500
Re: D simulated by H cannot possibly reach its own simulated final halt state joes <noreply@example.org> - 2025-11-07 10:45 +0000
Re: D simulated by H cannot possibly reach its own simulated final halt state olcott <polcott333@gmail.com> - 2025-11-07 06:55 -0600
Re: D simulated by H cannot possibly reach its own simulated final halt state wij <wyniijj5@gmail.com> - 2025-11-07 21:43 +0800
Proof that D simulated by H never reaches its own simulated "return" statement olcott <polcott333@gmail.com> - 2025-11-07 08:06 -0600
Re: Proof that D simulated by H never reaches its own simulated "return" statement wij <wyniijj5@gmail.com> - 2025-11-07 22:12 +0800
Re: Proof that D simulated by H never reaches its own simulated "return" statement olcott <polcott333@gmail.com> - 2025-11-07 08:28 -0600
Re: Proof that D simulated by H never reaches its own simulated "return" statement wij <wyniijj5@gmail.com> - 2025-11-07 22:35 +0800
Re: Proof that D simulated by H never reaches its own simulated "return" statement olcott <polcott333@gmail.com> - 2025-11-07 08:38 -0600
Re: Proof that D simulated by H never reaches its own simulated "return" statement wij <wyniijj5@gmail.com> - 2025-11-07 22:55 +0800
Re: Proof that D simulated by H never reaches its own simulated "return" statement olcott <polcott333@gmail.com> - 2025-11-07 09:06 -0600
Re: Proof that D simulated by H never reaches its own simulated "return" statement wij <wyniijj5@gmail.com> - 2025-11-07 23:17 +0800
Re: Proof that D simulated by H never reaches its own simulated "return" statement olcott <polcott333@gmail.com> - 2025-11-07 09:20 -0600
Re: Proof that D simulated by H never reaches its own simulated "return" statement wij <wyniijj5@gmail.com> - 2025-11-07 23:34 +0800
Re: Proof that D simulated by H never reaches its own simulated "return" statement olcott <polcott333@gmail.com> - 2025-11-07 09:53 -0600
Re: Proof that D simulated by H never reaches its own simulated "return" statement wij <wyniijj5@gmail.com> - 2025-11-08 00:07 +0800
Re: D simulated by H cannot possibly reach its own simulated final halt state joes <noreply@example.org> - 2025-11-07 14:16 +0000
Proof that D simulated by H never reaches its own simulated "return" statement olcott <polcott333@gmail.com> - 2025-11-07 08:29 -0600
Re: D simulated by H cannot possibly reach its own simulated final halt state olcott <NoOne@NoWhere.com> - 2025-11-06 21:31 -0600
Re: D simulated by H cannot possibly reach its own simulated final halt state dbush <dbush.mobile@gmail.com> - 2025-11-06 22:45 -0500
Re: D simulated by H cannot possibly reach its own simulated final halt state Kaz Kylheku <643-408-1753@kylheku.com> - 2025-11-07 03:59 +0000
Re: D simulated by H cannot possibly reach its own simulated final halt state olcott <NoOne@NoWhere.com> - 2025-11-06 22:07 -0600
Re: D simulated by H cannot possibly reach its own simulated final halt state dbush <dbush.mobile@gmail.com> - 2025-11-06 23:11 -0500
Re: D simulated by H cannot possibly reach its own simulated final halt state dbush <dbush.mobile@gmail.com> - 2025-11-06 23:29 -0500
Re: D simulated by H cannot possibly reach its own simulated final halt state olcott <polcott333@gmail.com> - 2025-11-06 22:02 -0600
Re: D simulated by H cannot possibly reach its own simulated final halt state olcott <polcott333@gmail.com> - 2025-11-06 22:04 -0600
Re: D simulated by H cannot possibly reach its own simulated final halt state olcott <polcott333@gmail.com> - 2025-11-06 18:01 -0600
Re: D simulated by H cannot possibly reach its own simulated final halt state dbush <dbush.mobile@gmail.com> - 2025-11-06 19:05 -0500
Re: D simulated by H cannot possibly reach its own simulated final halt state olcott <polcott333@gmail.com> - 2025-11-06 18:30 -0600
Re: D simulated by H cannot possibly reach its own simulated final halt state dbush <dbush.mobile@gmail.com> - 2025-11-06 19:36 -0500
Re: D simulated by H cannot possibly reach its own simulated final halt state olcott <polcott333@gmail.com> - 2025-11-06 18:44 -0600
Re: D simulated by H cannot possibly reach its own simulated final halt state dbush <dbush.mobile@gmail.com> - 2025-11-06 19:49 -0500
Re: D simulated by H cannot possibly reach its own simulated final halt state olcott <polcott333@gmail.com> - 2025-11-06 18:51 -0600
Re: D simulated by H cannot possibly reach its own simulated final halt state dbush <dbush.mobile@gmail.com> - 2025-11-06 19:54 -0500
Re: D simulated by H cannot possibly reach its own simulated final halt state olcott <polcott333@gmail.com> - 2025-11-06 18:57 -0600
Re: D simulated by H cannot possibly reach its own simulated final halt state dbush <dbush.mobile@gmail.com> - 2025-11-06 19:58 -0500
Re: D simulated by H cannot possibly reach its own simulated final halt state Kaz Kylheku <643-408-1753@kylheku.com> - 2025-11-07 01:22 +0000
Re: D simulated by H cannot possibly reach its own simulated final halt state olcott <polcott333@gmail.com> - 2025-11-06 19:25 -0600
Re: D simulated by H cannot possibly reach its own simulated final halt state Kaz Kylheku <643-408-1753@kylheku.com> - 2025-11-07 03:41 +0000
Re: D simulated by H cannot possibly reach its own simulated final halt state olcott <polcott333@gmail.com> - 2025-11-06 22:00 -0600
Re: D simulated by H cannot possibly reach its own simulated final halt state Mikko <mikko.levanto@iki.fi> - 2025-11-07 10:05 +0200
Re: D simulated by H cannot possibly reach its own simulated final halt state olcott <polcott333@gmail.com> - 2025-11-07 06:57 -0600
Re: D simulated by H cannot possibly reach its own simulated final halt state Mikko <mikko.levanto@iki.fi> - 2025-11-08 10:05 +0200
Re: D simulated by H cannot possibly reach its own simulated final halt state olcott <polcott333@gmail.com> - 2025-11-08 07:36 -0600
Re: D simulated by H cannot possibly reach its own simulated final halt state Mikko <mikko.levanto@iki.fi> - 2025-11-09 12:22 +0200
Re: D simulated by H cannot possibly reach its own simulated final halt state olcott <polcott333@gmail.com> - 2025-11-09 06:51 -0600
Re: D simulated by H cannot possibly reach its own simulated final halt state Kaz Kylheku <643-408-1753@kylheku.com> - 2025-11-10 06:17 +0000
Re: D simulated by H cannot possibly reach its own simulated final halt state olcott <polcott333@gmail.com> - 2025-11-10 08:40 -0600
Re: D simulated by H cannot possibly reach its own simulated final halt state Kaz Kylheku <643-408-1753@kylheku.com> - 2025-11-10 23:14 +0000
Re: D simulated by H cannot possibly reach its own simulated final halt state olcott <polcott333@gmail.com> - 2025-11-10 18:27 -0600
Re: D simulated by H cannot possibly reach its own simulated final halt state Kaz Kylheku <643-408-1753@kylheku.com> - 2025-11-11 04:02 +0000
Re: D simulated by H cannot possibly reach its own simulated final halt state olcott <polcott333@gmail.com> - 2025-11-10 09:43 -0600
Re: D simulated by H cannot possibly reach its own simulated final halt state dbush <dbush.mobile@gmail.com> - 2025-11-10 11:28 -0500
Re: D simulated by H cannot possibly reach its own simulated final halt state Kaz Kylheku <643-408-1753@kylheku.com> - 2025-11-10 23:19 +0000
Re: D simulated by H cannot possibly reach its own simulated final halt state olcott <polcott333@gmail.com> - 2025-11-10 21:58 -0600
Re: D simulated by H cannot possibly reach its own simulated final halt state Mikko <mikko.levanto@iki.fi> - 2025-11-10 11:43 +0200
Re: D simulated by H cannot possibly reach its own simulated final halt state olcott <polcott333@gmail.com> - 2025-11-10 08:48 -0600
Re: D simulated by H cannot possibly reach its own simulated final halt state Kaz Kylheku <643-408-1753@kylheku.com> - 2025-11-10 23:09 +0000
Re: D simulated by H cannot possibly reach its own simulated final halt state olcott <polcott333@gmail.com> - 2025-11-10 17:53 -0600
Re: D simulated by H cannot possibly reach its own simulated final halt state Kaz Kylheku <643-408-1753@kylheku.com> - 2025-11-11 03:55 +0000
Re: D simulated by H cannot possibly reach its own simulated final halt state olcott <polcott333@gmail.com> - 2025-11-10 21:59 -0600
Re: D simulated by H cannot possibly reach its own simulated final halt state Kaz Kylheku <643-408-1753@kylheku.com> - 2025-11-11 04:09 +0000
Re: D simulated by H cannot possibly reach its own simulated final halt state olcott <polcott333@gmail.com> - 2025-11-11 06:59 -0600
Re: D simulated by H cannot possibly reach its own simulated final halt state dbush <dbush.mobile@gmail.com> - 2025-11-11 08:03 -0500
Re: D simulated by H cannot possibly reach its own simulated final halt state Kaz Kylheku <643-408-1753@kylheku.com> - 2025-11-11 19:17 +0000
Re: D simulated by H cannot possibly reach its own simulated final halt state olcott <polcott333@gmail.com> - 2025-11-11 15:38 -0600
Re: D simulated by H cannot possibly reach its own simulated final halt state dbush <dbush.mobile@gmail.com> - 2025-11-11 16:56 -0500
How pathological self-reference is confused with undecidability olcott <polcott333@gmail.com> - 2025-11-11 19:38 -0600
Re: How pathological self-reference is confused with undecidability Kaz Kylheku <643-408-1753@kylheku.com> - 2025-11-12 02:13 +0000
Re: How pathological self-reference is confused with undecidability olcott <polcott333@gmail.com> - 2025-11-11 20:33 -0600
Re: How pathological self-reference is confused with undecidability olcott <polcott333@gmail.com> - 2025-11-11 21:05 -0600
Re: How pathological self-reference is confused with undecidability olcott <polcott333@gmail.com> - 2025-11-11 21:45 -0600
Re: How pathological self-reference is confused with undecidability Kaz Kylheku <643-408-1753@kylheku.com> - 2025-11-12 05:52 +0000
Re: How pathological self-reference is confused with undecidability olcott <polcott333@gmail.com> - 2025-11-11 23:59 -0600
Re: How pathological self-reference is confused with undecidability Kaz Kylheku <643-408-1753@kylheku.com> - 2025-11-12 06:13 +0000
Re: How pathological self-reference is confused with undecidability olcott <polcott333@gmail.com> - 2025-11-12 06:50 -0600
Re: How pathological self-reference is confused with undecidability Kaz Kylheku <643-408-1753@kylheku.com> - 2025-11-19 04:41 +0000
Re: How pathological self-reference is confused with undecidability Kaz Kylheku <643-408-1753@kylheku.com> - 2025-11-19 04:41 +0000
Re: How pathological self-reference is confused with undecidability Kaz Kylheku <643-408-1753@kylheku.com> - 2025-11-19 04:41 +0000
Re: D simulated by H cannot possibly reach its own simulated final halt state Kaz Kylheku <643-408-1753@kylheku.com> - 2025-11-12 02:20 +0000
Re: D simulated by H cannot possibly reach its own simulated final halt state olcott <polcott333@gmail.com> - 2025-11-11 20:41 -0600
Re: D simulated by H cannot possibly reach its own simulated final halt state Kaz Kylheku <643-408-1753@kylheku.com> - 2025-11-12 06:11 +0000
Re: D simulated by H cannot possibly reach its own simulated final halt state olcott <polcott333@gmail.com> - 2025-11-12 06:45 -0600
Re: D simulated by H cannot possibly reach its own simulated final halt state olcott <polcott333@gmail.com> - 2025-11-12 07:37 -0600
Re: D simulated by H cannot possibly reach its own simulated final halt state joes <noreply@example.org> - 2025-11-12 15:03 +0000
Re: D simulated by H cannot possibly reach its own simulated final halt state olcott <polcott333@gmail.com> - 2025-11-12 09:11 -0600
Re: D simulated by H cannot possibly reach its own simulated final halt state Kaz Kylheku <643-408-1753@kylheku.com> - 2025-11-13 02:16 +0000
Re: D simulated by H cannot possibly reach its own simulated final halt state dbush <dbush.mobile@gmail.com> - 2025-11-12 21:22 -0500
Re: D simulated by H cannot possibly reach its own simulated final halt state olcott <polcott333@gmail.com> - 2025-11-12 20:30 -0600
Re: D simulated by H cannot possibly reach its own simulated final halt state dbush <dbush.mobile@gmail.com> - 2025-11-12 21:35 -0500
Re: D simulated by H cannot possibly reach its own simulated final halt state Mike Terry <news.dead.person.stones@darjeeling.plus.com> - 2025-11-13 04:44 +0000
Re: D simulated by H cannot possibly reach its own simulated final halt state olcott <polcott333@gmail.com> - 2025-11-12 22:55 -0600
Re: D simulated by H cannot possibly reach its own simulated final halt state Kaz Kylheku <643-408-1753@kylheku.com> - 2025-11-13 08:32 +0000
Re: D simulated by H cannot possibly reach its own simulated final halt state olcott <polcott333@gmail.com> - 2025-11-13 09:36 -0600
Re: D simulated by H cannot possibly reach its own simulated final halt state "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2025-11-13 07:38 -0800
Re: D simulated by H cannot possibly reach its own simulated final halt state Kaz Kylheku <643-408-1753@kylheku.com> - 2025-11-13 17:40 +0000
Re: D simulated by H cannot possibly reach its own simulated final halt state olcott <polcott333@gmail.com> - 2025-11-13 13:20 -0600
Re: D simulated by H cannot possibly reach its own simulated final halt state Kaz Kylheku <643-408-1753@kylheku.com> - 2025-11-13 19:38 +0000
Re: D simulated by H cannot possibly reach its own simulated final halt state olcott <polcott333@gmail.com> - 2025-11-13 14:22 -0600
Re: D simulated by H cannot possibly reach its own simulated final halt state Mikko <mikko.levanto@iki.fi> - 2025-11-11 10:59 +0200
Re: D simulated by H cannot possibly reach its own simulated final halt state olcott <polcott333@gmail.com> - 2025-11-11 07:04 -0600
Re: D simulated by H cannot possibly reach its own simulated final halt state dbush <dbush.mobile@gmail.com> - 2025-11-11 08:05 -0500
Re: D simulated by H cannot possibly reach its own simulated final halt state Mikko <mikko.levanto@iki.fi> - 2025-11-12 09:09 +0200
Re: D simulated by H cannot possibly reach its own simulated final halt state olcott <polcott333@gmail.com> - 2025-11-12 06:54 -0600
Re: D simulated by H cannot possibly reach its own simulated final halt state Mikko <mikko.levanto@iki.fi> - 2025-11-13 10:48 +0200
Re: D simulated by H cannot possibly reach its own simulated final halt state olcott <polcott333@gmail.com> - 2025-11-13 09:50 -0600
Re: D simulated by H cannot possibly reach its own simulated final halt state Mikko <mikko.levanto@iki.fi> - 2025-11-14 11:21 +0200
The halting problem is incorrect two different ways olcott <polcott333@gmail.com> - 2025-11-14 09:00 -0600
Re: The halting problem is incorrect two different ways Mikko <mikko.levanto@iki.fi> - 2025-11-15 12:15 +0200
Re: The halting problem is incorrect two different ways olcott <polcott333@gmail.com> - 2025-11-15 10:12 -0600
Re: The halting problem is incorrect two different ways Mikko <mikko.levanto@iki.fi> - 2025-11-16 11:18 +0200
Re: The halting problem is incorrect two different ways olcott <polcott333@gmail.com> - 2025-11-16 18:12 -0600
Re: The halting problem is incorrect two different ways Mikko <mikko.levanto@iki.fi> - 2025-11-17 10:43 +0200
Re: The halting problem is incorrect two different ways olcott <polcott333@gmail.com> - 2025-11-17 07:31 -0600
Re: The halting problem is incorrect two different ways Mikko <mikko.levanto@iki.fi> - 2025-11-18 12:23 +0200
Re: The halting problem is incorrect two different ways olcott <polcott333@gmail.com> - 2025-11-18 10:43 -0600
Re: The halting problem is incorrect two different ways joes <noreply@example.org> - 2025-11-18 18:04 +0000
Re: The halting problem is incorrect two different ways olcott <polcott333@gmail.com> - 2025-11-18 12:26 -0600
Re: The halting problem is incorrect two different ways Alan Mackenzie <acm@muc.de> - 2025-11-18 18:51 +0000
Re: The halting problem is incorrect two different ways olcott <polcott333@gmail.com> - 2025-11-18 14:01 -0600
Re: The halting problem is incorrect two different ways Alan Mackenzie <acm@muc.de> - 2025-11-18 20:24 +0000
Re: The halting problem is incorrect two different ways olcott <polcott333@gmail.com> - 2025-11-18 14:39 -0600
Re: The halting problem is incorrect two different ways Alan Mackenzie <acm@muc.de> - 2025-11-18 21:30 +0000
Re: The halting problem is incorrect two different ways olcott <polcott333@gmail.com> - 2025-11-18 15:43 -0600
Re: The halting problem is incorrect two different ways olcott <polcott333@gmail.com> - 2025-11-18 15:48 -0600
Weasel word double talk excuses =--- AKA Liars olcott <polcott333@gmail.com> - 2025-11-18 15:57 -0600
Re: The halting problem is incorrect two different ways Mikko <mikko.levanto@iki.fi> - 2025-11-19 11:46 +0200
Re: The halting problem is incorrect two different ways olcott <polcott333@gmail.com> - 2025-11-19 06:59 -0600
Re: The halting problem is incorrect two different ways Mikko <mikko.levanto@iki.fi> - 2025-11-20 11:10 +0200
Re: The halting problem is incorrect two different ways olcott <polcott333@gmail.com> - 2025-11-17 07:31 -0600
Re: The halting problem is incorrect two different ways Mikko <mikko.levanto@iki.fi> - 2025-11-26 12:01 +0200
Re: The halting problem is incorrect two different ways olcott <polcott333@gmail.com> - 2025-11-26 09:17 -0600
Re: The halting problem is incorrect two different ways Richard Damon <Richard@Damon-Family.org> - 2025-11-26 10:29 -0500
Re: The halting problem is incorrect two different ways Kaz Kylheku <643-408-1753@kylheku.com> - 2025-11-26 18:35 +0000
Re: The halting problem is incorrect two different ways olcott <polcott333@gmail.com> - 2025-11-26 13:55 -0600
Re: The halting problem is incorrect two different ways dbush <dbush.mobile@gmail.com> - 2025-11-26 14:58 -0500
Re: The halting problem is incorrect two different ways Kaz Kylheku <643-408-1753@kylheku.com> - 2025-11-26 21:47 +0000
Re: The halting problem is incorrect two different ways olcott <polcott333@gmail.com> - 2025-11-26 15:53 -0600
Re: The halting problem is incorrect two different ways Kaz Kylheku <643-408-1753@kylheku.com> - 2025-11-26 22:19 +0000
Re: The halting problem is incorrect two different ways olcott <polcott333@gmail.com> - 2025-11-26 16:48 -0600
Re: The halting problem is incorrect two different ways dbush <dbush.mobile@gmail.com> - 2025-11-26 18:00 -0500
Re: The halting problem is incorrect two different ways Kaz Kylheku <643-408-1753@kylheku.com> - 2025-11-26 23:55 +0000
Re: The halting problem is incorrect two different ways olcott <polcott333@gmail.com> - 2025-11-26 18:20 -0600
Re: The halting problem is incorrect two different ways Kaz Kylheku <643-408-1753@kylheku.com> - 2025-11-27 00:39 +0000
Re: The halting problem is incorrect two different ways olcott <polcott333@gmail.com> - 2025-11-26 18:51 -0600
Re: The halting problem is incorrect two different ways dbush <dbush.mobile@gmail.com> - 2025-11-26 20:02 -0500
Re: The halting problem is incorrect two different ways Python <python@cccp.invalid> - 2025-11-27 01:24 +0000
Re: The halting problem is incorrect two different ways olcott <polcott333@gmail.com> - 2025-11-26 19:42 -0600
Re: The halting problem is incorrect two different ways Python <python@cccp.invalid> - 2025-11-27 02:00 +0000
Re: The halting problem is incorrect two different ways olcott <polcott333@gmail.com> - 2025-11-26 20:37 -0600
Re: The halting problem is incorrect two different ways Kaz Kylheku <643-408-1753@kylheku.com> - 2025-11-27 04:15 +0000
Re: The halting problem is incorrect two different ways olcott <polcott333@gmail.com> - 2025-11-26 22:31 -0600
Re: The halting problem is incorrect two different ways Kaz Kylheku <643-408-1753@kylheku.com> - 2025-11-27 06:51 +0000
Re: The halting problem is incorrect two different ways olcott <polcott333@gmail.com> - 2025-11-27 08:59 -0600
Re: The halting problem is incorrect two different ways Richard Damon <Richard@Damon-Family.org> - 2025-11-27 10:16 -0500
Re: The halting problem is incorrect two different ways Kaz Kylheku <643-408-1753@kylheku.com> - 2025-11-27 18:17 +0000
Re: The halting problem is incorrect two different ways Richard Damon <Richard@Damon-Family.org> - 2025-11-27 07:41 -0500
Re: The halting problem is incorrect two different ways Richard Damon <Richard@Damon-Family.org> - 2025-11-27 07:40 -0500
Re: The halting problem is incorrect two different ways "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2025-11-26 23:00 -0800
Re: The halting problem is incorrect two different ways Python <python@cccp.invalid> - 2025-11-27 01:39 +0000
Re: The halting problem is incorrect two different ways olcott <polcott333@gmail.com> - 2025-11-26 19:47 -0600
Re: The halting problem is incorrect two different ways Python <python@cccp.invalid> - 2025-11-27 01:59 +0000
Re: The halting problem is incorrect two different ways olcott <polcott333@gmail.com> - 2025-11-26 20:26 -0600
Re: The halting problem is incorrect two different ways Kaz Kylheku <643-408-1753@kylheku.com> - 2025-11-27 04:19 +0000
Re: The halting problem is incorrect two different ways olcott <polcott333@gmail.com> - 2025-11-26 22:39 -0600
Re: The halting problem is incorrect two different ways Mike Terry <news.dead.person.stones@darjeeling.plus.com> - 2025-11-27 04:48 +0000
Re: The halting problem is incorrect two different ways olcott <polcott333@gmail.com> - 2025-11-26 22:58 -0600
Re: The halting problem is incorrect two different ways Kaz Kylheku <643-408-1753@kylheku.com> - 2025-11-27 07:06 +0000
Re: The halting problem is incorrect two different ways "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2025-11-26 23:16 -0800
Re: The halting problem is incorrect two different ways "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2025-11-26 23:21 -0800
Re: The halting problem is incorrect two different ways Jan van den Broek <balglaas@dds.nl> - 2025-11-27 07:45 +0000
Re: The halting problem is incorrect two different ways olcott <polcott333@gmail.com> - 2025-11-27 09:08 -0600
Re: The halting problem is incorrect two different ways Richard Damon <Richard@Damon-Family.org> - 2025-11-27 10:38 -0500
Re: The halting problem is incorrect two different ways Kaz Kylheku <643-408-1753@kylheku.com> - 2025-11-27 18:05 +0000
Re: The halting problem is incorrect two different ways Kaz Kylheku <643-408-1753@kylheku.com> - 2025-11-27 18:05 +0000
Re: The halting problem is incorrect two different ways Kaz Kylheku <643-408-1753@kylheku.com> - 2025-11-27 18:18 +0000
Re: The halting problem is incorrect two different ways "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2025-11-28 16:27 -0800
Re: The halting problem is incorrect two different ways Kaz Kylheku <643-408-1753@kylheku.com> - 2025-11-29 01:25 +0000
Re: The halting problem is incorrect two different ways "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2025-12-01 16:24 -0800
Re: The halting problem is incorrect two different ways "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2025-12-01 16:36 -0800
Re: The halting problem is incorrect two different ways "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2025-11-26 23:14 -0800
Re: The halting problem is incorrect two different ways Mikko <mikko.levanto@iki.fi> - 2025-11-27 09:49 +0200
Re: The halting problem is incorrect two different ways "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2025-11-26 23:58 -0800
Re: The halting problem is incorrect two different ways Mikko <mikko.levanto@iki.fi> - 2025-11-28 10:14 +0200
The halting problem is incorrect two different ways --- updated olcott <polcott333@gmail.com> - 2025-11-28 08:46 -0600
Re: The halting problem is incorrect two different ways --- updated Richard Damon <Richard@Damon-Family.org> - 2025-11-28 10:59 -0500
Re: The halting problem is incorrect two different ways --- updated Mikko <mikko.levanto@iki.fi> - 2025-11-29 11:27 +0200
Re: The halting problem is incorrect two different ways --- updated olcott <polcott333@gmail.com> - 2025-11-29 10:38 -0600
Re: The halting problem is incorrect two different ways --- updated Richard Damon <Richard@Damon-Family.org> - 2025-11-29 14:58 -0500
Re: The halting problem is incorrect two different ways --- updated Mikko <mikko.levanto@iki.fi> - 2025-12-01 12:45 +0200
Re: The halting problem is incorrect two different ways --- updated olcott <polcott333@gmail.com> - 2025-12-01 06:47 -0600
Re: The halting problem is incorrect two different ways --- updated Python <python@cccp.invalid> - 2025-12-01 14:29 +0000
Re: The halting problem is incorrect two different ways --- updated olcott <polcott333@gmail.com> - 2025-12-01 08:38 -0600
Re: The halting problem is incorrect two different ways --- updated Python <python@cccp.invalid> - 2025-12-01 14:45 +0000
Re: The halting problem is incorrect two different ways --- updated olcott <polcott333@gmail.com> - 2025-12-01 08:57 -0600
Re: The halting problem is incorrect two different ways --- updated Python <python@cccp.invalid> - 2025-12-01 15:06 +0000
Re: The halting problem is incorrect two different ways --- updated olcott <polcott333@gmail.com> - 2025-12-01 09:19 -0600
Re: The halting problem is incorrect two different ways --- updated olcott <polcott333@gmail.com> - 2025-12-01 09:26 -0600
Re: The halting problem is incorrect two different ways --- updated olcott <polcott333@gmail.com> - 2025-12-01 09:29 -0600
Re: The halting problem is incorrect two different ways --- updated Python <python@cccp.invalid> - 2025-12-01 15:31 +0000
Re: The halting problem is incorrect two different ways --- updated olcott <polcott333@gmail.com> - 2025-12-01 09:39 -0600
Re: The halting problem is incorrect two different ways --- updated Python <python@cccp.invalid> - 2025-12-01 15:48 +0000
Re: The halting problem is incorrect two different ways --- updated olcott <polcott333@gmail.com> - 2025-12-01 09:55 -0600
Re: The halting problem is incorrect two different ways --- updated Python <python@cccp.invalid> - 2025-12-01 16:00 +0000
Re: The halting problem is incorrect two different ways --- updated olcott <polcott333@gmail.com> - 2025-12-01 10:27 -0600
Re: The halting problem is incorrect two different ways --- updated "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2025-12-01 16:41 -0800
Re: The halting problem is incorrect two different ways --- updated olcott <polcott333@gmail.com> - 2025-12-03 18:24 -0600
Olcott is provably correct --- no one can correctly refute this olcott <polcott333@gmail.com> - 2025-12-03 19:54 -0600
Re: The halting problem is incorrect two different ways --- updated Mikko <mikko.levanto@iki.fi> - 2025-12-02 11:07 +0200
Re: The halting problem is incorrect two different ways --- updated olcott <polcott333@gmail.com> - 2025-12-02 08:14 -0600
Re: The halting problem is incorrect two different ways --- updated Mikko <mikko.levanto@iki.fi> - 2025-12-03 13:34 +0200
Re: The halting problem is incorrect two different ways --- updated olcott <polcott333@gmail.com> - 2025-12-03 10:27 -0600
Re: The halting problem is incorrect two different ways --- updated Mikko <mikko.levanto@iki.fi> - 2025-12-04 11:17 +0200
Re: The halting problem is incorrect two different ways --- updated olcott <polcott333@gmail.com> - 2025-12-04 08:15 -0600
Re: The halting problem is incorrect two different ways --- updated Mikko <mikko.levanto@iki.fi> - 2025-12-06 11:23 +0200
Re: The halting problem is incorrect two different ways --- updated olcott <polcott333@gmail.com> - 2025-12-06 06:47 -0600
Re: The halting problem is incorrect two different ways --- updated Richard Damon <Richard@Damon-Family.org> - 2025-12-06 17:26 -0500
Re: The halting problem is incorrect two different ways --- faking ignorance olcott <polcott333@gmail.com> - 2025-11-27 09:21 -0600
Re: The halting problem is incorrect two different ways --- faking ignorance Richard Damon <Richard@Damon-Family.org> - 2025-11-27 10:40 -0500
Re: The halting problem is incorrect two different ways --- faking ignorance Kaz Kylheku <643-408-1753@kylheku.com> - 2025-11-27 18:37 +0000
Re: The halting problem is incorrect two different ways --- faking ignorance Kaz Kylheku <643-408-1753@kylheku.com> - 2025-11-27 18:24 +0000
Re: The halting problem is incorrect two different ways --- faking ignorance Mikko <mikko.levanto@iki.fi> - 2025-11-28 10:18 +0200
Re: The halting problem is incorrect two different ways --- faking ignorance olcott <polcott333@gmail.com> - 2025-11-28 08:52 -0600
Re: The halting problem is incorrect two different ways --- faking ignorance Richard Damon <Richard@Damon-Family.org> - 2025-11-28 11:01 -0500
Re: D simulated by H cannot possibly reach its own simulated final halt state olcott <polcott333@gmail.com> - 2025-11-10 09:37 -0600
Re: D simulated by H cannot possibly reach its own simulated final halt state Mikko <mikko.levanto@iki.fi> - 2025-11-11 10:56 +0200
Re: D simulated by H cannot possibly reach its own simulated final halt state olcott <polcott333@gmail.com> - 2025-11-11 07:02 -0600
Re: D simulated by H cannot possibly reach its own simulated final halt state dbush <dbush.mobile@gmail.com> - 2025-11-11 08:04 -0500
Re: D simulated by H cannot possibly reach its own simulated final halt state "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2025-11-11 13:19 -0800
Re: D simulated by H cannot possibly reach its own simulated final halt state Mikko <mikko.levanto@iki.fi> - 2025-11-12 09:12 +0200
Re: D simulated by H cannot possibly reach its own simulated final halt state olcott <polcott333@gmail.com> - 2025-11-12 06:56 -0600
Re: D simulated by H cannot possibly reach its own simulated final halt state Mikko <mikko.levanto@iki.fi> - 2025-11-13 10:51 +0200
Re: D simulated by H cannot possibly reach its own simulated final halt state "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2025-11-13 01:00 -0800
Re: D simulated by H cannot possibly reach its own simulated final halt state olcott <polcott333@gmail.com> - 2025-11-13 09:56 -0600
Re: D simulated by H cannot possibly reach its own simulated final halt state Kaz Kylheku <643-408-1753@kylheku.com> - 2025-11-13 19:12 +0000
Re: D simulated by H cannot possibly reach its own simulated final halt state olcott <polcott333@gmail.com> - 2025-11-13 14:39 -0600
Re: D simulated by H cannot possibly reach its own simulated final halt state Mikko <mikko.levanto@iki.fi> - 2025-11-14 11:24 +0200
Re: D simulated by H cannot possibly reach its own simulated final halt state olcott <polcott333@gmail.com> - 2025-11-14 09:12 -0600
Re: D simulated by H cannot possibly reach its own simulated final halt state Mikko <mikko.levanto@iki.fi> - 2025-11-15 12:23 +0200
Re: D simulated by H cannot possibly reach its own simulated final halt state olcott <polcott333@gmail.com> - 2025-11-15 10:14 -0600
Re: D simulated by H cannot possibly reach its own simulated final halt state Mikko <mikko.levanto@iki.fi> - 2025-11-16 11:21 +0200
Re: D simulated by H cannot possibly reach its own simulated final halt state joes <noreply@example.org> - 2025-11-16 15:39 +0000
Re: D simulated by H cannot possibly reach its own simulated final halt state olcott <polcott333@gmail.com> - 2025-11-16 10:15 -0600
Re: D simulated by H cannot possibly reach its own simulated final halt state joes <noreply@example.org> - 2025-11-16 16:24 +0000
Re: D simulated by H cannot possibly reach its own simulated final halt state olcott <polcott333@gmail.com> - 2025-11-16 10:45 -0600
Re: D simulated by H cannot possibly reach its own simulated final halt state joes <noreply@example.org> - 2025-11-16 17:13 +0000
Re: D simulated by H cannot possibly reach its own simulated final halt state olcott <polcott333@gmail.com> - 2025-11-16 11:40 -0600
Re: D simulated by H cannot possibly reach its own simulated final halt state Mikko <mikko.levanto@iki.fi> - 2025-11-17 10:46 +0200
Re: D simulated by H cannot possibly reach its own simulated final halt state olcott <polcott333@gmail.com> - 2025-11-17 07:34 -0600
Re: D simulated by H cannot possibly reach its own simulated final halt state Mikko <mikko.levanto@iki.fi> - 2025-11-18 12:26 +0200
Re: D simulated by H cannot possibly reach its own simulated final halt state olcott <polcott333@gmail.com> - 2025-11-18 10:45 -0600
Re: D simulated by H cannot possibly reach its own simulated final halt state Kaz Kylheku <643-408-1753@kylheku.com> - 2025-11-18 21:21 +0000
Re: D simulated by H cannot possibly reach its own simulated final halt state olcott <polcott333@gmail.com> - 2025-11-18 15:29 -0600
Re: D simulated by H cannot possibly reach its own simulated final halt state dbush <dbush.mobile@gmail.com> - 2025-11-18 16:49 -0500
Re: D simulated by H cannot possibly reach its own simulated final halt state Kaz Kylheku <643-408-1753@kylheku.com> - 2025-11-19 01:01 +0000
Re: D simulated by H cannot possibly reach its own simulated final halt state olcott <polcott333@gmail.com> - 2025-11-18 19:27 -0600
Re: D simulated by H cannot possibly reach its own simulated final halt state Kaz Kylheku <643-408-1753@kylheku.com> - 2025-11-19 02:53 +0000
Re: D simulated by H cannot possibly reach its own simulated final halt state olcott <polcott333@gmail.com> - 2025-11-18 21:07 -0600
Re: D simulated by H cannot possibly reach its own simulated final halt state Kaz Kylheku <643-408-1753@kylheku.com> - 2025-11-19 04:30 +0000
Re: D simulated by H cannot possibly reach its own simulated final halt state Kaz Kylheku <643-408-1753@kylheku.com> - 2025-11-19 04:31 +0000
DDD simulated by HHH cannot possibly reach its own simulated final halt state olcott <polcott333@gmail.com> - 2025-11-18 22:45 -0600
Re: DDD simulated by HHH cannot possibly reach its own simulated final halt state Kaz Kylheku <643-408-1753@kylheku.com> - 2025-11-19 04:52 +0000
Re: DDD simulated by HHH cannot possibly reach its own simulated final halt state olcott <polcott333@gmail.com> - 2025-11-18 23:08 -0600
Re: DDD simulated by HHH cannot possibly reach its own simulated final halt state dbush <dbush.mobile@gmail.com> - 2025-11-19 00:14 -0500
Re: DDD simulated by HHH cannot possibly reach its own simulated final halt state Kaz Kylheku <643-408-1753@kylheku.com> - 2025-11-19 05:23 +0000
Re: DDD simulated by HHH cannot possibly reach its own simulated final halt state joes <noreply@example.org> - 2025-11-19 10:58 +0000
Re: DDD simulated by HHH cannot possibly reach its own simulated final halt state olcott <polcott333@gmail.com> - 2025-11-19 06:18 -0600
Re: D simulated by H cannot possibly reach its own simulated final halt state joes <noreply@example.org> - 2025-11-23 21:20 +0000
Glossary of names of my simulating termination analyzer HHH(DD) olcott <polcott333@gmail.com> - 2025-11-23 16:29 -0600
Re: Glossary of names of my simulating termination analyzer HHH(DD) Mikko <mikko.levanto@iki.fi> - 2025-11-24 11:23 +0200
Re: Glossary of names of my simulating termination analyzer HHH(DD) olcott <polcott333@gmail.com> - 2025-11-24 07:30 -0600
Re: D simulated by H cannot possibly reach its own simulated final halt state Mikko <mikko.levanto@iki.fi> - 2025-11-19 11:50 +0200
Re: D simulated by H cannot possibly reach its own simulated final halt state olcott <polcott333@gmail.com> - 2025-11-19 07:01 -0600
Re: D simulated by H cannot possibly reach its own simulated final halt state Mikko <mikko.levanto@iki.fi> - 2025-11-20 11:11 +0200
Re: D simulated by H cannot possibly reach its own simulated final halt state olcott <polcott333@gmail.com> - 2025-11-21 13:54 -0600
Re: D simulated by H cannot possibly reach its own simulated final halt state Kaz Kylheku <643-408-1753@kylheku.com> - 2025-11-21 21:58 +0000
Re: D simulated by H cannot possibly reach its own simulated final halt state olcott <polcott333@gmail.com> - 2025-11-21 23:09 -0600
Re: D simulated by H cannot possibly reach its own simulated final halt state Kaz Kylheku <643-408-1753@kylheku.com> - 2025-11-22 06:49 +0000
polcott agrees the Kaz is a damned liar --- DD simulated by HHH olcott <polcott333@gmail.com> - 2025-11-22 07:22 -0600
Re: polcott agrees the Kaz is a damned liar --- DD simulated by HHH Kaz Kylheku <643-408-1753@kylheku.com> - 2025-11-22 17:51 +0000
Re: polcott agrees the Kaz is a damned liar --- DD simulated by HHH olcott <polcott333@gmail.com> - 2025-11-22 12:06 -0600
Re: polcott agrees the Kaz is a damned liar --- DD simulated by HHH Kaz Kylheku <643-408-1753@kylheku.com> - 2025-11-22 18:08 +0000
Re: polcott agrees the Kaz is a damned liar --- DD simulated by HHH Kaz Kylheku <643-408-1753@kylheku.com> - 2025-11-22 18:08 +0000
Re: polcott agrees the Kaz is a damned liar --- DD simulated by HHH Kaz Kylheku <643-408-1753@kylheku.com> - 2025-11-23 03:53 +0000
Re: D simulated by H cannot possibly reach its own simulated final halt state Kaz Kylheku <643-408-1753@kylheku.com> - 2025-11-22 07:03 +0000
polcott agrees the Kaz is a damned liar --- DD simulated by HHH olcott <polcott333@gmail.com> - 2025-11-22 07:33 -0600
Re: polcott agrees the Kaz is a damned liar --- DD simulated by HHH Kaz Kylheku <643-408-1753@kylheku.com> - 2025-11-22 17:56 +0000
Dangerous Precipice that could end all life --- DD simulated by HHH olcott <polcott333@gmail.com> - 2025-11-22 13:29 -0600
Re: Dangerous Precipice that could end all life --- DD simulated by HHH Kaz Kylheku <643-408-1753@kylheku.com> - 2025-11-23 04:00 +0000
Re: Dangerous Precipice that could end all life --- DD simulated by HHH olcott <polcott333@gmail.com> - 2025-11-22 23:02 -0600
Re: Dangerous Precipice that could end all life --- DD simulated by HHH Kaz Kylheku <643-408-1753@kylheku.com> - 2025-11-23 05:23 +0000
Re: Dangerous Precipice that could end all life --- DD simulated by HHH Kaz Kylheku <643-408-1753@kylheku.com> - 2025-11-23 05:24 +0000
Re: Dangerous Precipice that could end all life --- DD simulated by HHH olcott <polcott333@gmail.com> - 2025-11-23 14:53 -0600
Re: Dangerous Precipice that could end all life --- DD simulated by HHH "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2025-11-23 13:32 -0800
Re: Dangerous Precipice that could end all life --- DD simulated by HHH Kaz Kylheku <643-408-1753@kylheku.com> - 2025-11-24 02:44 +0000
Re: Dangerous Precipice that could end all life --- DD simulated by HHH Kaz Kylheku <643-408-1753@kylheku.com> - 2025-11-24 02:45 +0000
DD simulated by HHH and DD simulated by HHH1 olcott <polcott333@gmail.com> - 2025-11-23 21:15 -0600
Re: DD simulated by HHH and DD simulated by HHH1 "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2025-11-23 23:54 -0800
Re: DD simulated by HHH and DD simulated by HHH1 Kaz Kylheku <643-408-1753@kylheku.com> - 2025-11-24 16:32 +0000
Re: DD simulated by HHH and DD simulated by HHH1 Kaz Kylheku <643-408-1753@kylheku.com> - 2025-11-24 16:32 +0000
Re: DD simulated by HHH and DD simulated by HHH1 olcott <polcott333@gmail.com> - 2025-11-24 10:37 -0600
Re: DD simulated by HHH and DD simulated by HHH1 Kaz Kylheku <643-408-1753@kylheku.com> - 2025-11-24 17:55 +0000
Re: DD simulated by HHH and DD simulated by HHH1 olcott <polcott333@gmail.com> - 2025-11-24 12:08 -0600
Re: DD simulated by HHH and DD simulated by HHH1 Kaz Kylheku <643-408-1753@kylheku.com> - 2025-11-24 19:22 +0000
Re: DD simulated by HHH and DD simulated by HHH1 Kaz Kylheku <643-408-1753@kylheku.com> - 2025-11-24 19:30 +0000
Re: DD simulated by HHH and DD simulated by HHH1 olcott <polcott333@gmail.com> - 2025-11-24 14:20 -0600
Re: DD simulated by HHH and DD simulated by HHH1 Kaz Kylheku <643-408-1753@kylheku.com> - 2025-11-24 22:31 +0000
Re: DD simulated by HHH and DD simulated by HHH1 Kaz Kylheku <643-408-1753@kylheku.com> - 2025-11-24 22:45 +0000
Re: DD simulated by HHH and DD simulated by HHH1 olcott <NoOne@NoWhere.com> - 2025-11-24 17:23 -0600
Re: DD simulated by HHH and DD simulated by HHH1 Richard Heathfield <rjh@cpax.org.uk> - 2025-11-25 05:10 +0000
Re: DD simulated by HHH and DD simulated by HHH1 olcott <polcott333@gmail.com> - 2025-11-24 23:25 -0600
Re: DD simulated by HHH and DD simulated by HHH1 Richard Damon <Richard@Damon-Family.org> - 2025-11-25 10:34 -0500
Re: DD simulated by HHH and DD simulated by HHH1 Richard Heathfield <rjh@cpax.org.uk> - 2025-11-26 05:43 +0000
Re: DD simulated by HHH and DD simulated by HHH1 olcott <polcott333@gmail.com> - 2025-11-25 23:51 -0600
Re: DD simulated by HHH and DD simulated by HHH1 Richard Damon <Richard@Damon-Family.org> - 2025-11-26 07:21 -0500
Re: DD simulated by HHH and DD simulated by HHH1 Richard Heathfield <rjh@cpax.org.uk> - 2025-11-26 17:37 +0000
Re: DD simulated by HHH and DD simulated by HHH1 Richard Damon <Richard@Damon-Family.org> - 2025-11-26 12:52 -0500
Re: DD simulated by HHH and DD simulated by HHH1 Richard Heathfield <rjh@cpax.org.uk> - 2025-11-26 17:59 +0000
Re: DD simulated by HHH and DD simulated by HHH1 olcott <polcott333@gmail.com> - 2025-11-26 12:32 -0600
Re: DD simulated by HHH and DD simulated by HHH1 olcott <polcott333@gmail.com> - 2025-11-26 12:28 -0600
Re: DD simulated by HHH and DD simulated by HHH1 "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2025-11-25 12:45 -0800
Re: DD simulated by HHH and DD simulated by HHH1 olcott <polcott333@gmail.com> - 2025-11-24 10:45 -0600
Re: DD simulated by HHH and DD simulated by HHH1 tTh <tth@none.invalid> - 2025-11-24 19:45 +0100
Re: DD simulated by HHH and DD simulated by HHH1 Mike Terry <news.dead.person.stones@darjeeling.plus.com> - 2025-11-24 18:12 +0000
Re: DD simulated by HHH and DD simulated by HHH1 olcott <polcott333@gmail.com> - 2025-11-24 12:21 -0600
Re: DD simulated by HHH and DD simulated by HHH1 Kaz Kylheku <643-408-1753@kylheku.com> - 2025-11-24 19:30 +0000
Re: DD simulated by HHH and DD simulated by HHH1 dbush <dbush.mobile@gmail.com> - 2025-11-24 14:32 -0500
Re: DD simulated by HHH and DD simulated by HHH1 olcott <polcott333@gmail.com> - 2025-11-24 14:15 -0600
Re: DD simulated by HHH and DD simulated by HHH1 Kaz Kylheku <643-408-1753@kylheku.com> - 2025-11-24 22:25 +0000
Re: DD simulated by HHH and DD simulated by HHH1 olcott <polcott333@gmail.com> - 2025-11-24 17:21 -0600
Re: DD simulated by HHH and DD simulated by HHH1 dbush <dbush.mobile@gmail.com> - 2025-11-24 13:47 -0500
Re: DD simulated by HHH and DD simulated by HHH1 Ross Finlayson <ross.a.finlayson@gmail.com> - 2025-11-24 11:20 -0800
Re: DD simulated by HHH and DD simulated by HHH1 Kaz Kylheku <643-408-1753@kylheku.com> - 2025-11-24 19:27 +0000
Re: DD simulated by HHH and DD simulated by HHH1 olcott <polcott333@gmail.com> - 2025-11-24 14:14 -0600
Re: DD simulated by HHH and DD simulated by HHH1 Kaz Kylheku <643-408-1753@kylheku.com> - 2025-11-24 22:22 +0000
Re: DD simulated by HHH and DD simulated by HHH1 olcott <polcott333@gmail.com> - 2025-11-24 17:19 -0600
Re: DD simulated by HHH and DD simulated by HHH1 "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2025-11-24 16:15 -0800
Re: DD simulated by HHH and DD simulated by HHH1 "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2025-11-24 16:25 -0800
Re: DD simulated by HHH and DD simulated by HHH1 Kaz Kylheku <643-408-1753@kylheku.com> - 2025-11-25 01:39 +0000
Re: DD simulated by HHH and DD simulated by HHH1 Kaz Kylheku <643-408-1753@kylheku.com> - 2025-11-25 02:15 +0000
Re: DD simulated by HHH and DD simulated by HHH1 olcott <polcott333@gmail.com> - 2025-11-24 22:12 -0600
Re: DD simulated by HHH and DD simulated by HHH1 Mike Terry <news.dead.person.stones@darjeeling.plus.com> - 2025-11-24 23:33 +0000
Re: DD simulated by HHH and DD simulated by HHH1 olcott <polcott333@gmail.com> - 2025-11-24 18:33 -0600
Re: DD simulated by HHH and DD simulated by HHH1 "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2025-11-24 16:37 -0800
Re: DD simulated by HHH and DD simulated by HHH1 Mike Terry <news.dead.person.stones@darjeeling.plus.com> - 2025-11-25 02:10 +0000
Re: DD simulated by HHH and DD simulated by HHH1 olcott <polcott333@gmail.com> - 2025-11-24 22:10 -0600
Re: DD simulated by HHH and DD simulated by HHH1 Richard Damon <Richard@Damon-Family.org> - 2025-11-25 10:38 -0500
Re: DD simulated by HHH and DD simulated by HHH1 olcott <polcott333@gmail.com> - 2025-11-24 14:47 -0600
Re: DD simulated by HHH and DD simulated by HHH1 Kaz Kylheku <643-408-1753@kylheku.com> - 2025-11-24 22:35 +0000
Re: DD simulated by HHH and DD simulated by HHH1 "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2025-11-24 19:43 -0800
Re: DD simulated by HHH and DD simulated by HHH1 Kaz Kylheku <643-408-1753@kylheku.com> - 2025-11-24 22:45 +0000
Re: DD simulated by HHH and DD simulated by HHH1 olcott <NoOne@NoWhere.com> - 2025-11-24 17:24 -0600
Re: DD simulated by HHH and DD simulated by HHH1 Kaz Kylheku <643-408-1753@kylheku.com> - 2025-11-25 01:42 +0000
Re: DD simulated by HHH and DD simulated by HHH1 Kaz Kylheku <643-408-1753@kylheku.com> - 2025-11-25 02:15 +0000
Re: DD simulated by HHH and DD simulated by HHH1 olcott <polcott333@gmail.com> - 2025-11-24 22:35 -0600
Re: DD simulated by HHH and DD simulated by HHH1 Kaz Kylheku <643-408-1753@kylheku.com> - 2025-11-25 07:00 +0000
Re: DD simulated by HHH and DD simulated by HHH1 Kaz Kylheku <643-408-1753@kylheku.com> - 2025-11-25 07:00 +0000
Re: DD simulated by HHH and DD simulated by HHH1 olcott <polcott333@gmail.com> - 2025-11-25 08:56 -0600
Re: DD simulated by HHH and DD simulated by HHH1 Richard Damon <Richard@Damon-Family.org> - 2025-11-25 10:49 -0500
Re: DD simulated by HHH and DD simulated by HHH1 Kaz Kylheku <643-408-1753@kylheku.com> - 2025-11-25 17:39 +0000
Re: DD simulated by HHH and DD simulated by HHH1 olcott <polcott333@gmail.com> - 2025-11-25 11:44 -0600
Re: DD simulated by HHH and DD simulated by HHH1 Richard Damon <Richard@Damon-Family.org> - 2025-11-25 13:06 -0500
Re: DD simulated by HHH and DD simulated by HHH1 olcott <polcott333@gmail.com> - 2025-11-25 11:50 -0600
Re: DD simulated by HHH and DD simulated by HHH1 Richard Damon <Richard@Damon-Family.org> - 2025-11-25 13:06 -0500
Re: DD simulated by HHH and DD simulated by HHH1 olcott <polcott333@gmail.com> - 2025-11-25 09:44 -0600
Re: DD simulated by HHH and DD simulated by HHH1 Richard Damon <Richard@Damon-Family.org> - 2025-11-25 10:46 -0500
Re: DD simulated by HHH and DD simulated by HHH1 Mike Terry <news.dead.person.stones@darjeeling.plus.com> - 2025-11-25 19:19 +0000
Re: DD simulated by HHH and DD simulated by HHH1 olcott <polcott333@gmail.com> - 2025-11-25 13:35 -0600
Re: DD simulated by HHH and DD simulated by HHH1 Kaz Kylheku <643-408-1753@kylheku.com> - 2025-11-25 20:27 +0000
Re: DD simulated by HHH and DD simulated by HHH1 Kaz Kylheku <643-408-1753@kylheku.com> - 2025-11-25 20:27 +0000
Re: DD simulated by HHH and DD simulated by HHH1 olcott <polcott333@gmail.com> - 2025-11-25 14:52 -0600
Re: DD simulated by HHH and DD simulated by HHH1 Richard Damon <Richard@Damon-Family.org> - 2025-11-25 16:42 -0500
Re: DD simulated by HHH and DD simulated by HHH1 Kaz Kylheku <643-408-1753@kylheku.com> - 2025-11-25 20:38 +0000
Re: DD simulated by HHH and DD simulated by HHH1 olcott <polcott333@gmail.com> - 2025-11-25 14:56 -0600
Re: DD simulated by HHH and DD simulated by HHH1 "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2025-11-25 13:32 -0800
Re: DD simulated by HHH and DD simulated by HHH1 Mike Terry <news.dead.person.stones@darjeeling.plus.com> - 2025-11-28 17:24 +0000
Re: DD simulated by HHH and DD simulated by HHH1 olcott <polcott333@gmail.com> - 2025-11-28 12:09 -0600
Re: D simulated by H cannot possibly reach its own simulated final halt state Mikko <mikko.levanto@iki.fi> - 2025-11-22 10:25 +0200
Re: D simulated by H cannot possibly reach its own simulated final halt state Richard Damon <Richard@Damon-Family.org> - 2025-11-24 22:30 -0500
Re: D simulated by H cannot possibly reach its own simulated final halt state Bonita Montero <Bonita.Montero@gmail.com> - 2025-11-25 16:20 +0100
Re: D simulated by H cannot possibly reach its own simulated final halt state olcott <polcott333@gmail.com> - 2025-11-25 09:47 -0600
Re: D simulated by H cannot possibly reach its own simulated final halt state Bonita Montero <Bonita.Montero@gmail.com> - 2025-11-25 16:50 +0100
Re: D simulated by H cannot possibly reach its own simulated final halt state olcott <polcott333@gmail.com> - 2025-11-25 10:09 -0600
Re: D simulated by H cannot possibly reach its own simulated final halt state Kaz Kylheku <643-408-1753@kylheku.com> - 2025-11-25 17:33 +0000
Re: D simulated by H cannot possibly reach its own simulated final halt state Kaz Kylheku <643-408-1753@kylheku.com> - 2025-11-25 17:36 +0000
Re: D simulated by H cannot possibly reach its own simulated final halt state Richard Damon <Richard@Damon-Family.org> - 2025-11-25 11:37 -0500
Re: D simulated by H cannot possibly reach its own simulated final halt state Kaz Kylheku <643-408-1753@kylheku.com> - 2025-11-25 17:29 +0000
Re: D simulated by H cannot possibly reach its own simulated final halt state olcott <polcott333@gmail.com> - 2025-11-25 11:39 -0600
Re: D simulated by H cannot possibly reach its own simulated final halt state Kaz Kylheku <643-408-1753@kylheku.com> - 2025-11-25 17:44 +0000
Re: D simulated by H cannot possibly reach its own simulated final halt state olcott <polcott333@gmail.com> - 2025-11-25 12:04 -0600
Re: D simulated by H cannot possibly reach its own simulated final halt state Richard Damon <Richard@Damon-Family.org> - 2025-11-25 13:09 -0500
Re: D simulated by H cannot possibly reach its own simulated final halt state olcott <polcott333@gmail.com> - 2025-11-25 12:36 -0600
Re: D simulated by H cannot possibly reach its own simulated final halt state Kaz Kylheku <643-408-1753@kylheku.com> - 2025-11-25 19:08 +0000
Olcott creates a new foundation for automated correct reasoning olcott <polcott333@gmail.com> - 2025-11-25 13:22 -0600
Re: Olcott creates a new foundation for automated correct reasoning Richard Damon <Richard@Damon-Family.org> - 2025-11-25 16:47 -0500
Re: D simulated by H cannot possibly reach its own simulated final halt state "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2025-11-25 12:35 -0800
Re: D simulated by H cannot possibly reach its own simulated final halt state Richard Damon <Richard@Damon-Family.org> - 2025-11-25 16:45 -0500
Re: D simulated by H cannot possibly reach its own simulated final halt state "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2025-11-25 21:05 -0800
Re: D simulated by H cannot possibly reach its own simulated final halt state Richard Damon <Richard@Damon-Family.org> - 2025-11-26 07:22 -0500
Re: D simulated by H cannot possibly reach its own simulated final halt state Mike Terry <news.dead.person.stones@darjeeling.plus.com> - 2025-11-26 17:13 +0000
Re: D simulated by H cannot possibly reach its own simulated final halt state "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2025-11-26 22:36 -0800
Re: D simulated by H cannot possibly reach its own simulated final halt state "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2025-11-26 22:41 -0800
Re: D simulated by H cannot possibly reach its own simulated final halt state Richard Damon <Richard@Damon-Family.org> - 2025-11-25 13:08 -0500
Re: D simulated by H cannot possibly reach its own simulated final halt state Kaz Kylheku <643-408-1753@kylheku.com> - 2025-11-25 17:42 +0000
Re: D simulated by H cannot possibly reach its own simulated final halt state olcott <polcott333@gmail.com> - 2025-11-25 11:52 -0600
Re: D simulated by H cannot possibly reach its own simulated final halt state Kaz Kylheku <643-408-1753@kylheku.com> - 2025-11-25 18:46 +0000
Re: D simulated by H cannot possibly reach its own simulated final halt state olcott <polcott333@gmail.com> - 2025-11-25 13:18 -0600
Re: D simulated by H cannot possibly reach its own simulated final halt state dart200 <user7160@newsgrouper.org.invalid> - 2025-11-25 12:05 -0800
New formal foundation for correct reasoning makes True(X) computable olcott <polcott333@gmail.com> - 2025-11-25 14:20 -0600
Re: New formal foundation for correct reasoning makes True(X) computable Python <python@cccp.invalid> - 2025-11-25 20:56 +0000
Re: New formal foundation for correct reasoning makes True(X) computable olcott <polcott333@gmail.com> - 2025-11-25 15:01 -0600
Re: New formal foundation for correct reasoning makes True(X) computable Python <python@cccp.invalid> - 2025-11-25 21:03 +0000
Re: New formal foundation for correct reasoning makes True(X) computable olcott <polcott333@gmail.com> - 2025-11-25 15:09 -0600
Re: New formal foundation for correct reasoning makes True(X) computable Python <python@cccp.invalid> - 2025-11-25 21:12 +0000
Re: New formal foundation for correct reasoning makes True(X) computable olcott <polcott333@gmail.com> - 2025-11-25 15:27 -0600
Re: New formal foundation for correct reasoning makes True(X) computable "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2025-11-25 13:30 -0800
Re: New formal foundation for correct reasoning makes True(X) computable Python <python@cccp.invalid> - 2025-11-25 23:14 +0000
Re: New formal foundation for correct reasoning makes True(X) computable olcott <polcott333@gmail.com> - 2025-11-25 17:21 -0600
Re: New formal foundation for correct reasoning makes True(X) computable Python <python@cccp.invalid> - 2025-11-25 23:25 +0000
Re: New formal foundation for correct reasoning makes True(X) computable olcott <polcott333@gmail.com> - 2025-11-25 18:00 -0600
Re: New formal foundation for correct reasoning makes True(X) computable Python <python@cccp.invalid> - 2025-11-26 00:04 +0000
Re: New formal foundation for correct reasoning makes True(X) computable olcott <polcott333@gmail.com> - 2025-11-25 18:14 -0600
Re: New formal foundation for correct reasoning makes True(X) computable Python <python@cccp.invalid> - 2025-11-26 00:18 +0000
Re: New formal foundation for correct reasoning makes True(X) computable olcott <polcott333@gmail.com> - 2025-11-25 18:38 -0600
Re: New formal foundation for correct reasoning makes True(X) computable Python <python@cccp.invalid> - 2025-11-26 00:42 +0000
Re: New formal foundation for correct reasoning makes True(X) computable Kaz Kylheku <643-408-1753@kylheku.com> - 2025-11-26 00:47 +0000
Re: New formal foundation for correct reasoning makes True(X) computable olcott <polcott333@gmail.com> - 2025-11-25 18:52 -0600
Re: New formal foundation for correct reasoning makes True(X) computable Python <python@cccp.invalid> - 2025-11-26 00:57 +0000
Re: New formal foundation for correct reasoning makes True(X) computable olcott <polcott333@gmail.com> - 2025-11-25 19:19 -0600
Re: New formal foundation for correct reasoning makes True(X) computable Python <python@cccp.invalid> - 2025-11-26 01:29 +0000
Re: New formal foundation for correct reasoning makes True(X) computable Python <python@cccp.invalid> - 2025-11-26 01:32 +0000
Re: New formal foundation for correct reasoning makes True(X) computable André G. Isaak <agisaak@gm.invalid> - 2025-11-25 18:29 -0700
Re: New formal foundation for correct reasoning makes True(X) computable olcott <polcott333@gmail.com> - 2025-11-25 19:43 -0600
Re: New formal foundation for correct reasoning makes True(X) computable Python <python@cccp.invalid> - 2025-11-26 01:45 +0000
Re: New formal foundation for correct reasoning makes True(X) computable olcott <polcott333@gmail.com> - 2025-11-25 20:03 -0600
Re: New formal foundation for correct reasoning makes True(X) computable Python <python@cccp.invalid> - 2025-11-26 02:09 +0000
Re: New formal foundation for correct reasoning makes True(X) computable olcott <polcott333@gmail.com> - 2025-11-25 20:34 -0600
Re: New formal foundation for correct reasoning makes True(X) computable Python <python@cccp.invalid> - 2025-11-26 02:36 +0000
Re: New formal foundation for correct reasoning makes True(X) computable olcott <polcott333@gmail.com> - 2025-11-25 20:46 -0600
Re: New formal foundation for correct reasoning makes True(X) computable Python <python@cccp.invalid> - 2025-11-26 02:47 +0000
Re: New formal foundation for correct reasoning makes True(X) computable olcott <polcott333@gmail.com> - 2025-11-25 21:01 -0600
Re: New formal foundation for correct reasoning makes True(X) computable Python <python@cccp.invalid> - 2025-11-26 03:03 +0000
Re: New formal foundation for correct reasoning makes True(X) computable olcott <polcott333@gmail.com> - 2025-11-25 21:11 -0600
Re: New formal foundation for correct reasoning makes True(X) computable Richard Damon <Richard@Damon-Family.org> - 2025-11-26 07:34 -0500
Re: New formal foundation for correct reasoning makes True(X) computable olcott <polcott333@gmail.com> - 2025-12-05 17:03 -0600
Re: New formal foundation for correct reasoning makes True(X) computable olcott <polcott333@gmail.com> - 2025-12-05 19:53 -0600
Re: New formal foundation for correct reasoning makes True(X) computable olcott <polcott333@gmail.com> - 2025-11-25 20:36 -0600
Re: New formal foundation for correct reasoning makes True(X) computable Python <python@cccp.invalid> - 2025-11-26 02:38 +0000
Re: New formal foundation for correct reasoning makes True(X) computable "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2025-11-26 19:36 -0800
Re: New formal foundation for correct reasoning makes True(X) computable polcott <polcott333@gmail.com> - 2025-11-26 22:10 -0600
Re: New formal foundation for correct reasoning makes True(X) computable "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2025-11-25 21:30 -0800
Re: New formal foundation for correct reasoning makes True(X) computable Kaz Kylheku <643-408-1753@kylheku.com> - 2025-11-26 02:36 +0000
Re: New formal foundation for correct reasoning makes True(X) computable olcott <polcott333@gmail.com> - 2025-11-25 20:43 -0600
Re: New formal foundation for correct reasoning makes True(X) computable Kaz Kylheku <643-408-1753@kylheku.com> - 2025-11-26 03:09 +0000
Re: New formal foundation for correct reasoning makes True(X) computable olcott <polcott333@gmail.com> - 2025-11-25 21:17 -0600
Re: New formal foundation for correct reasoning makes True(X) computable Kaz Kylheku <643-408-1753@kylheku.com> - 2025-11-26 03:26 +0000
Re: New formal foundation for correct reasoning makes True(X) computable olcott <polcott333@gmail.com> - 2025-11-25 21:32 -0600
Re: New formal foundation for correct reasoning makes True(X) computable Kaz Kylheku <643-408-1753@kylheku.com> - 2025-11-26 05:15 +0000
Re: New formal foundation for correct reasoning makes True(X) computable Richard Damon <Richard@Damon-Family.org> - 2025-11-26 07:36 -0500
Re: New formal foundation for correct reasoning makes True(X) computable Mikko <mikko.levanto@iki.fi> - 2025-11-26 11:22 +0200
Re: New formal foundation for correct reasoning makes True(X) computable olcott <polcott333@gmail.com> - 2025-11-26 09:15 -0600
Re: New formal foundation for correct reasoning makes True(X) computable dbush <dbush.mobile@gmail.com> - 2025-11-26 10:20 -0500
Re: New formal foundation for correct reasoning makes True(X) computable Richard Damon <Richard@Damon-Family.org> - 2025-11-26 10:31 -0500
Re: New formal foundation for correct reasoning makes True(X) computable "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2025-11-26 19:43 -0800
Re: New formal foundation for correct reasoning makes True(X) computable Mikko <mikko.levanto@iki.fi> - 2025-11-27 09:40 +0200
Re: New formal foundation for correct reasoning makes True(X) computable olcott <polcott333@gmail.com> - 2025-11-27 09:17 -0600
Re: New formal foundation for correct reasoning makes True(X) computable Richard Damon <Richard@Damon-Family.org> - 2025-11-27 10:42 -0500
Re: New formal foundation for correct reasoning makes True(X) computable Mikko <mikko.levanto@iki.fi> - 2025-11-28 10:29 +0200
Re: New formal foundation for correct reasoning makes True(X) computable olcott <polcott333@gmail.com> - 2025-11-28 08:54 -0600
Re: New formal foundation for correct reasoning makes True(X) computable Kaz Kylheku <643-408-1753@kylheku.com> - 2025-11-28 17:22 +0000
Re: New formal foundation for correct reasoning makes True(X) computable "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2025-11-28 16:31 -0800
Re: New formal foundation for correct reasoning makes True(X) computable Mikko <mikko.levanto@iki.fi> - 2025-11-29 11:40 +0200
Re: New formal foundation for correct reasoning makes True(X) computable olcott <polcott333@gmail.com> - 2025-11-29 10:42 -0600
Re: New formal foundation for correct reasoning makes True(X) computable Richard Damon <Richard@Damon-Family.org> - 2025-11-29 15:01 -0500
Re: New formal foundation for correct reasoning makes True(X) computable Mikko <mikko.levanto@iki.fi> - 2025-11-30 12:19 +0200
Re: New formal foundation for correct reasoning makes True(X) computable olcott <polcott333@gmail.com> - 2025-11-25 20:45 -0600
Re: New formal foundation for correct reasoning makes True(X) computable Python <python@cccp.invalid> - 2025-11-26 02:46 +0000
Re: New formal foundation for correct reasoning makes True(X) computable olcott <polcott333@gmail.com> - 2025-11-25 21:22 -0600
Re: New formal foundation for correct reasoning makes True(X) computable Python <python@cccp.invalid> - 2025-11-26 03:24 +0000
Re: New formal foundation for correct reasoning makes True(X) computable Kaz Kylheku <643-408-1753@kylheku.com> - 2025-11-26 03:27 +0000
Re: New formal foundation for correct reasoning makes True(X) computable olcott <polcott333@gmail.com> - 2025-11-25 21:33 -0600
Re: New formal foundation for correct reasoning makes True(X) computable Python <python@cccp.invalid> - 2025-11-26 03:36 +0000
Re: New formal foundation for correct reasoning makes True(X) computable olcott <polcott333@gmail.com> - 2025-11-25 21:50 -0600
Re: New formal foundation for correct reasoning makes True(X) computable Python <python@cccp.invalid> - 2025-11-26 03:53 +0000
Re: New formal foundation for correct reasoning makes True(X) computable Python <python@cccp.invalid> - 2025-11-26 03:58 +0000
Re: New formal foundation for correct reasoning makes True(X) computable olcott <polcott333@gmail.com> - 2025-11-25 22:18 -0600
Re: New formal foundation for correct reasoning makes True(X) computable Python <python@cccp.invalid> - 2025-11-26 04:21 +0000
Re: New formal foundation for correct reasoning makes True(X) computable "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2025-11-26 21:56 -0800
Re: New formal foundation for correct reasoning makes True(X) computable "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2025-11-26 21:54 -0800
Re: New formal foundation for correct reasoning makes True(X) computable dart200 <user7160@newsgrouper.org.invalid> - 2025-11-25 20:22 -0800
Re: New formal foundation for correct reasoning makes True(X) computable Python <python@cccp.invalid> - 2025-11-26 04:23 +0000
Re: New formal foundation for correct reasoning makes True(X) computable dart200 <user7160@newsgrouper.org.invalid> - 2025-11-25 20:55 -0800
Re: New formal foundation for correct reasoning makes True(X) computable "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2025-11-26 21:58 -0800
Re: New formal foundation for correct reasoning makes True(X) computable olcott <polcott333@gmail.com> - 2025-11-25 22:06 -0600
Re: New formal foundation for correct reasoning makes True(X) computable Python <python@cccp.invalid> - 2025-11-26 04:11 +0000
Re: New formal foundation for correct reasoning makes True(X) computable dart200 <user7160@newsgrouper.org.invalid> - 2025-11-25 20:23 -0800
Re: New formal foundation for correct reasoning makes True(X) computable Python <python@cccp.invalid> - 2025-11-26 04:24 +0000
Re: New formal foundation for correct reasoning makes True(X) computable dart200 <user7160@newsgrouper.org.invalid> - 2025-11-25 20:56 -0800
Re: New formal foundation for correct reasoning makes True(X) computable "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2025-11-26 22:01 -0800
Re: New formal foundation for correct reasoning makes True(X) computable olcott <polcott333@gmail.com> - 2025-11-26 08:53 -0600
Re: New formal foundation for correct reasoning makes True(X) computable dbush <dbush.mobile@gmail.com> - 2025-11-26 10:06 -0500
Re: New formal foundation for correct reasoning makes True(X) computable "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2025-11-26 21:59 -0800
Re: New formal foundation for correct reasoning makes True(X) computable Kaz Kylheku <643-408-1753@kylheku.com> - 2025-11-26 05:18 +0000
Re: New formal foundation for correct reasoning makes True(X) computable Kaz Kylheku <643-408-1753@kylheku.com> - 2025-11-26 05:16 +0000
Re: New formal foundation for correct reasoning makes True(X) computable Kaz Kylheku <643-408-1753@kylheku.com> - 2025-11-26 03:14 +0000
Re: New formal foundation for correct reasoning makes True(X) computable Richard Damon <Richard@Damon-Family.org> - 2025-11-26 07:27 -0500
Re: New formal foundation for correct reasoning makes True(X) computable André G. Isaak <agisaak@gm.invalid> - 2025-11-25 19:00 -0700
Re: New formal foundation for correct reasoning makes True(X) computable olcott <polcott333@gmail.com> - 2025-11-25 20:08 -0600
Re: New formal foundation for correct reasoning makes True(X) computable André G. Isaak <agisaak@gm.invalid> - 2025-11-25 19:12 -0700
Re: New formal foundation for correct reasoning makes True(X) computable olcott <polcott333@gmail.com> - 2025-11-25 20:30 -0600
Re: New formal foundation for correct reasoning makes True(X) computable André G. Isaak <agisaak@gm.invalid> - 2025-11-25 19:36 -0700
Re: New formal foundation for correct reasoning makes True(X) computable olcott <polcott333@gmail.com> - 2025-11-25 20:41 -0600
Re: New formal foundation for correct reasoning makes True(X) computable Python <python@cccp.invalid> - 2025-11-26 02:43 +0000
Re: New formal foundation for correct reasoning makes True(X) computable olcott <polcott333@gmail.com> - 2025-11-25 21:24 -0600
Re: New formal foundation for correct reasoning makes True(X) computable Python <python@cccp.invalid> - 2025-11-26 03:26 +0000
Re: New formal foundation for correct reasoning makes True(X) computable Kaz Kylheku <643-408-1753@kylheku.com> - 2025-11-26 03:30 +0000
Re: New formal foundation for correct reasoning makes True(X) computable olcott <polcott333@gmail.com> - 2025-11-25 21:45 -0600
Re: New formal foundation for correct reasoning makes True(X) computable Python <python@cccp.invalid> - 2025-11-26 03:47 +0000
Re: New formal foundation for correct reasoning makes True(X) computable olcott <polcott333@gmail.com> - 2025-11-25 22:01 -0600
Re: New formal foundation for correct reasoning makes True(X) computable Python <python@cccp.invalid> - 2025-11-26 04:07 +0000
Re: New formal foundation for correct reasoning makes True(X) computable olcott <polcott333@gmail.com> - 2025-11-26 08:44 -0600
Re: New formal foundation for correct reasoning makes True(X) computable dbush <dbush.mobile@gmail.com> - 2025-11-26 10:04 -0500
Re: New formal foundation for correct reasoning makes True(X) computable Richard Damon <Richard@Damon-Family.org> - 2025-11-26 10:34 -0500
Re: New formal foundation for correct reasoning makes True(X) computable Mikko <mikko.levanto@iki.fi> - 2025-11-26 11:05 +0200
Re: New formal foundation for correct reasoning makes True(X) computable olcott <polcott333@gmail.com> - 2025-11-26 08:58 -0600
Re: New formal foundation for correct reasoning makes True(X) computable Mikko <mikko.levanto@iki.fi> - 2025-11-27 09:30 +0200
Re: New formal foundation for correct reasoning makes True(X) computable olcott <polcott333@gmail.com> - 2025-11-27 09:16 -0600
Re: New formal foundation for correct reasoning makes True(X) computable Mikko <mikko.levanto@iki.fi> - 2025-11-28 10:35 +0200
Re: New formal foundation for correct reasoning makes True(X) computable olcott <polcott333@gmail.com> - 2025-11-28 09:16 -0600
Re: New formal foundation for correct reasoning makes True(X) computable Mikko <mikko.levanto@iki.fi> - 2025-11-29 11:44 +0200
Re: New formal foundation for correct reasoning makes True(X) computable olcott <polcott333@gmail.com> - 2025-11-29 10:40 -0600
Re: New formal foundation for correct reasoning makes True(X) computable Mikko <mikko.levanto@iki.fi> - 2025-11-30 12:14 +0200
Re: New formal foundation for correct reasoning makes True(X) computable olcott <polcott333@gmail.com> - 2025-11-26 09:13 -0600
Re: New formal foundation for correct reasoning makes True(X) computable Mikko <mikko.levanto@iki.fi> - 2025-11-28 10:36 +0200
Re: New formal foundation for correct reasoning makes True(X) computable olcott <polcott333@gmail.com> - 2025-11-28 09:18 -0600
Re: New formal foundation for correct reasoning makes True(X) computable Mikko <mikko.levanto@iki.fi> - 2025-11-29 11:48 +0200
Re: New formal foundation for correct reasoning makes True(X) computable olcott <polcott333@gmail.com> - 2025-11-29 10:45 -0600
Re: New formal foundation for correct reasoning makes True(X) computable Mikko <mikko.levanto@iki.fi> - 2025-11-30 12:07 +0200
Re: New formal foundation for correct reasoning makes True(X) computable Mikko <mikko.levanto@iki.fi> - 2025-12-03 12:53 +0200
Re: New formal foundation for correct reasoning makes True(X) computable olcott <polcott333@gmail.com> - 2025-12-03 10:11 -0600
Re: New formal foundation for correct reasoning makes True(X) computable Mikko <mikko.levanto@iki.fi> - 2025-12-04 11:07 +0200
Re: New formal foundation for correct reasoning makes True(X) computable olcott <polcott333@gmail.com> - 2025-12-04 08:10 -0600
Re: New formal foundation for correct reasoning makes True(X) computable Mikko <mikko.levanto@iki.fi> - 2025-12-05 11:13 +0200
Re: New formal foundation for correct reasoning makes True(X) computable olcott <polcott333@gmail.com> - 2025-12-05 11:40 -0600
Re: New formal foundation for correct reasoning makes True(X) computable Mikko <mikko.levanto@iki.fi> - 2025-12-06 11:19 +0200
Re: New formal foundation for correct reasoning makes True(X) computable olcott <polcott333@gmail.com> - 2025-12-06 06:45 -0600
Re: New formal foundation for correct reasoning makes True(X) computable Mikko <mikko.levanto@iki.fi> - 2025-12-07 12:55 +0200
Re: New formal foundation for correct reasoning makes True(X) computable olcott <polcott333@gmail.com> - 2025-12-08 13:44 -0600
Re: New formal foundation for correct reasoning makes True(X) computable Mikko <mikko.levanto@iki.fi> - 2025-12-06 11:21 +0200
Re: New formal foundation for correct reasoning makes True(X) computable olcott <polcott333@gmail.com> - 2025-12-06 06:46 -0600
Re: New formal foundation for correct reasoning makes True(X) computable Mikko <mikko.levanto@iki.fi> - 2025-12-07 12:50 +0200
Re: New formal foundation for correct reasoning makes True(X) computable olcott <polcott333@gmail.com> - 2025-12-07 11:15 -0600
Re: New formal foundation for correct reasoning makes True(X) computable Mikko <mikko.levanto@iki.fi> - 2025-12-08 11:08 +0200
Re: New formal foundation for correct reasoning makes True(X) computable olcott <polcott333@gmail.com> - 2025-12-08 13:05 -0600
Re: New formal foundation for correct reasoning makes True(X) computable Mikko <mikko.levanto@iki.fi> - 2025-12-13 13:05 +0200
Re: New formal foundation for correct reasoning makes True(X) computable olcott <polcott333@gmail.com> - 2025-12-13 09:55 -0600
Re: New formal foundation for correct reasoning makes True(X) computable Mikko <mikko.levanto@iki.fi> - 2025-12-15 11:52 +0200
Re: New formal foundation for correct reasoning makes True(X) computable olcott <polcott333@gmail.com> - 2025-12-15 09:49 -0600
Re: New formal foundation for correct reasoning makes True(X) computable Mikko <mikko.levanto@iki.fi> - 2025-12-17 12:49 +0200
Re: New formal foundation for correct reasoning makes True(X) computable André G. Isaak <agisaak@gm.invalid> - 2025-11-25 19:45 -0700
Re: New formal foundation for correct reasoning makes True(X) computable olcott <polcott333@gmail.com> - 2025-11-25 20:59 -0600
Re: New formal foundation for correct reasoning makes True(X) computable Kaz Kylheku <643-408-1753@kylheku.com> - 2025-11-26 03:16 +0000
Re: New formal foundation for correct reasoning makes True(X) computable Kaz Kylheku <643-408-1753@kylheku.com> - 2025-11-26 02:34 +0000
Re: New formal foundation for correct reasoning makes True(X) computable olcott <polcott333@gmail.com> - 2025-11-25 20:37 -0600
Re: New formal foundation for correct reasoning makes True(X) computable Kaz Kylheku <643-408-1753@kylheku.com> - 2025-11-26 03:02 +0000
Re: New formal foundation for correct reasoning makes True(X) computable olcott <polcott333@gmail.com> - 2025-11-25 21:06 -0600
Re: New formal foundation for correct reasoning makes True(X) computable Python <python@cccp.invalid> - 2025-11-26 03:08 +0000
Re: New formal foundation for correct reasoning makes True(X) computable Kaz Kylheku <643-408-1753@kylheku.com> - 2025-11-26 03:19 +0000
Re: New formal foundation for correct reasoning makes True(X) computable olcott <polcott333@gmail.com> - 2025-11-25 21:28 -0600
Re: New formal foundation for correct reasoning makes True(X) computable Richard Heathfield <rjh@cpax.org.uk> - 2025-11-26 05:53 +0000
Re: New formal foundation for correct reasoning makes True(X) computable "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2025-11-26 22:15 -0800
Re: New formal foundation for correct reasoning makes True(X) computable olcott <polcott333@gmail.com> - 2025-11-25 21:21 -0600
Re: New formal foundation for correct reasoning makes True(X) computable "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2025-11-26 22:16 -0800
Re: New formal foundation for correct reasoning makes True(X) computable dart200 <user7160@newsgrouper.org.invalid> - 2025-11-25 19:08 -0800
Re: New formal foundation for correct reasoning makes True(X) computable olcott <polcott333@gmail.com> - 2025-11-25 21:19 -0600
Re: New formal foundation for correct reasoning makes True(X) computable dart200 <user7160@newsgrouper.org.invalid> - 2025-11-25 19:22 -0800
Re: New formal foundation for correct reasoning makes True(X) computable olcott <polcott333@gmail.com> - 2025-11-25 21:30 -0600
Re: New formal foundation for correct reasoning makes True(X) computable "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2025-11-26 22:18 -0800
Re: New formal foundation for correct reasoning makes True(X) computable "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2025-11-26 22:14 -0800
Re: New formal foundation for correct reasoning makes True(X) computable Kaz Kylheku <643-408-1753@kylheku.com> - 2025-11-26 01:48 +0000
Re: New formal foundation for correct reasoning makes True(X) computable Richard Damon <Richard@Damon-Family.org> - 2025-11-25 20:59 -0500
Re: New formal foundation for correct reasoning makes True(X) computable "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2025-11-25 21:11 -0800
Re: New formal foundation for correct reasoning makes True(X) computable Tristan Wibberley <tristan.wibberley+netnews2@alumni.manchester.ac.uk> - 2025-11-26 19:16 +0000
Re: New formal foundation for correct reasoning makes True(X) computable Tristan Wibberley <tristan.wibberley+netnews2@alumni.manchester.ac.uk> - 2025-11-26 19:34 +0000
Re: New formal foundation for correct reasoning makes True(X) computable "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2025-11-26 20:05 -0800
Re: New formal foundation for correct reasoning makes True(X) computable "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2025-11-25 13:27 -0800
Re: New formal foundation for correct reasoning makes True(X) computable Tristan Wibberley <tristan.wibberley+netnews2@alumni.manchester.ac.uk> - 2025-11-26 19:23 +0000
Re: New formal foundation for correct reasoning makes True(X) computable dbush <dbush.mobile@gmail.com> - 2025-11-26 14:40 -0500
Re: New formal foundation for correct reasoning makes True(X) computable "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2025-11-26 20:03 -0800
Re: New formal foundation for correct reasoning makes True(X) computable dart200 <user7160@newsgrouper.org.invalid> - 2025-11-25 16:29 -0800
Re: New formal foundation for correct reasoning makes True(X) computable Python <python@cccp.invalid> - 2025-11-26 00:31 +0000
Re: New formal foundation for correct reasoning makes True(X) computable dart200 <user7160@newsgrouper.org.invalid> - 2025-11-25 17:09 -0800
Re: New formal foundation for correct reasoning makes True(X) computable Python <python@cccp.invalid> - 2025-11-26 01:19 +0000
Re: New formal foundation for correct reasoning makes True(X) computable dart200 <user7160@newsgrouper.org.invalid> - 2025-11-25 18:38 -0800
Re: New formal foundation for correct reasoning makes True(X) computable Python <python@cccp.invalid> - 2025-11-26 02:40 +0000
Re: New formal foundation for correct reasoning makes True(X) computable dart200 <user7160@newsgrouper.org.invalid> - 2025-11-25 19:16 -0800
Re: New formal foundation for correct reasoning makes True(X) computable olcott <polcott333@gmail.com> - 2025-11-25 18:40 -0600
Re: New formal foundation for correct reasoning makes True(X) computable Python <python@cccp.invalid> - 2025-11-26 00:45 +0000
Page 18 of 32 — ← Prev page 1 … 16 17 [18] 19 20 … 32 Next page →
| From | Kaz Kylheku <643-408-1753@kylheku.com> |
|---|---|
| Date | 2025-11-24 17:55 +0000 |
| Subject | Re: DD simulated by HHH and DD simulated by HHH1 |
| Message-ID | <20251124094728.243@kylheku.com> |
| In reply to | #136336 |
On 2025-11-24, olcott <polcott333@gmail.com> wrote:
> On 11/24/2025 10:32 AM, Kaz Kylheku wrote:
>> On 2025-11-24, olcott <polcott333@gmail.com> wrote:
>>> On 11/22/2025 11:24 PM, Kaz Kylheku wrote:
>>>> That's just the thing! If this were correctly implemented then in fact
>>>> DD /wold be/ calling HHH1, using the name HHH.
>>>>
>>>
>>> You are trying to get away with this lie
>>> about the semantics of C?
>>>
>>> int main()
>>> {
>>> HHH(DD);
>>> HHH1(DD);
>>> return 0;
>>> }
>>>
>>> _main()
>>> [000022c4] 55 push ebp
>>> [000022c5] 8bec mov ebp,esp
>>> [000022c7] 6834220000 push 00002234 ; push DD
>>> [000022cc] e833f3ffff call 00001604 ; call HHH
>>> [000022d1] 83c404 add esp,+04
>>> [000022d4] 6834220000 push 00002234 ; push DD
>>> [000022d9] e856f2ffff call 00001534 ; call HHH1
>>> [000022de] 83c404 add esp,+04
>>> [000022e1] 33c0 xor eax,eax
>>> [000022e3] 5d pop ebp
>>> [000022e4] c3 ret
>>> Size in bytes:(0033) [000022e4]
>>
>> That's right; even if HHH and HHH1 are separately realized and given
>> different adddresses, not recognized as identical by the compiler and
>> not folded into one copy, in a correct implementation of your software,
>> HHH(DD) and HHH1(DD) would behave as indistinguishable, mutually
>> interchangeable operations.
>>
>> The problem is that you have logic which concludes that HHH1 != HHH (low
>> level pointer comparison), they are different functions.
>>
>
> Except when their input calls themself.
That makes no difference.
> In this case they must simulate themselves
> simulating their input, not just simulate
> their input.
In a correctly implemented C simulation of the theory, there
is no difference between HHH and HHH1.
This means that when HHH1 simulates DD, and DD calls HHH,
HHH1 is simulating a call to itself: i.e. simulating a call
to a procedure that is /equivalent/ to itself.
I.e. from HHH1's p.o.v. HHH is itself, and from HHH's p.o.v. HHH1
is itself.
If you use pointer comparison as a cheap substitute for equality,
then you get wrong results. Just like from the point of view
"Hello", another string "Hello" at a different address is not itself
if looking at pointers.
So for instance
char *liar1 = "This sentence is false";
char *liar2 = "This sentence is false";
if you wrongly compare pointers, then from the perspective of liar1,
liar2 is not "this sentence". But obviously it is; they are the
same string.
Moreover, if you were using programming, such as with C, to explore
the Liar Paradox, you could not use strcmp string comparison either.
Because the following are all the same:
"This sentence is false"
"This sentence is false!"
"THIS SENTENCE IS FALSE."
"This sentence is not true."
"Not true, this sentence be."
You need to identify all of these, and numerous others, as being equal
and as all being instances of the same thing: the Liar Paradox. And
that's just if you restrict to English.
Equivalence of logical assertions and programming language expressions
is functional: do they /calculate/ or /denote/ the same result.
--
TXR Programming Language: http://nongnu.org/txr
Cygnal: Cygwin Native Application Library: http://kylheku.com/cygnal
Mastodon: @Kazinator@mstdn.ca
[toc] | [prev] | [next] | [standalone]
| From | olcott <polcott333@gmail.com> |
|---|---|
| Date | 2025-11-24 12:08 -0600 |
| Subject | Re: DD simulated by HHH and DD simulated by HHH1 |
| Message-ID | <10g26vs$2lph1$1@dont-email.me> |
| In reply to | #136339 |
On 11/24/2025 11:55 AM, Kaz Kylheku wrote:
> On 2025-11-24, olcott <polcott333@gmail.com> wrote:
>> On 11/24/2025 10:32 AM, Kaz Kylheku wrote:
>>> On 2025-11-24, olcott <polcott333@gmail.com> wrote:
>>>> On 11/22/2025 11:24 PM, Kaz Kylheku wrote:
>>>>> That's just the thing! If this were correctly implemented then in fact
>>>>> DD /wold be/ calling HHH1, using the name HHH.
>>>>>
>>>>
>>>> You are trying to get away with this lie
>>>> about the semantics of C?
>>>>
>>>> int main()
>>>> {
>>>> HHH(DD);
>>>> HHH1(DD);
>>>> return 0;
>>>> }
>>>>
>>>> _main()
>>>> [000022c4] 55 push ebp
>>>> [000022c5] 8bec mov ebp,esp
>>>> [000022c7] 6834220000 push 00002234 ; push DD
>>>> [000022cc] e833f3ffff call 00001604 ; call HHH
>>>> [000022d1] 83c404 add esp,+04
>>>> [000022d4] 6834220000 push 00002234 ; push DD
>>>> [000022d9] e856f2ffff call 00001534 ; call HHH1
>>>> [000022de] 83c404 add esp,+04
>>>> [000022e1] 33c0 xor eax,eax
>>>> [000022e3] 5d pop ebp
>>>> [000022e4] c3 ret
>>>> Size in bytes:(0033) [000022e4]
>>>
>>> That's right; even if HHH and HHH1 are separately realized and given
>>> different adddresses, not recognized as identical by the compiler and
>>> not folded into one copy, in a correct implementation of your software,
>>> HHH(DD) and HHH1(DD) would behave as indistinguishable, mutually
>>> interchangeable operations.
>>>
>>> The problem is that you have logic which concludes that HHH1 != HHH (low
>>> level pointer comparison), they are different functions.
>>>
>>
>> Except when their input calls themself.
>
> That makes no difference.
>
typedef int (*ptr)();
int HHH(ptr P);
int HHH1(ptr P);
int DD()
{
int Halt_Status = HHH(DD);
if (Halt_Status)
HERE: goto HERE;
return Halt_Status;
}
int main()
{
HHH(DD);
HHH1(DD);
}
HHH simulates DD that calls HHH(DD)
that simulates DD that calls HHH(DD)...
HHH1 simulates DD that calls HHH(DD) that
returns to DD that returns to HHH1.
--
Copyright 2025 Olcott
My 28 year goal has been to make
"true on the basis of meaning" computable.
[toc] | [prev] | [next] | [standalone]
| From | Kaz Kylheku <643-408-1753@kylheku.com> |
|---|---|
| Date | 2025-11-24 19:22 +0000 |
| Subject | Re: DD simulated by HHH and DD simulated by HHH1 |
| Message-ID | <20251124111443.615@kylheku.com> |
| In reply to | #136340 |
On 2025-11-24, olcott <polcott333@gmail.com> wrote:
> On 11/24/2025 11:55 AM, Kaz Kylheku wrote:
>> On 2025-11-24, olcott <polcott333@gmail.com> wrote:
>>> On 11/24/2025 10:32 AM, Kaz Kylheku wrote:
>>>> On 2025-11-24, olcott <polcott333@gmail.com> wrote:
>>>>> On 11/22/2025 11:24 PM, Kaz Kylheku wrote:
>>>>>> That's just the thing! If this were correctly implemented then in fact
>>>>>> DD /wold be/ calling HHH1, using the name HHH.
>>>>>>
>>>>>
>>>>> You are trying to get away with this lie
>>>>> about the semantics of C?
>>>>>
>>>>> int main()
>>>>> {
>>>>> HHH(DD);
>>>>> HHH1(DD);
>>>>> return 0;
>>>>> }
>>>>>
>>>>> _main()
>>>>> [000022c4] 55 push ebp
>>>>> [000022c5] 8bec mov ebp,esp
>>>>> [000022c7] 6834220000 push 00002234 ; push DD
>>>>> [000022cc] e833f3ffff call 00001604 ; call HHH
>>>>> [000022d1] 83c404 add esp,+04
>>>>> [000022d4] 6834220000 push 00002234 ; push DD
>>>>> [000022d9] e856f2ffff call 00001534 ; call HHH1
>>>>> [000022de] 83c404 add esp,+04
>>>>> [000022e1] 33c0 xor eax,eax
>>>>> [000022e3] 5d pop ebp
>>>>> [000022e4] c3 ret
>>>>> Size in bytes:(0033) [000022e4]
>>>>
>>>> That's right; even if HHH and HHH1 are separately realized and given
>>>> different adddresses, not recognized as identical by the compiler and
>>>> not folded into one copy, in a correct implementation of your software,
>>>> HHH(DD) and HHH1(DD) would behave as indistinguishable, mutually
>>>> interchangeable operations.
>>>>
>>>> The problem is that you have logic which concludes that HHH1 != HHH (low
>>>> level pointer comparison), they are different functions.
>>>>
>>>
>>> Except when their input calls themself.
>>
>> That makes no difference.
>>
>
> typedef int (*ptr)();
> int HHH(ptr P);
> int HHH1(ptr P);
Please, don't post this repeated crap any more.
When I say "that makes no difference", I'm saying that it makes no
difference in the theory and therefore /must not/ make any difference
in your exploratory code.
You a must have the skill and know-how to write the key details of your
C code such that it is ensured that HHH1(P) and HHH(P) are
interchangeable, equivalent expressions, such that substituting
one for the other.
Those details are not present in the code you are pasting here,
so it is absolutely pointless:
> int DD()
> {
> int Halt_Status = HHH(DD);
> if (Halt_Status)
> HERE: goto HERE;
> return Halt_Status;
> }
>
> int main()
> {
> HHH(DD);
> HHH1(DD);
> }
>
> HHH simulates DD that calls HHH(DD)
> that simulates DD that calls HHH(DD)...
>
> HHH1 simulates DD that calls HHH(DD) that
> returns to DD that returns to HHH1.
So you basically lack the capacity for the abstract thinking
required to do computer science at the first year level.
--
TXR Programming Language: http://nongnu.org/txr
Cygnal: Cygwin Native Application Library: http://kylheku.com/cygnal
Mastodon: @Kazinator@mstdn.ca
[toc] | [prev] | [next] | [standalone]
| From | Kaz Kylheku <643-408-1753@kylheku.com> |
|---|---|
| Date | 2025-11-24 19:30 +0000 |
| Subject | Re: DD simulated by HHH and DD simulated by HHH1 |
| Message-ID | <10g2bph$2neps$4@dont-email.me> |
| In reply to | #136340 |
On 2025-11-24, olcott <polcott333@gmail.com> wrote:
> On 11/24/2025 11:55 AM, Kaz Kylheku wrote:
>> On 2025-11-24, olcott <polcott333@gmail.com> wrote:
>>> On 11/24/2025 10:32 AM, Kaz Kylheku wrote:
>>>> On 2025-11-24, olcott <polcott333@gmail.com> wrote:
>>>>> On 11/22/2025 11:24 PM, Kaz Kylheku wrote:
>>>>>> That's just the thing! If this were correctly implemented then in fact
>>>>>> DD /wold be/ calling HHH1, using the name HHH.
>>>>>>
>>>>>
>>>>> You are trying to get away with this lie
>>>>> about the semantics of C?
>>>>>
>>>>> int main()
>>>>> {
>>>>> HHH(DD);
>>>>> HHH1(DD);
>>>>> return 0;
>>>>> }
>>>>>
>>>>> _main()
>>>>> [000022c4] 55 push ebp
>>>>> [000022c5] 8bec mov ebp,esp
>>>>> [000022c7] 6834220000 push 00002234 ; push DD
>>>>> [000022cc] e833f3ffff call 00001604 ; call HHH
>>>>> [000022d1] 83c404 add esp,+04
>>>>> [000022d4] 6834220000 push 00002234 ; push DD
>>>>> [000022d9] e856f2ffff call 00001534 ; call HHH1
>>>>> [000022de] 83c404 add esp,+04
>>>>> [000022e1] 33c0 xor eax,eax
>>>>> [000022e3] 5d pop ebp
>>>>> [000022e4] c3 ret
>>>>> Size in bytes:(0033) [000022e4]
>>>>
>>>> That's right; even if HHH and HHH1 are separately realized and given
>>>> different adddresses, not recognized as identical by the compiler and
>>>> not folded into one copy, in a correct implementation of your software,
>>>> HHH(DD) and HHH1(DD) would behave as indistinguishable, mutually
>>>> interchangeable operations.
>>>>
>>>> The problem is that you have logic which concludes that HHH1 != HHH (low
>>>> level pointer comparison), they are different functions.
>>>>
>>>
>>> Except when their input calls themself.
>>
>> That makes no difference.
>>
>
> typedef int (*ptr)();
> int HHH(ptr P);
> int HHH1(ptr P);
Please, don't post this repeated crap any more.
When I say "that makes no difference", I'm saying that it makes no
difference in the theory and therefore /must not/ make any difference
in your exploratory code.
You a must have the skill and know-how to write the key details of your
C code such that it is ensured that HHH1(P) and HHH(P) are
interchangeable, equivalent expressions, such that substituting
one for the other.
Those details are not present in the code you are pasting here,
so it is absolutely pointless:
> int DD()
> {
> int Halt_Status = HHH(DD);
> if (Halt_Status)
> HERE: goto HERE;
> return Halt_Status;
> }
>
> int main()
> {
> HHH(DD);
> HHH1(DD);
> }
>
> HHH simulates DD that calls HHH(DD)
> that simulates DD that calls HHH(DD)...
>
> HHH1 simulates DD that calls HHH(DD) that
> returns to DD that returns to HHH1.
So you basically lack the capacity for the abstract thinking
required to do computer science at the first year level.
--
TXR Programming Language: http://nongnu.org/txr
Cygnal: Cygwin Native Application Library: http://kylheku.com/cygnal
Mastodon: @Kazinator@mstdn.ca
[toc] | [prev] | [next] | [standalone]
| From | olcott <polcott333@gmail.com> |
|---|---|
| Date | 2025-11-24 14:20 -0600 |
| Subject | Re: DD simulated by HHH and DD simulated by HHH1 |
| Message-ID | <10g2emj$2p377$1@dont-email.me> |
| In reply to | #136350 |
On 11/24/2025 1:30 PM, Kaz Kylheku wrote:
> On 2025-11-24, olcott <polcott333@gmail.com> wrote:
>> On 11/24/2025 11:55 AM, Kaz Kylheku wrote:
>>> On 2025-11-24, olcott <polcott333@gmail.com> wrote:
>>>> On 11/24/2025 10:32 AM, Kaz Kylheku wrote:
>>>>> On 2025-11-24, olcott <polcott333@gmail.com> wrote:
>>>>>> On 11/22/2025 11:24 PM, Kaz Kylheku wrote:
>>>>>>> That's just the thing! If this were correctly implemented then in fact
>>>>>>> DD /wold be/ calling HHH1, using the name HHH.
>>>>>>>
>>>>>>
>>>>>> You are trying to get away with this lie
>>>>>> about the semantics of C?
>>>>>>
>>>>>> int main()
>>>>>> {
>>>>>> HHH(DD);
>>>>>> HHH1(DD);
>>>>>> return 0;
>>>>>> }
>>>>>>
>>>>>> _main()
>>>>>> [000022c4] 55 push ebp
>>>>>> [000022c5] 8bec mov ebp,esp
>>>>>> [000022c7] 6834220000 push 00002234 ; push DD
>>>>>> [000022cc] e833f3ffff call 00001604 ; call HHH
>>>>>> [000022d1] 83c404 add esp,+04
>>>>>> [000022d4] 6834220000 push 00002234 ; push DD
>>>>>> [000022d9] e856f2ffff call 00001534 ; call HHH1
>>>>>> [000022de] 83c404 add esp,+04
>>>>>> [000022e1] 33c0 xor eax,eax
>>>>>> [000022e3] 5d pop ebp
>>>>>> [000022e4] c3 ret
>>>>>> Size in bytes:(0033) [000022e4]
>>>>>
>>>>> That's right; even if HHH and HHH1 are separately realized and given
>>>>> different adddresses, not recognized as identical by the compiler and
>>>>> not folded into one copy, in a correct implementation of your software,
>>>>> HHH(DD) and HHH1(DD) would behave as indistinguishable, mutually
>>>>> interchangeable operations.
>>>>>
>>>>> The problem is that you have logic which concludes that HHH1 != HHH (low
>>>>> level pointer comparison), they are different functions.
>>>>>
>>>>
>>>> Except when their input calls themself.
>>>
>>> That makes no difference.
>>>
>>
>> typedef int (*ptr)();
>> int HHH(ptr P);
>> int HHH1(ptr P);
>
> Please, don't post this repeated crap any more.
>
As long as you keep lying I will keep repeating it.
If five people from comp.lang.c confirm that you
are lying and I am correct then I will quit posting it.
typedef int (*ptr)();
int HHH(ptr P);
int HHH1(ptr P);
int DD()
{
int Halt_Status = HHH(DD);
if (Halt_Status)
HERE: goto HERE;
return Halt_Status;
}
int main()
{
HHH(DD);
HHH1(DD);
}
HHH simulates DD that calls HHH(DD)
that simulates DD that calls HHH(DD)...
HHH1 simulates DD that calls HHH(DD) that
returns to DD that returns to HHH1.
--
Copyright 2025 Olcott
My 28 year goal has been to make
"true on the basis of meaning" computable.
[toc] | [prev] | [next] | [standalone]
| From | Kaz Kylheku <643-408-1753@kylheku.com> |
|---|---|
| Date | 2025-11-24 22:31 +0000 |
| Subject | Re: DD simulated by HHH and DD simulated by HHH1 |
| Message-ID | <20251124142538.434@kylheku.com> |
| In reply to | #136355 |
On 2025-11-24, olcott <polcott333@gmail.com> wrote: > As long as you keep lying I will keep repeating it. To lie is to knowing post something that is false. But if you do that about an objectively verifiable fact that has nothing to do with yourself, but some scientific matter, nobody in their right mind will see you as a liar. Rather than see you as a liar, they will just assume you are ignorant and incompetent. What makes you think I, or Mike, or anyone here would write something I know to be false, which would be interpreted as ignorant, rather than dishonest? Maybe you don't understand that nobody would do that, since you have no problem being casually wrong yourself. -- TXR Programming Language: http://nongnu.org/txr Cygnal: Cygwin Native Application Library: http://kylheku.com/cygnal Mastodon: @Kazinator@mstdn.ca
[toc] | [prev] | [next] | [standalone]
| From | Kaz Kylheku <643-408-1753@kylheku.com> |
|---|---|
| Date | 2025-11-24 22:45 +0000 |
| Subject | Re: DD simulated by HHH and DD simulated by HHH1 |
| Message-ID | <10g2n66$2rqmd$6@dont-email.me> |
| In reply to | #136355 |
On 2025-11-24, olcott <polcott333@gmail.com> wrote: > As long as you keep lying I will keep repeating it. To lie is to knowing post something that is false. But if you do that about an objectively verifiable fact that has nothing to do with yourself, but some scientific matter, nobody in their right mind will see you as a liar. Rather than see you as a liar, they will just assume you are ignorant and incompetent. What makes you think I, or Mike, or anyone here would write something I know to be false, which would be interpreted as ignorant, rather than dishonest? Maybe you don't understand that nobody would do that, since you have no problem being casually wrong yourself. -- TXR Programming Language: http://nongnu.org/txr Cygnal: Cygwin Native Application Library: http://kylheku.com/cygnal Mastodon: @Kazinator@mstdn.ca
[toc] | [prev] | [next] | [standalone]
| From | olcott <NoOne@NoWhere.com> |
|---|---|
| Date | 2025-11-24 17:23 -0600 |
| Subject | Re: DD simulated by HHH and DD simulated by HHH1 |
| Message-ID | <9fOcnfvm1-hGdbn0nZ2dnZfqlJ-dnZ2d@giganews.com> |
| In reply to | #136362 |
On 11/24/2025 4:45 PM, Kaz Kylheku wrote:
> On 2025-11-24, olcott <polcott333@gmail.com> wrote:
>> As long as you keep lying I will keep repeating it.
>
> To lie is to knowing post something that is false.
>
> But if you do that about an objectively verifiable fact that has nothing
> to do with yourself, but some scientific matter, nobody in their right
> mind will see you as a liar.
>
> Rather than see you as a liar, they will just assume you are ignorant
> and incompetent.
>
> What makes you think I, or Mike, or anyone here would write something I
> know to be false, which would be interpreted as ignorant, rather than
> dishonest?
>
> Maybe you don't understand that nobody would do that, since
> you have no problem being casually wrong yourself.
>
The people on comp.lang.c or comp.lang.c++
can always speak up.
typedef int (*ptr)();
int HHH(ptr P);
int HHH1(ptr P);
int DD()
{
int Halt_Status = HHH(DD);
if (Halt_Status)
HERE: goto HERE;
return Halt_Status;
}
int main()
{
HHH(DD);
HHH1(DD);
}
HHH simulates DD that calls HHH(DD)
that simulates DD that calls HHH(DD)...
that never stops running until aborted
HHH1 simulates DD that calls HHH(DD) that
returns to DD that returns to HHH1.
--
Copyright 2025 Olcott
My 28 year goal has been to make
"true on the basis of meaning" computable.
[toc] | [prev] | [next] | [standalone]
| From | Richard Heathfield <rjh@cpax.org.uk> |
|---|---|
| Date | 2025-11-25 05:10 +0000 |
| Subject | Re: DD simulated by HHH and DD simulated by HHH1 |
| Message-ID | <10g3dne$3462a$1@dont-email.me> |
| In reply to | #136365 |
[Follow-ups set]
On 24/11/2025 23:23, olcott wrote:
> On 11/24/2025 4:45 PM, Kaz Kylheku wrote:
>> On 2025-11-24, olcott <polcott333@gmail.com> wrote:
>>> As long as you keep lying I will keep repeating it.
>>
>> To lie is to knowing post something that is false.
>>
>> But if you do that about an objectively verifiable fact
>> that has nothing to do with yourself, but some scientific
>> matter, nobody in their right mind will see you as a liar.
>>
>> Rather than see you as a liar, they will just assume you
>> are ignorant and incompetent.
>>
>> What makes you think I, or Mike, or anyone here would
>> write something I know to be false, which would be
>> interpreted as ignorant, rather than dishonest?
>>
>> Maybe you don't understand that nobody would do that, since
>> you have no problem being casually wrong yourself.
>>
>
> The people on comp.lang.c or comp.lang.c++ can always speak
> up.
They have done so, many times. They have told you many times that
you are wrong. You don't care, of course.
>
> typedef int (*ptr)(); int HHH(ptr P); int HHH1(ptr P);
>
> int DD() { int Halt_Status = HHH(DD); if (Halt_Status) HERE:
> goto HERE; return Halt_Status; }
>
> int main() { HHH(DD); HHH1(DD); }
>
> HHH simulates DD
The rules of C offer no mechanism for HHH to be able to simulate
any C function using nothing but a function pointer. The closest
you can get is to dereference it, but you don't do that. Your
'simulation' doesn't simulate any part of DD past the call in its
first line, and you can only do that because of a
platform-specific hack that breaks the rules of C.
You have been told this many times, but you're not interested in
truth or competence., so (as Kaz rightly said) we all have to
assume that you are ignorant and incompetent.
Followups set to comp.theory only, because nobody has anything to
gain from your cross-posting to language experts whose expert
opinions you invariably ignore.
--
Richard Heathfield
Email: rjh at cpax dot org dot uk
"Usenet is a strange place" - dmr 29 July 1999
Sig line 4 vacant - apply within
[toc] | [prev] | [next] | [standalone]
| From | olcott <polcott333@gmail.com> |
|---|---|
| Date | 2025-11-24 23:25 -0600 |
| Subject | Re: DD simulated by HHH and DD simulated by HHH1 |
| Message-ID | <10g3ek2$34ohi$1@dont-email.me> |
| In reply to | #136389 |
On 11/24/2025 11:10 PM, Richard Heathfield wrote:
>
> [Follow-ups set]
>
> On 24/11/2025 23:23, olcott wrote:
>> On 11/24/2025 4:45 PM, Kaz Kylheku wrote:
>>> On 2025-11-24, olcott <polcott333@gmail.com> wrote:
>>>> As long as you keep lying I will keep repeating it.
>>>
>>> To lie is to knowing post something that is false.
>>>
>>> But if you do that about an objectively verifiable fact
>>> that has nothing to do with yourself, but some scientific
>>> matter, nobody in their right mind will see you as a liar.
>>>
>>> Rather than see you as a liar, they will just assume you
>>> are ignorant and incompetent.
>>>
>>> What makes you think I, or Mike, or anyone here would
>>> write something I know to be false, which would be
>>> interpreted as ignorant, rather than dishonest?
>>>
>>> Maybe you don't understand that nobody would do that, since you have
>>> no problem being casually wrong yourself.
>>>
>>
>> The people on comp.lang.c or comp.lang.c++ can always speak
>> up.
>
> They have done so, many times. They have told you many times that
> you are wrong. You don't care, of course.
>
Time and date stamp any time anyone
from comp.lang.c that ever said that
actually made a specific programming error.
>>
>> typedef int (*ptr)(); int HHH(ptr P); int HHH1(ptr P);
>>
>> int DD() { int Halt_Status = HHH(DD); if (Halt_Status) HERE:
>> goto HERE; return Halt_Status; }
>>
>> int main() { HHH(DD); HHH1(DD); }
>>
>> HHH simulates DD
>
> The rules of C offer no mechanism for HHH to be able to simulate any C
> function using nothing but a function pointer.
I do this at the x86 level thus equivalent to the
C level.
> The closest you can get
> is to dereference it, but you don't do that. Your 'simulation' doesn't
> simulate any part of DD past the call in its first line, and you can
> only do that because of a platform-specific hack that breaks the rules
> of C.
>
The x86 code can and does pass machine addresses
after I am done with the construction on my house
I plan on rewriting this using a C interpreter.
> You have been told this many times, but you're not interested in truth
> or competence., so (as Kaz rightly said) we all have to assume that you
> are ignorant and incompetent.
>
I have been told counter-factually that I
an wrong many times. It is a matter of
verified fact that
HHH simulates DD that calls HHH(DD)
that simulates DD that calls HHH(DD)...
that never stops running until aborted
HHH1 simulates DD that calls HHH(DD) that
returns to DD that returns to HHH1.
(when HHH(DD) sees the repeating pattern)
The dumbest person here should have gotten
that three years ago.
Only one person ever got that and he did get
that three years ago.
On 10/14/2022 7:44 PM, Ben Bacarisse wrote:
> 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.
> Followups set to comp.theory only, because nobody has anything to gain
> from your cross-posting to language experts whose expert opinions you
> invariably ignore.
>
--
Copyright 2025 Olcott
My 28 year goal has been to make
"true on the basis of meaning" computable.
[toc] | [prev] | [next] | [standalone]
| From | Richard Damon <Richard@Damon-Family.org> |
|---|---|
| Date | 2025-11-25 10:34 -0500 |
| Subject | Re: DD simulated by HHH and DD simulated by HHH1 |
| Message-ID | <g0kVQ.39951$C8i7.20486@fx16.iad> |
| In reply to | #136390 |
On 11/25/25 12:25 AM, olcott wrote:
> On 11/24/2025 11:10 PM, Richard Heathfield wrote:
>>
>> [Follow-ups set]
>>
>> On 24/11/2025 23:23, olcott wrote:
>>> On 11/24/2025 4:45 PM, Kaz Kylheku wrote:
>>>> On 2025-11-24, olcott <polcott333@gmail.com> wrote:
>>>>> As long as you keep lying I will keep repeating it.
>>>>
>>>> To lie is to knowing post something that is false.
>>>>
>>>> But if you do that about an objectively verifiable fact
>>>> that has nothing to do with yourself, but some scientific
>>>> matter, nobody in their right mind will see you as a liar.
>>>>
>>>> Rather than see you as a liar, they will just assume you
>>>> are ignorant and incompetent.
>>>>
>>>> What makes you think I, or Mike, or anyone here would
>>>> write something I know to be false, which would be
>>>> interpreted as ignorant, rather than dishonest?
>>>>
>>>> Maybe you don't understand that nobody would do that, since you have
>>>> no problem being casually wrong yourself.
>>>>
>>>
>>> The people on comp.lang.c or comp.lang.c++ can always speak
>>> up.
>>
>> They have done so, many times. They have told you many times that
>> you are wrong. You don't care, of course.
>>
>
> Time and date stamp any time anyone
> from comp.lang.c that ever said that
> actually made a specific programming error.
I guess words don't mean anything to you, as that isn't the claim.
Your program does (sort of) what you claim it does, it partially
simulates the input until it matchs a specified pattern.
But it doesn't prove your ultimate claim, as that pattern doesn't
indicate what you claim. and partial simulation isn't what the question
is about.
>
>>>
>>> typedef int (*ptr)(); int HHH(ptr P); int HHH1(ptr P);
>>>
>>> int DD() { int Halt_Status = HHH(DD); if (Halt_Status) HERE:
>>> goto HERE; return Halt_Status; }
>>>
>>> int main() { HHH(DD); HHH1(DD); }
>>>
>>> HHH simulates DD
>>
>> The rules of C offer no mechanism for HHH to be able to simulate any C
>> function using nothing but a function pointer.
>
> I do this at the x86 level thus equivalent to the
> C level.
>
NO, you don't. because you don't correctly simulate the CALL
instruction, at least not to the output that you claim shows your proof.
>> The closest you can get is to dereference it, but you don't do that.
>> Your 'simulation' doesn't simulate any part of DD past the call in its
>> first line, and you can only do that because of a platform-specific
>> hack that breaks the rules of C.
>>
>
> The x86 code can and does pass machine addresses
> after I am done with the construction on my house
> I plan on rewriting this using a C interpreter.
But if the "address" is the sum of the "input", then the program isn't
ALLOWED to look at that memory and be a computation.
If you consider the input to be that memory, you don't get to change ANY
of it, and thus can't change the code of H, since it is part of the
memory you look at.
Sorry, all you are doing is prove you are ignorant of what you are
talking about.
A fact you ADMIT, as you have noted you haven't actually studied any of
the theory, just read the problem and the summary of the proof.
Your deductions are made based on ignorant assumptions of what things
are supposed to mean, and a deliberate refusal to learn, possible
becuase you are just incabable.
>
>> You have been told this many times, but you're not interested in truth
>> or competence., so (as Kaz rightly said) we all have to assume that
>> you are ignorant and incompetent.
>>
>
> I have been told counter-factually that I
> an wrong many times. It is a matter of
> verified fact that
No, you have been told FACTUALLY that you are wrong, but you insist on
keeping to your own lies that are not based on actual facts.
>
> HHH simulates DD that calls HHH(DD)
> that simulates DD that calls HHH(DD)...
> that never stops running until aborted
So? Since a given HHH either aborts or it doesn't, and the DD built on
an aborting HHH will eventually halt, means you logic is based on lies
and false premises.
The "meaning" of Halting, isn't based on partial simulations, or looking
at non-programs, but on the behavior of the actual execution of
programs, which can also be determined by COMPLETE simulation of said
program.
>
> HHH1 simulates DD that calls HHH(DD) that
> returns to DD that returns to HHH1.
> (when HHH(DD) sees the repeating pattern)
Whhich shows that HHH was WRONG to abort, as the complete simulation of
its input will halt.
>
> The dumbest person here should have gotten
> that three years ago.
Yes, YOU should have understood that a long time ago.
Your problem is you refuse to learn what the word you use mean, because
it would force you to see that you are just a stupid liar.
>
> Only one person ever got that and he did get
> that three years ago.
>
> On 10/14/2022 7:44 PM, Ben Bacarisse wrote:
> > 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.
For which you don't understand what Ben meant, as even he has pointed out,
>
>
>> Followups set to comp.theory only, because nobody has anything to gain
>> from your cross-posting to language experts whose expert opinions you
>> invariably ignore.
>>
>
>
So, all you are doing is PROVING that you are nothing but a pathological
idiotic liar that doesn't understand even the fundamental basics of how
logic works.
[toc] | [prev] | [next] | [standalone]
| From | Richard Heathfield <rjh@cpax.org.uk> |
|---|---|
| Date | 2025-11-26 05:43 +0000 |
| Subject | Re: DD simulated by HHH and DD simulated by HHH1 |
| Message-ID | <10g641f$3uok$1@dont-email.me> |
| In reply to | #136397 |
On 25/11/2025 15:34, Richard Damon wrote: > On 11/25/25 12:25 AM, olcott wrote: >> On 11/24/2025 11:10 PM, Richard Heathfield wrote: >>> >>> [Follow-ups set] >>> >>> On 24/11/2025 23:23, olcott wrote: <snip> >>>> The people on comp.lang.c or comp.lang.c++ can always >>>> speak up. >>> >>> They have done so, many times. They have told you many >>> times that you are wrong. You don't care, of course. >>> >> >> Time and date stamp any time anyone from comp.lang.c that >> ever said that actually made a specific programming error. Ah, a nymshyfter. Still, since we're here, the following was plucked at random from dozens of examples of articles pointing out problems in your C: Date: Thu, 8 May 2025 05:09:07 +0100 which shows a syntax error and a null pointer deref. Unless someone replies to it as here, I won't see any reply of yours because after briefly nymshifting to gain some visibility you've reverted to posting from an account in my killfile. -- Richard Heathfield Email: rjh at cpax dot org dot uk "Usenet is a strange place" - dmr 29 July 1999 Sig line 4 vacant - apply within
[toc] | [prev] | [next] | [standalone]
| From | olcott <polcott333@gmail.com> |
|---|---|
| Date | 2025-11-25 23:51 -0600 |
| Subject | Re: DD simulated by HHH and DD simulated by HHH1 |
| Message-ID | <10g64g8$40vq$1@dont-email.me> |
| In reply to | #136556 |
On 11/25/2025 11:43 PM, Richard Heathfield wrote: > On 25/11/2025 15:34, Richard Damon wrote: >> On 11/25/25 12:25 AM, olcott wrote: >>> On 11/24/2025 11:10 PM, Richard Heathfield wrote: >>>> >>>> [Follow-ups set] >>>> >>>> On 24/11/2025 23:23, olcott wrote: > > <snip> > >>>>> The people on comp.lang.c or comp.lang.c++ can always >>>>> speak up. >>>> >>>> They have done so, many times. They have told you many >>>> times that you are wrong. You don't care, of course. >>>> >>> >>> Time and date stamp any time anyone from comp.lang.c that >>> ever said that actually made a specific programming error. > > Ah, a nymshyfter. > > Still, since we're here, the following was plucked at random from dozens > of examples of articles pointing out problems in your C: > > Date: Thu, 8 May 2025 05:09:07 +0100 > > which shows a syntax error and a null pointer deref. > You already had you false assumption corrected on that. You have to go all the way back six months to find one mistaken assessment of error? > Unless someone replies to it as here, I won't see any reply of yours > because after briefly nymshifting to gain some visibility you've > reverted to posting from an account in my killfile. > -- Copyright 2025 Olcott My 28 year goal has been to make "true on the basis of meaning" computable. This required establishing a new foundation for correct reasoning.
[toc] | [prev] | [next] | [standalone]
| From | Richard Damon <Richard@Damon-Family.org> |
|---|---|
| Date | 2025-11-26 07:21 -0500 |
| Subject | Re: DD simulated by HHH and DD simulated by HHH1 |
| Message-ID | <6hCVQ.51182$liu8.47982@fx17.iad> |
| In reply to | #136557 |
On 11/26/25 12:51 AM, olcott wrote: > On 11/25/2025 11:43 PM, Richard Heathfield wrote: >> On 25/11/2025 15:34, Richard Damon wrote: >>> On 11/25/25 12:25 AM, olcott wrote: >>>> On 11/24/2025 11:10 PM, Richard Heathfield wrote: >>>>> >>>>> [Follow-ups set] >>>>> >>>>> On 24/11/2025 23:23, olcott wrote: >> >> <snip> >> >>>>>> The people on comp.lang.c or comp.lang.c++ can always >>>>>> speak up. >>>>> >>>>> They have done so, many times. They have told you many >>>>> times that you are wrong. You don't care, of course. >>>>> >>>> >>>> Time and date stamp any time anyone from comp.lang.c that >>>> ever said that actually made a specific programming error. >> >> Ah, a nymshyfter. >> >> Still, since we're here, the following was plucked at random from >> dozens of examples of articles pointing out problems in your C: >> >> Date: Thu, 8 May 2025 05:09:07 +0100 >> >> which shows a syntax error and a null pointer deref. >> > > You already had you false assumption corrected on that. > You have to go all the way back six months to find one > mistaken assessment of error? So NONE doesn't mean NONE? Just like to you Halting doesn't mean Halting? or a Computable Function isn't actually what mathematics defines as a Computable Function. Your program, by the C Standard, has undefined behavior as it looks at memory that hasn't been initialized, relying on an assumption of implementation defined behavior. You have agreed that a decider needs to act as if it was a pure function, but your H changes behavior (and not just in logging) based on if it is the outer invocation or a nested one, and thus YOU have admitted that you claim that H is a decider is just a lie. The fact you won't accept the correct analysis of the behavior of your own program just shows how much of a liar you are. YOU, have had your lies corrected, but continue with them, just making you a flat out stupid liar. > >> Unless someone replies to it as here, I won't see any reply of yours >> because after briefly nymshifting to gain some visibility you've >> reverted to posting from an account in my killfile. >> > >
[toc] | [prev] | [next] | [standalone]
| From | Richard Heathfield <rjh@cpax.org.uk> |
|---|---|
| Date | 2025-11-26 17:37 +0000 |
| Subject | Re: DD simulated by HHH and DD simulated by HHH1 |
| Message-ID | <10g7dsa$jtm9$1@dont-email.me> |
| In reply to | #136565 |
On 26/11/2025 12:21, Richard Damon wrote: > On 11/26/25 12:51 AM, olcott wrote: >> On 11/25/2025 11:43 PM, Richard Heathfield wrote: >>> On 25/11/2025 15:34, Richard Damon wrote: >>>> On 11/25/25 12:25 AM, olcott wrote: >>>>> On 11/24/2025 11:10 PM, Richard Heathfield wrote: >>>>>> >>>>>> [Follow-ups set] >>>>>> >>>>>> On 24/11/2025 23:23, olcott wrote: >>> >>> <snip> >>> >>>>>>> The people on comp.lang.c or comp.lang.c++ can always >>>>>>> speak up. >>>>>> >>>>>> They have done so, many times. They have told you many >>>>>> times that you are wrong. You don't care, of course. >>>>>> >>>>> >>>>> Time and date stamp any time anyone from comp.lang.c that >>>>> ever said that actually made a specific programming error. >>> >>> Ah, a nymshyfter. >>> >>> Still, since we're here, the following was plucked at random >>> from dozens of examples of articles pointing out problems in >>> your C: >>> >>> Date: Thu, 8 May 2025 05:09:07 +0100 >>> >>> which shows a syntax error and a null pointer deref. >>> >> >> You already had you false assumption corrected on that. No false assumption. In each case I can give C&V from ISO. >> You have to go all the way back six months to find one >> mistaken assessment of error? > > So NONE doesn't mean NONE? Of course not. And neither did I have to go that far back. But when I look through a list, I naturally start at the beginning --- ie when I first started posting here. That was the first example that caught my eye. Contrary to Olcott's claim, I have posted *dozens* of articles pointing out specific programming errors he has made. Olcott doesn't like criticism, though, so he likes to ignore my articles and pretend they never happened. -- Richard Heathfield Email: rjh at cpax dot org dot uk "Usenet is a strange place" - dmr 29 July 1999 Sig line 4 vacant - apply within
[toc] | [prev] | [next] | [standalone]
| From | Richard Damon <Richard@Damon-Family.org> |
|---|---|
| Date | 2025-11-26 12:52 -0500 |
| Subject | Re: DD simulated by HHH and DD simulated by HHH1 |
| Message-ID | <L7HVQ.49150$r_jb.3596@fx11.iad> |
| In reply to | #136589 |
On 11/26/25 12:37 PM, Richard Heathfield wrote: > On 26/11/2025 12:21, Richard Damon wrote: >> On 11/26/25 12:51 AM, olcott wrote: >>> On 11/25/2025 11:43 PM, Richard Heathfield wrote: >>>> On 25/11/2025 15:34, Richard Damon wrote: >>>>> On 11/25/25 12:25 AM, olcott wrote: >>>>>> On 11/24/2025 11:10 PM, Richard Heathfield wrote: >>>>>>> >>>>>>> [Follow-ups set] >>>>>>> >>>>>>> On 24/11/2025 23:23, olcott wrote: >>>> >>>> <snip> >>>> >>>>>>>> The people on comp.lang.c or comp.lang.c++ can always >>>>>>>> speak up. >>>>>>> >>>>>>> They have done so, many times. They have told you many >>>>>>> times that you are wrong. You don't care, of course. >>>>>>> >>>>>> >>>>>> Time and date stamp any time anyone from comp.lang.c that >>>>>> ever said that actually made a specific programming error. >>>> >>>> Ah, a nymshyfter. >>>> >>>> Still, since we're here, the following was plucked at random from >>>> dozens of examples of articles pointing out problems in your C: >>>> >>>> Date: Thu, 8 May 2025 05:09:07 +0100 >>>> >>>> which shows a syntax error and a null pointer deref. >>>> >>> >>> You already had you false assumption corrected on that. > > No false assumption. In each case I can give C&V from ISO. > >>> You have to go all the way back six months to find one >>> mistaken assessment of error? >> >> So NONE doesn't mean NONE? > > Of course not. And neither did I have to go that far back. But when I > look through a list, I naturally start at the beginning --- ie when I > first started posting here. That was the first example that caught my eye. > > Contrary to Olcott's claim, I have posted *dozens* of articles pointing > out specific programming errors he has made. Olcott doesn't like > criticism, though, so he likes to ignore my articles and pretend they > never happened. > You seem to have messed up the reply. I agree that Olcott is wrong in his statement, and your examples prove it. His problem is that he doesn't use words to mean what they mean. When He says no one has pointed out an error, he means no one has convinced him that he is wrong, becuase he just categorically refused to admit that, because he is just too wrong.
[toc] | [prev] | [next] | [standalone]
| From | Richard Heathfield <rjh@cpax.org.uk> |
|---|---|
| Date | 2025-11-26 17:59 +0000 |
| Subject | Re: DD simulated by HHH and DD simulated by HHH1 |
| Message-ID | <10g7f6r$jtm9$3@dont-email.me> |
| In reply to | #136592 |
On 26/11/2025 17:52, Richard Damon wrote: > On 11/26/25 12:37 PM, Richard Heathfield wrote [in reply to] >> On 26/11/2025 12:21, Richard Damon wrote: <snip> >> >> Contrary to Olcott's claim, I have posted *dozens* of articles >> pointing out specific programming errors he has made. Olcott >> doesn't like criticism, though, so he likes to ignore my >> articles and pretend they never happened. >> > > You seem to have messed up the reply. I was piggybacking on your reply, that's all. Sorry about that, but Olcott's originals no longer reach my in-box except when he nymshyfts. -- Richard Heathfield Email: rjh at cpax dot org dot uk "Usenet is a strange place" - dmr 29 July 1999 Sig line 4 vacant - apply within
[toc] | [prev] | [next] | [standalone]
| From | olcott <polcott333@gmail.com> |
|---|---|
| Date | 2025-11-26 12:32 -0600 |
| Subject | Re: DD simulated by HHH and DD simulated by HHH1 |
| Message-ID | <10g7h43$le5s$2@dont-email.me> |
| In reply to | #136593 |
On 11/26/2025 11:59 AM, Richard Heathfield wrote: > On 26/11/2025 17:52, Richard Damon wrote: >> On 11/26/25 12:37 PM, Richard Heathfield wrote [in reply to] >>> On 26/11/2025 12:21, Richard Damon wrote: > > <snip> > >>> >>> Contrary to Olcott's claim, I have posted *dozens* of articles >>> pointing out specific programming errors he has made. Olcott doesn't >>> like criticism, though, so he likes to ignore my articles and pretend >>> they never happened. >>> >> >> You seem to have messed up the reply. > > I was piggybacking on your reply, that's all. Sorry about that, but > Olcott's originals no longer reach my in-box except when he nymshyfts. > news.solani.org goes back 2 years and it is free -- Copyright 2025 Olcott My 28 year goal has been to make "true on the basis of meaning" computable. This required establishing a new foundation for correct reasoning.
[toc] | [prev] | [next] | [standalone]
| From | olcott <polcott333@gmail.com> |
|---|---|
| Date | 2025-11-26 12:28 -0600 |
| Subject | Re: DD simulated by HHH and DD simulated by HHH1 |
| Message-ID | <10g7grk$le5s$1@dont-email.me> |
| In reply to | #136589 |
On 11/26/2025 11:37 AM, Richard Heathfield wrote:
> On 26/11/2025 12:21, Richard Damon wrote:
>> On 11/26/25 12:51 AM, olcott wrote:
>>> On 11/25/2025 11:43 PM, Richard Heathfield wrote:
>>>> On 25/11/2025 15:34, Richard Damon wrote:
>>>>> On 11/25/25 12:25 AM, olcott wrote:
>>>>>> On 11/24/2025 11:10 PM, Richard Heathfield wrote:
>>>>>>>
>>>>>>> [Follow-ups set]
>>>>>>>
>>>>>>> On 24/11/2025 23:23, olcott wrote:
>>>>
>>>> <snip>
>>>>
>>>>>>>> The people on comp.lang.c or comp.lang.c++ can always
>>>>>>>> speak up.
>>>>>>>
>>>>>>> They have done so, many times. They have told you many
>>>>>>> times that you are wrong. You don't care, of course.
>>>>>>>
>>>>>>
>>>>>> Time and date stamp any time anyone from comp.lang.c that
>>>>>> ever said that actually made a specific programming error.
>>>>
>>>> Ah, a nymshyfter.
>>>>
>>>> Still, since we're here, the following was plucked at random from
>>>> dozens of examples of articles pointing out problems in your C:
>>>>
>>>> Date: Thu, 8 May 2025 05:09:07 +0100
>>>>
>>>> which shows a syntax error and a null pointer deref.
>>>>
>>>
>>> You already had you false assumption corrected on that.
>
> No false assumption. In each case I can give C&V from ISO.
>
https://github.com/plolcott/x86utm/blob/master/Halt7.c
// Empty Stub Functions of Virtual Machine Instructions
// x86utm operating system calls
void OutputString(char* S) {}
void Output(char* S, u32 N) {}
u32* Allocate(u32 size) { return 0; }
void SaveState(Registers* state) {}
void LoadState(Registers* state) {}
u32 DebugStep(Registers* master_state,
Registers* slave_state, Decoded_Line_Of_Code* decoded)
{ return 0; }
void PushBack(u32 stdvector, u32 data_ptr, u32 size_in_bytes) {}
u32 StackPush(u32* S, u32 M) { return 0; }
u32 get_code_end(u32 EIP){ return 0; }
u32 Last_Address_Of_Operating_System(){ return 0; }; // 2021-08-26
void Output_Decoded(u32 decoded){};
// Empty Stub Functions of Virtual Machine Instructions
// x86utm operating system calls
// Empty Stub Functions of Virtual Machine Instructions
// x86utm operating system calls
// Empty Stub Functions of Virtual Machine Instructions
// x86utm operating system calls
// Empty Stub Functions of Virtual Machine Instructions
// x86utm operating system calls
// Empty Stub Functions of Virtual Machine Instructions
// x86utm operating system calls
// Empty Stub Functions of Virtual Machine Instructions
// x86utm operating system calls
// Empty Stub Functions of Virtual Machine Instructions
// x86utm operating system calls
Repeated so that people having a very hard time
paying attention will notice.
>>> You have to go all the way back six months to find one
>>> mistaken assessment of error?
>>
>> So NONE doesn't mean NONE?
>
> Of course not. And neither did I have to go that far back. But when I
> look through a list, I naturally start at the beginning --- ie when I
> first started posting here. That was the first example that caught my eye.
>
I have not made any mistake in the essence of
what I am been saying for 20 years. I did
make numerous typographical errors.
> Contrary to Olcott's claim, I have posted *dozens* of articles pointing
> out specific programming errors he has made. Olcott doesn't like
> criticism, though, so he likes to ignore my articles and pretend they
> never happened.
>
I already asked you to give me the time and
date stamp of one and you failed to do even
that.
--
Copyright 2025 Olcott
My 28 year goal has been to make
"true on the basis of meaning" computable.
This required establishing a new foundation
for correct reasoning.
[toc] | [prev] | [next] | [standalone]
| From | "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> |
|---|---|
| Date | 2025-11-25 12:45 -0800 |
| Subject | Re: DD simulated by HHH and DD simulated by HHH1 |
| Message-ID | <10g54hl$3ol6f$2@dont-email.me> |
| In reply to | #136390 |
On 11/24/2025 9:25 PM, olcott wrote:
> On 11/24/2025 11:10 PM, Richard Heathfield wrote:
>>
>> [Follow-ups set]
>>
>> On 24/11/2025 23:23, olcott wrote:
>>> On 11/24/2025 4:45 PM, Kaz Kylheku wrote:
>>>> On 2025-11-24, olcott <polcott333@gmail.com> wrote:
>>>>> As long as you keep lying I will keep repeating it.
>>>>
>>>> To lie is to knowing post something that is false.
>>>>
>>>> But if you do that about an objectively verifiable fact
>>>> that has nothing to do with yourself, but some scientific
>>>> matter, nobody in their right mind will see you as a liar.
>>>>
>>>> Rather than see you as a liar, they will just assume you
>>>> are ignorant and incompetent.
>>>>
>>>> What makes you think I, or Mike, or anyone here would
>>>> write something I know to be false, which would be
>>>> interpreted as ignorant, rather than dishonest?
>>>>
>>>> Maybe you don't understand that nobody would do that, since you have
>>>> no problem being casually wrong yourself.
>>>>
>>>
>>> The people on comp.lang.c or comp.lang.c++ can always speak
>>> up.
>>
>> They have done so, many times. They have told you many times that
>> you are wrong. You don't care, of course.
>>
>
> Time and date stamp any time anyone
> from comp.lang.c that ever said that
> actually made a specific programming error.
>
>>>
>>> typedef int (*ptr)(); int HHH(ptr P); int HHH1(ptr P);
>>>
>>> int DD() { int Halt_Status = HHH(DD); if (Halt_Status) HERE:
>>> goto HERE; return Halt_Status; }
>>>
>>> int main() { HHH(DD); HHH1(DD); }
>>>
>>> HHH simulates DD
>>
>> The rules of C offer no mechanism for HHH to be able to simulate any C
>> function using nothing but a function pointer.
>
> I do this at the x86 level thus equivalent to the
> C level.
>
>> The closest you can get is to dereference it, but you don't do that.
>> Your 'simulation' doesn't simulate any part of DD past the call in its
>> first line, and you can only do that because of a platform-specific
>> hack that breaks the rules of C.
>>
>
> The x86 code can and does pass machine addresses
> after I am done with the construction on my house
> I plan on rewriting this using a C interpreter.
>
>> You have been told this many times, but you're not interested in truth
>> or competence., so (as Kaz rightly said) we all have to assume that
>> you are ignorant and incompetent.
>>
>
> I have been told counter-factually that I
> an wrong many times. It is a matter of
> verified fact that
>
> HHH simulates DD that calls HHH(DD)
> that simulates DD that calls HHH(DD)...
> that never stops running until aborted
>
> HHH1 simulates DD that calls HHH(DD) that
> returns to DD that returns to HHH1.
> (when HHH(DD) sees the repeating pattern)
>
> The dumbest person here should have gotten
> that three years ago.
>
> Only one person ever got that and he did get
> that three years ago.
>
> On 10/14/2022 7:44 PM, Ben Bacarisse wrote:
> > 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.
I still don't think you know how to properly read and actually
_understand_ what Ben wrote.
>
>
>> Followups set to comp.theory only, because nobody has anything to gain
>> from your cross-posting to language experts whose expert opinions you
>> invariably ignore.
>>
>
>
[toc] | [prev] | [next] | [standalone]
Page 18 of 32 — ← Prev page 1 … 16 17 [18] 19 20 … 32 Next page →
Back to top | Article view | comp.theory
csiph-web