Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.theory > #134369 > unrolled thread

Semantic properties of finite string inputs

Started byolcott <polcott333@gmail.com>
First post2025-10-30 09:49 -0500
Last post2025-11-01 12:42 -0700
Articles 20 on this page of 293 — 15 participants

Back to article view | Back to comp.theory


Contents

  Semantic properties of finite string inputs olcott <polcott333@gmail.com> - 2025-10-30 09:49 -0500
    Re: Semantic properties of finite string inputs Kaz Kylheku <643-408-1753@kylheku.com> - 2025-10-30 20:11 +0000
      Re: Semantic properties of finite string inputs olcott <polcott333@gmail.com> - 2025-10-30 15:25 -0500
        Re: Semantic properties of finite string inputs Kaz Kylheku <643-408-1753@kylheku.com> - 2025-10-30 20:42 +0000
          Re: Semantic properties of finite string inputs olcott <polcott333@gmail.com> - 2025-10-30 16:05 -0500
            Re: Semantic properties of finite string inputs Kaz Kylheku <643-408-1753@kylheku.com> - 2025-10-30 21:15 +0000
              Re: Semantic properties of finite string inputs olcott <polcott333@gmail.com> - 2025-10-30 16:49 -0500
                Re: Semantic properties of finite string inputs dbush <dbush.mobile@gmail.com> - 2025-10-30 20:13 -0400
                  Re: Semantic properties of finite string inputs --- Mike never did get this olcott <polcott333@gmail.com> - 2025-10-30 21:14 -0500
                    Re: Semantic properties of finite string inputs --- Mike never did get this "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2025-10-30 19:15 -0700
                    Re: Semantic properties of finite string inputs --- Mike never did get this dbush <dbush.mobile@gmail.com> - 2025-10-30 22:33 -0400
                      Re: Semantic properties of finite string inputs --- Mike never did get this olcott <polcott333@gmail.com> - 2025-10-30 21:45 -0500
                        Re: Semantic properties of finite string inputs --- Mike never did get this dbush <dbush.mobile@gmail.com> - 2025-10-30 22:49 -0400
                          Re: Semantic properties of finite string inputs --- Mike never did get this olcott <polcott333@gmail.com> - 2025-10-30 21:54 -0500
                            Re: Semantic properties of finite string inputs --- Mike never did get this dbush <dbush.mobile@gmail.com> - 2025-10-30 22:56 -0400
                              Re: Semantic properties of finite string inputs --- Mike never did get this olcott <polcott333@gmail.com> - 2025-10-30 21:59 -0500
                                Re: Semantic properties of finite string inputs --- Mike never did get this dbush <dbush.mobile@gmail.com> - 2025-10-30 23:00 -0400
                                  Re: Semantic properties of finite string inputs --- Mike never did get this olcott <polcott333@gmail.com> - 2025-10-30 22:03 -0500
                                    Re: Semantic properties of finite string inputs --- Mike never did get this dbush <dbush.mobile@gmail.com> - 2025-10-30 23:04 -0400
                                      Re: Semantic properties of finite string inputs --- Mike never did get this olcott <polcott333@gmail.com> - 2025-10-30 22:15 -0500
                                        Re: Semantic properties of finite string inputs --- Mike never did get this dbush <dbush.mobile@gmail.com> - 2025-10-30 23:19 -0400
                                          Re: Semantic properties of finite string inputs --- Mike never did get this olcott <polcott333@gmail.com> - 2025-10-30 22:25 -0500
                                            Re: Semantic properties of finite string inputs --- Mike never did get this dbush <dbush.mobile@gmail.com> - 2025-10-30 23:28 -0400
                                              Re: Semantic properties of finite string inputs --- Mike never did get this olcott <polcott333@gmail.com> - 2025-10-30 22:49 -0500
                                                Re: Semantic properties of finite string inputs --- Mike never did get this dbush <dbush.mobile@gmail.com> - 2025-10-31 00:00 -0400
                                                  Re: Semantic properties of finite string inputs --- Mike never did get this olcott <polcott333@gmail.com> - 2025-10-30 23:06 -0500
                                                    Re: Semantic properties of finite string inputs --- Mike never did get this dbush <dbush.mobile@gmail.com> - 2025-10-31 07:22 -0400
                                                      Re: Semantic properties of finite string inputs --- Mike never did get this olcott <polcott333@gmail.com> - 2025-10-31 06:55 -0500
                                                        Re: Semantic properties of finite string inputs --- Mike never did get this dbush <dbush.mobile@gmail.com> - 2025-10-31 08:08 -0400
                                                          Re: Semantic properties of finite string inputs --- Mike never did get this olcott <polcott333@gmail.com> - 2025-10-31 07:30 -0500
                                                            Re: Semantic properties of finite string inputs --- Mike never did get this dbush <dbush.mobile@gmail.com> - 2025-10-31 08:33 -0400
                                                              Re: Semantic properties of finite string inputs --- Mike never did get this olcott <polcott333@gmail.com> - 2025-10-31 09:02 -0500
                                                                Re: Semantic properties of finite string inputs --- Mike never did get this dbush <dbush.mobile@gmail.com> - 2025-10-31 10:15 -0400
                                                                  Re: Semantic properties of finite string inputs --- Mike never did get this olcott <polcott333@gmail.com> - 2025-10-31 09:24 -0500
                                                                    Re: Semantic properties of finite string inputs --- Mike never did get this dbush <dbush.mobile@gmail.com> - 2025-10-31 10:28 -0400
                                                            Re: Semantic properties of finite string inputs --- Mike never did get this "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2025-10-31 12:36 -0700
                                                  Re: Semantic properties of finite string inputs --- Mike never did get this "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2025-10-31 12:35 -0700
                                            Re: Semantic properties of finite string inputs --- Mike never did get this Kaz Kylheku <643-408-1753@kylheku.com> - 2025-10-31 04:55 +0000
                                              Re: Semantic properties of finite string inputs --- Mike never did get this olcott <polcott333@gmail.com> - 2025-10-31 06:57 -0500
                                                Re: Semantic properties of finite string inputs --- Mike never did get this Kaz Kylheku <643-408-1753@kylheku.com> - 2025-10-31 17:17 +0000
                                                Re: Semantic properties of finite string inputs --- Mike never did get this Kaz Kylheku <643-408-1753@kylheku.com> - 2025-10-31 17:20 +0000
                                            Re: Semantic properties of finite string inputs --- Mike never did get this "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2025-10-31 12:32 -0700
                Re: Semantic properties of finite string inputs Kaz Kylheku <643-408-1753@kylheku.com> - 2025-10-31 00:22 +0000
                  Re: Semantic properties of finite string inputs olcott <polcott333@gmail.com> - 2025-10-30 21:07 -0500
                    Re: Semantic properties of finite string inputs dbush <dbush.mobile@gmail.com> - 2025-10-30 22:10 -0400
                      Re: Semantic properties of finite string inputs olcott <polcott333@gmail.com> - 2025-10-30 21:17 -0500
                        Re: Semantic properties of finite string inputs "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2025-10-30 19:18 -0700
                        Re: Semantic properties of finite string inputs dbush <dbush.mobile@gmail.com> - 2025-10-30 22:35 -0400
                      Re: Semantic properties of finite string inputs olcott <polcott333@gmail.com> - 2025-10-30 21:48 -0500
                        Re: Semantic properties of finite string inputs dbush <dbush.mobile@gmail.com> - 2025-10-30 22:50 -0400
                          Re: Semantic properties of finite string inputs olcott <polcott333@gmail.com> - 2025-10-30 21:56 -0500
                            Re: Semantic properties of finite string inputs dbush <dbush.mobile@gmail.com> - 2025-10-30 22:58 -0400
                              Re: Semantic properties of finite string inputs olcott <polcott333@gmail.com> - 2025-10-30 22:01 -0500
                                Re: Semantic properties of finite string inputs dbush <dbush.mobile@gmail.com> - 2025-10-30 23:03 -0400
                                  Re: Semantic properties of finite string inputs olcott <polcott333@gmail.com> - 2025-10-30 22:05 -0500
                                    Re: Semantic properties of finite string inputs dbush <dbush.mobile@gmail.com> - 2025-10-30 23:06 -0400
                                      Re: Semantic properties of finite string inputs olcott <polcott333@gmail.com> - 2025-10-30 22:16 -0500
                                        Re: Semantic properties of finite string inputs dbush <dbush.mobile@gmail.com> - 2025-10-30 23:20 -0400
                                          Re: Semantic properties of finite string inputs olcott <polcott333@gmail.com> - 2025-10-30 22:27 -0500
                                            Re: Semantic properties of finite string inputs dbush <dbush.mobile@gmail.com> - 2025-10-30 23:30 -0400
                            Re: Semantic properties of finite string inputs dbush <dbush.mobile@gmail.com> - 2025-10-30 22:59 -0400
                        Re: Semantic properties of finite string inputs Kaz Kylheku <643-408-1753@kylheku.com> - 2025-10-31 03:35 +0000
                    Re: Semantic properties of finite string inputs Kaz Kylheku <643-408-1753@kylheku.com> - 2025-10-31 03:29 +0000
                      Re: Semantic properties of finite string inputs olcott <polcott333@gmail.com> - 2025-10-30 22:47 -0500
                        Re: Semantic properties of finite string inputs Kaz Kylheku <643-408-1753@kylheku.com> - 2025-10-31 04:39 +0000
                          Re: Semantic properties of finite string inputs olcott <polcott333@gmail.com> - 2025-10-31 07:27 -0500
              Re: Semantic properties of finite string inputs olcott <polcott333@gmail.com> - 2025-10-30 17:32 -0500
                Re: Semantic properties of finite string inputs "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2025-10-30 17:01 -0700
              Re: Semantic properties of finite string inputs Ben Bacarisse <ben@bsb.me.uk> - 2025-10-31 00:57 +0000
        Re: Semantic properties of finite string inputs dbush <dbush.mobile@gmail.com> - 2025-10-30 16:44 -0400
    Re: Semantic properties of finite string inputs Mikko <mikko.levanto@iki.fi> - 2025-10-31 13:28 +0200
      Re: Semantic properties of finite string inputs olcott <polcott333@gmail.com> - 2025-10-31 07:44 -0500
        Re: Semantic properties of finite string inputs Mikko <mikko.levanto@iki.fi> - 2025-11-01 10:42 +0200
          Re: Semantic properties of finite string inputs olcott <polcott333@gmail.com> - 2025-11-01 08:25 -0500
            Re: Semantic properties of finite string inputs dbush <dbush.mobile@gmail.com> - 2025-11-01 09:51 -0400
              Re: Semantic properties of finite string inputs Tristan Wibberley <tristan.wibberley+netnews2@alumni.manchester.ac.uk> - 2025-11-01 20:12 +0000
                Re: Semantic properties of finite string inputs olcott <polcott333@gmail.com> - 2025-11-01 15:18 -0500
                  Re: Semantic properties of finite string inputs Tristan Wibberley <tristan.wibberley+netnews2@alumni.manchester.ac.uk> - 2025-11-01 20:53 +0000
                    Re: Semantic properties of finite string inputs olcott <polcott333@gmail.com> - 2025-11-01 16:08 -0500
                      Re: Semantic properties of finite string inputs Mr Flibble <flibble@red-dwarf.jmc.corp> - 2025-11-01 21:12 +0000
                  Re: Semantic properties of finite string inputs "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2025-11-01 13:59 -0700
            Re: Semantic properties of finite string inputs Mikko <mikko.levanto@iki.fi> - 2025-11-02 14:17 +0200
              Re: Semantic properties of finite string inputs olcott <polcott333@gmail.com> - 2025-11-02 07:29 -0600
                Re: Semantic properties of finite string inputs Kaz Kylheku <643-408-1753@kylheku.com> - 2025-11-02 22:26 +0000
                  Re: Semantic properties of finite string inputs Kaz Kylheku <643-408-1753@kylheku.com> - 2025-11-03 20:43 +0000
                    Re: Semantic properties of finite string inputs olcott <polcott333@gmail.com> - 2025-11-03 14:47 -0600
                      Re: Semantic properties of finite string inputs Kaz Kylheku <643-408-1753@kylheku.com> - 2025-11-03 22:40 +0000
                        Re: Semantic properties of finite string inputs olcott <polcott333@gmail.com> - 2025-11-03 16:56 -0600
                          Re: Semantic properties of finite string inputs Kaz Kylheku <643-408-1753@kylheku.com> - 2025-11-04 00:24 +0000
                            Re: Semantic properties of finite string inputs --- Closure ??? olcott <polcott333@gmail.com> - 2025-11-03 18:43 -0600
                              Re: Semantic properties of finite string inputs --- Closure ??? Kaz Kylheku <643-408-1753@kylheku.com> - 2025-11-04 02:22 +0000
                                Re: Semantic properties of finite string inputs --- Closure ??? olcott <polcott333@gmail.com> - 2025-11-03 21:02 -0600
                                  Re: Semantic properties of finite string inputs --- Closure ??? Kaz Kylheku <643-408-1753@kylheku.com> - 2025-11-04 04:28 +0000
                                    Re: Semantic properties of finite string inputs --- Closure ??? olcott <polcott333@gmail.com> - 2025-11-04 13:52 -0600
                                      Re: Semantic properties of finite string inputs --- Closure ??? Kaz Kylheku <643-408-1753@kylheku.com> - 2025-11-04 20:20 +0000
                                        Re: Semantic properties of finite string inputs --- Closure ??? Mr Flibble <flibble@red-dwarf.jmc.corp> - 2025-11-04 21:04 +0000
                                          Re: Semantic properties of finite string inputs --- Closure ??? wij <wyniijj5@gmail.com> - 2025-11-05 20:04 +0800
                                            Re: Semantic properties of finite string inputs --- Closure !!! olcott <polcott333@gmail.com> - 2025-11-05 09:50 -0600
                                              Re: Semantic properties of finite string inputs --- Closure !!! Kaz Kylheku <643-408-1753@kylheku.com> - 2025-11-05 17:51 +0000
                                                Re: Semantic properties of finite string inputs --- Closure !!! "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2025-11-05 12:18 -0800
                                                Re: Semantic properties of finite string inputs --- Closure !!! olcott <polcott333@gmail.com> - 2025-11-05 19:29 -0600
                                                  Re: Semantic properties of finite string inputs --- Closure !!! dbush <dbush.mobile@gmail.com> - 2025-11-05 20:43 -0500
                                                    Re: Semantic properties of finite string inputs --- Closure !!! Tristan Wibberley <tristan.wibberley+netnews2@alumni.manchester.ac.uk> - 2025-11-07 16:03 +0000
                                                  Re: Semantic properties of finite string inputs --- Closure !!! Tristan Wibberley <tristan.wibberley+netnews2@alumni.manchester.ac.uk> - 2025-11-07 15:59 +0000
                                                    Re: Semantic properties of finite string inputs --- Closure !!! olcott <polcott333@gmail.com> - 2025-11-07 10:13 -0600
                                                      Re: Semantic properties of finite string inputs --- Closure !!! Tristan Wibberley <tristan.wibberley+netnews2@alumni.manchester.ac.uk> - 2025-11-07 16:41 +0000
                                                        Re: Semantic properties of finite string inputs --- Closure !!! olcott <polcott333@gmail.com> - 2025-11-07 10:44 -0600
                                                    Re: Semantic properties of finite string inputs --- Closure !!! olcott <polcott333@gmail.com> - 2025-11-07 10:27 -0600
                                      Re: Semantic properties of finite string inputs --- Closure ??? joes <noreply@example.org> - 2025-11-05 14:52 +0000
                                        Re: Semantic properties of finite string inputs --- Closure ??? olcott <polcott333@gmail.com> - 2025-11-05 09:54 -0600
                                          Re: Semantic properties of finite string inputs --- Closure ??? joes <noreply@example.org> - 2025-11-05 16:52 +0000
                                            Re: Semantic properties of finite string inputs --- Closure on one point olcott <polcott333@gmail.com> - 2025-11-05 11:10 -0600
                                              Re: Semantic properties of finite string inputs --- Closure on one point "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2025-11-05 12:11 -0800
                                    Re: Semantic properties of finite string inputs --- Closure ??? Tristan Wibberley <tristan.wibberley+netnews2@alumni.manchester.ac.uk> - 2025-11-04 20:10 +0000
                                    Re: Semantic properties of finite string inputs --- Closure ??? olcott <polcott333@gmail.com> - 2025-11-04 14:35 -0600
                                      Re: Semantic properties of finite string inputs --- Closure ??? joes <noreply@example.org> - 2025-11-04 20:51 +0000
                                        Re: Semantic properties of finite string inputs --- Closure ??? olcott <polcott333@gmail.com> - 2025-11-04 14:55 -0600
                                          Re: Semantic properties of finite string inputs --- Closure ??? Kaz Kylheku <643-408-1753@kylheku.com> - 2025-11-04 21:43 +0000
                                      Re: Semantic properties of finite string inputs --- Closure ??? Kaz Kylheku <643-408-1753@kylheku.com> - 2025-11-04 21:35 +0000
                                    Re: Semantic properties of finite string inputs --- Kaz made a great test olcott <polcott333@gmail.com> - 2025-11-04 15:52 -0600
                                      Re: Semantic properties of finite string inputs --- Kaz made a great test Kaz Kylheku <643-408-1753@kylheku.com> - 2025-11-04 22:12 +0000
                                    Re: Semantic properties of finite string inputs --- Kaz code Deviation olcott <polcott333@gmail.com> - 2025-11-04 16:13 -0600
                                      Re: Semantic properties of finite string inputs --- Kaz code Deviation Kaz Kylheku <643-408-1753@kylheku.com> - 2025-11-04 22:33 +0000
                                        Re: Semantic properties of finite string inputs --- Kaz code Deviation "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2025-11-04 14:41 -0800
                                        Re: Semantic properties of finite string inputs --- Kaz code Deviation olcott <polcott333@gmail.com> - 2025-11-04 17:18 -0600
                                          Re: Semantic properties of finite string inputs --- Kaz code Deviation Kaz Kylheku <643-408-1753@kylheku.com> - 2025-11-05 02:08 +0000
                                            Re: Semantic properties of finite string inputs --- Kaz code Deviation olcott <polcott333@gmail.com> - 2025-11-04 20:24 -0600
                                    Re: Semantic properties of finite string inputs --- Kaz makes a very smart example olcott <polcott333@gmail.com> - 2025-11-04 18:16 -0600
                Re: Semantic properties of finite string inputs Mikko <mikko.levanto@iki.fi> - 2025-11-03 12:05 +0200
                  Re: Semantic properties of finite string inputs Tristan Wibberley <tristan.wibberley+netnews2@alumni.manchester.ac.uk> - 2025-11-03 17:16 +0000
                    Re: Semantic properties of finite string inputs Alan Mackenzie <acm@muc.de> - 2025-11-03 20:19 +0000
                      Re: Semantic properties of finite string inputs Kaz Kylheku <643-408-1753@kylheku.com> - 2025-11-03 21:35 +0000
                      Re: Semantic properties of finite string inputs Tristan Wibberley <tristan.wibberley+netnews2@alumni.manchester.ac.uk> - 2025-11-03 21:36 +0000
                        Olcott's revised position statement olcott <polcott333@gmail.com> - 2025-11-03 15:48 -0600
                        Re: Semantic properties of finite string inputs Kaz Kylheku <643-408-1753@kylheku.com> - 2025-11-03 21:57 +0000
            Re: Semantic properties of finite string inputs Richard Damon <Richard@Damon-Family.org> - 2025-11-02 14:10 -0500
    Re: Semantic properties of finite string inputs Tristan Wibberley <tristan.wibberley+netnews2@alumni.manchester.ac.uk> - 2025-10-31 12:35 +0000
      Re: Semantic properties of finite string inputs Kaz Kylheku <643-408-1753@kylheku.com> - 2025-10-31 18:00 +0000
        Re: Semantic properties of finite string inputs Tristan Wibberley <tristan.wibberley+netnews2@alumni.manchester.ac.uk> - 2025-10-31 19:46 +0000
          Re: Semantic properties of finite string inputs Kaz Kylheku <643-408-1753@kylheku.com> - 2025-10-31 23:10 +0000
            Re: Semantic properties of finite string inputs Tristan Wibberley <tristan.wibberley+netnews2@alumni.manchester.ac.uk> - 2025-11-01 02:47 +0000
              Re: Semantic properties of finite string inputs Richard Damon <Richard@Damon-Family.org> - 2025-11-01 00:14 -0400
                Re: Semantic properties of finite string inputs Tristan Wibberley <tristan.wibberley+netnews2@alumni.manchester.ac.uk> - 2025-11-01 18:09 +0000
                  Re: Semantic properties of finite string inputs "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2025-11-01 12:53 -0700
                    A decider for the proposition "Tristan is Olcott" (Was: Semantic properties of finite string inputs) Tristan Wibberley <tristan.wibberley+netnews2@alumni.manchester.ac.uk> - 2025-11-01 20:15 +0000
                      Re: A decider for the proposition "Tristan is Olcott" (Was: Semantic properties of finite string inputs) "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2025-11-01 14:06 -0700
          Re: Semantic properties of finite string inputs Richard Damon <Richard@Damon-Family.org> - 2025-10-31 22:13 -0400
            Re: Semantic properties of finite string inputs Tristan Wibberley <tristan.wibberley+netnews2@alumni.manchester.ac.uk> - 2025-11-01 02:53 +0000
              Re: Semantic properties of finite string inputs --- More precisely olcott <polcott333@gmail.com> - 2025-10-31 21:58 -0500
                Re: Semantic properties of finite string inputs --- More precisely Kaz Kylheku <643-408-1753@kylheku.com> - 2025-11-01 04:23 +0000
                  Re: Semantic properties of finite string inputs --- More precisely olcott <polcott333@gmail.com> - 2025-10-31 23:37 -0500
                    Re: Semantic properties of finite string inputs --- More precisely Kaz Kylheku <643-408-1753@kylheku.com> - 2025-11-01 07:47 +0000
                      Re: Semantic properties of finite string inputs --- More precisely olcott <polcott333@gmail.com> - 2025-11-01 08:22 -0500
                        Re: Semantic properties of finite string inputs --- More precisely Kaz Kylheku <643-408-1753@kylheku.com> - 2025-11-01 16:54 +0000
                          Re: Semantic properties of finite string inputs --- More precisely olcott <polcott333@gmail.com> - 2025-11-01 12:50 -0500
                            Re: Semantic properties of finite string inputs --- More precisely Kaz Kylheku <643-408-1753@kylheku.com> - 2025-11-01 20:59 +0000
                              Re: Semantic properties of finite string inputs --- More precisely olcott <polcott333@gmail.com> - 2025-11-01 16:32 -0500
                                Re: Semantic properties of finite string inputs --- More precisely "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2025-11-01 14:37 -0700
                                Re: Semantic properties of finite string inputs --- More precisely Kaz Kylheku <643-408-1753@kylheku.com> - 2025-11-01 22:11 +0000
                                  Re: Semantic properties of finite string inputs --- More precisely olcott <polcott333@gmail.com> - 2025-11-01 17:17 -0500
                                    Re: Semantic properties of finite string inputs --- More precisely Kaz Kylheku <643-408-1753@kylheku.com> - 2025-11-01 23:51 +0000
                  Re: Semantic properties of finite string inputs --- More precisely Tristan Wibberley <tristan.wibberley+netnews2@alumni.manchester.ac.uk> - 2025-11-01 18:14 +0000
                    Re: Semantic properties of finite string inputs --- deliberately misleading olcott <polcott333@gmail.com> - 2025-11-01 13:38 -0500
                      Re: Semantic properties of finite string inputs --- deliberately misleading dbush <dbush.mobile@gmail.com> - 2025-11-01 14:45 -0400
                        Re: Semantic properties of finite string inputs --- deliberately misleading olcott <polcott333@gmail.com> - 2025-11-01 14:01 -0500
                          Re: Semantic properties of finite string inputs --- deliberately misleading dbush <dbush.mobile@gmail.com> - 2025-11-01 15:05 -0400
                            Re: Semantic properties of finite string inputs --- deliberately misleading olcott <polcott333@gmail.com> - 2025-11-01 14:13 -0500
                              Re: Semantic properties of finite string inputs --- deliberately misleading Kaz Kylheku <643-408-1753@kylheku.com> - 2025-11-01 22:46 +0000
                                Re: Semantic properties of finite string inputs --- olcott <polcott333@gmail.com> - 2025-11-01 17:50 -0500
                                  Re: Semantic properties of finite string inputs --- Kaz Kylheku <643-408-1753@kylheku.com> - 2025-11-01 23:47 +0000
                                    Re: Semantic properties of finite string inputs --- olcott <polcott333@gmail.com> - 2025-11-01 18:56 -0500
                                      Re: Semantic properties of finite string inputs --- Kaz Kylheku <643-408-1753@kylheku.com> - 2025-11-02 00:12 +0000
                                        Re: Semantic properties of finite string inputs --- olcott <polcott333@gmail.com> - 2025-11-01 19:18 -0500
                                          Re: Semantic properties of finite string inputs --- Kaz Kylheku <643-408-1753@kylheku.com> - 2025-11-02 00:50 +0000
                                            Re: Semantic properties of finite string inputs --- olcott <polcott333@gmail.com> - 2025-11-01 20:13 -0500
                                              Re: Semantic properties of finite string inputs --- Kaz Kylheku <643-408-1753@kylheku.com> - 2025-11-02 02:40 +0000
                                                Re: Semantic properties of finite string inputs --- olcott <polcott333@gmail.com> - 2025-11-01 21:49 -0500
                                                  Re: Semantic properties of finite string inputs --- Kaz Kylheku <643-408-1753@kylheku.com> - 2025-11-02 17:47 +0000
                                  Re: Semantic properties of finite string inputs --- Tristan Wibberley <tristan.wibberley+netnews2@alumni.manchester.ac.uk> - 2025-11-02 07:39 +0000
                                    Re: Semantic properties of finite string inputs --- olcott <polcott333@gmail.com> - 2025-11-02 07:19 -0600
                              Re: Semantic properties of finite string inputs --- deliberately misleading dbush <dbush.mobile@gmail.com> - 2025-11-01 22:13 -0400
                          Re: Semantic properties of finite string inputs --- deliberately misleading Kaz Kylheku <643-408-1753@kylheku.com> - 2025-11-01 22:19 +0000
                            Re: Semantic properties of finite string inputs --- olcott <polcott333@gmail.com> - 2025-11-01 17:31 -0500
                              Re: Semantic properties of finite string inputs --- Kaz Kylheku <643-408-1753@kylheku.com> - 2025-11-02 17:57 +0000
                            Re: Semantic properties of finite string inputs --- deliberately misleading Tristan Wibberley <tristan.wibberley+netnews2@alumni.manchester.ac.uk> - 2025-11-01 22:36 +0000
                              Re: Semantic properties of finite string inputs --- deliberately misleading olcott <polcott333@gmail.com> - 2025-11-01 17:38 -0500
                                Re: Semantic properties of finite string inputs --- deliberately misleading Tristan Wibberley <tristan.wibberley+netnews2@alumni.manchester.ac.uk> - 2025-11-02 07:43 +0000
                              Re: Semantic properties of finite string inputs --- deliberately misleading Kaz Kylheku <643-408-1753@kylheku.com> - 2025-11-01 22:59 +0000
                                Re: Semantic properties of finite string inputs --- deliberately misleading olcott <polcott333@gmail.com> - 2025-11-01 18:09 -0500
                                  Re: Semantic properties of finite string inputs --- deliberately misleading Kaz Kylheku <643-408-1753@kylheku.com> - 2025-11-02 22:32 +0000
                              Re: Semantic properties of finite string inputs --- deliberately misleading "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2025-11-01 19:51 -0700
                      Re: Semantic properties of finite string inputs --- deliberately misleading "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2025-11-01 12:50 -0700
                      Re: Semantic properties of finite string inputs --- deliberately misleading Tristan Wibberley <tristan.wibberley+netnews2@alumni.manchester.ac.uk> - 2025-11-01 20:23 +0000
                        Re: Semantic properties of finite string inputs --- deliberately misleading olcott <polcott333@gmail.com> - 2025-11-01 15:32 -0500
                          Re: Semantic properties of finite string inputs --- deliberately misleading Tristan Wibberley <tristan.wibberley+netnews2@alumni.manchester.ac.uk> - 2025-11-01 21:16 +0000
                      Re: Semantic properties of finite string inputs --- deliberately misleading Kaz Kylheku <643-408-1753@kylheku.com> - 2025-11-01 22:00 +0000
              Re: Semantic properties of finite string inputs Kaz Kylheku <643-408-1753@kylheku.com> - 2025-11-01 03:38 +0000
              Re: Semantic properties of finite string inputs Richard Damon <Richard@Damon-Family.org> - 2025-11-01 00:19 -0400
        Re: Semantic properties of finite string inputs olcott <polcott333@gmail.com> - 2025-10-31 17:37 -0500
          Re: Semantic properties of finite string inputs Kaz Kylheku <643-408-1753@kylheku.com> - 2025-10-31 23:16 +0000
            Re: Semantic properties of finite string inputs dbush <dbush.mobile@gmail.com> - 2025-10-31 19:38 -0400
              Re: Semantic properties of finite string inputs Kaz Kylheku <643-408-1753@kylheku.com> - 2025-11-01 01:05 +0000
                Re: Semantic properties of finite string inputs Richard Heathfield <rjh@cpax.org.uk> - 2025-11-01 02:38 +0000
                  Re: Semantic properties of finite string inputs olcott <polcott333@gmail.com> - 2025-10-31 21:43 -0500
          Re: Semantic properties of finite string inputs Richard Damon <Richard@Damon-Family.org> - 2025-10-31 22:17 -0400
    Re: Semantic properties of finite string inputs Tristan Wibberley <tristan.wibberley+netnews2@alumni.manchester.ac.uk> - 2025-10-31 12:48 +0000
      Re: Semantic properties of finite string inputs olcott <polcott333@gmail.com> - 2025-10-31 08:58 -0500
        Re: Semantic properties of finite string inputs Tristan Wibberley <tristan.wibberley+netnews2@alumni.manchester.ac.uk> - 2025-10-31 17:43 +0000
          Re: Semantic properties of finite string inputs olcott <polcott333@gmail.com> - 2025-10-31 13:25 -0500
            Re: Semantic properties of finite string inputs Richard Damon <Richard@Damon-Family.org> - 2025-10-31 22:26 -0400
        Re: Semantic properties of finite string inputs Kaz Kylheku <643-408-1753@kylheku.com> - 2025-10-31 17:49 +0000
          Re: Semantic properties of finite string inputs olcott <polcott333@gmail.com> - 2025-10-31 17:38 -0500
            Re: Semantic properties of finite string inputs Kaz Kylheku <643-408-1753@kylheku.com> - 2025-10-31 23:06 +0000
              Monty Python (Was: Semantic properties of finite string inputs) Tristan Wibberley <tristan.wibberley+netnews2@alumni.manchester.ac.uk> - 2025-11-01 20:30 +0000
              Re: Semantic properties of finite string inputs olcott <polcott333@gmail.com> - 2025-11-01 15:36 -0500
        Re: Semantic properties of finite string inputs Richard Damon <Richard@Damon-Family.org> - 2025-10-31 14:06 -0400
          Re: Semantic properties of finite string inputs Tristan Wibberley <tristan.wibberley+netnews2@alumni.manchester.ac.uk> - 2025-10-31 19:57 +0000
            Re: Semantic properties of finite string inputs Richard Damon <Richard@Damon-Family.org> - 2025-10-31 22:32 -0400
              Re: Semantic properties of finite string inputs Tristan Wibberley <tristan.wibberley+netnews2@alumni.manchester.ac.uk> - 2025-11-01 20:36 +0000
                Re: Semantic properties of finite string inputs James Kuyper <jameskuyper@alumni.caltech.edu> - 2025-11-02 20:49 -0500
                  Re: Semantic properties of finite string inputs Richard Damon <Richard@Damon-Family.org> - 2025-11-02 22:44 -0500
                  Re: Semantic properties of finite string inputs Tristan Wibberley <tristan.wibberley+netnews2@alumni.manchester.ac.uk> - 2025-11-03 17:32 +0000
                    Re: Semantic properties of finite string inputs olcott <polcott333@gmail.com> - 2025-11-03 11:57 -0600
                Re: Semantic properties of finite string inputs Richard Damon <Richard@Damon-Family.org> - 2025-11-02 22:48 -0500
            Re: Semantic properties of finite string inputs Kaz Kylheku <643-408-1753@kylheku.com> - 2025-11-01 03:46 +0000
    Re: Semantic properties of finite string inputs Richard Damon <Richard@Damon-Family.org> - 2025-10-31 12:17 -0400
      Re: Semantic properties of finite string inputs olcott <polcott333@gmail.com> - 2025-10-31 11:51 -0500
        Re: Semantic properties of finite string inputs Richard Damon <Richard@Damon-Family.org> - 2025-10-31 13:42 -0400
          Re: Semantic properties of finite string inputs olcott <polcott333@gmail.com> - 2025-10-31 13:45 -0500
            Re: Semantic properties of finite string inputs Tristan Wibberley <tristan.wibberley+netnews2@alumni.manchester.ac.uk> - 2025-10-31 20:10 +0000
              Re: Semantic properties of finite string inputs --- many months of careful crafting olcott <polcott333@gmail.com> - 2025-10-31 16:00 -0500
                Re: Semantic properties of finite string inputs --- many months of careful crafting Richard Damon <Richard@Damon-Family.org> - 2025-10-31 22:45 -0400
                  Re: Semantic properties of finite string inputs --- many months of careful crafting Tristan Wibberley <tristan.wibberley+netnews2@alumni.manchester.ac.uk> - 2025-11-01 21:39 +0000
                Re: Semantic properties of finite string inputs --- many months of careful crafting joes <noreply@example.org> - 2025-11-01 12:01 +0000
                  Re: Semantic properties of finite string inputs --- many months of careful crafting olcott <polcott333@gmail.com> - 2025-11-01 08:14 -0500
            Re: Semantic properties of finite string inputs Richard Damon <Richard@Damon-Family.org> - 2025-10-31 22:38 -0400
        Re: Semantic properties of finite string inputs joes <noreply@example.org> - 2025-11-01 12:10 +0000
          Re: Semantic properties of finite string inputs olcott <polcott333@gmail.com> - 2025-11-01 08:18 -0500
            Re: Semantic properties of finite string inputs joes <noreply@example.org> - 2025-11-01 13:23 +0000
              Re: Semantic properties of finite string inputs olcott <polcott333@gmail.com> - 2025-11-01 08:55 -0500
            Re: Semantic properties of finite string inputs dbush <dbush.mobile@gmail.com> - 2025-11-01 09:45 -0400
              Re: Semantic properties of finite string inputs Kaz Kylheku <643-408-1753@kylheku.com> - 2025-11-01 22:49 +0000
            Re: Semantic properties of finite string inputs Kaz Kylheku <643-408-1753@kylheku.com> - 2025-11-01 16:59 +0000
              Re: Semantic properties of finite string inputs olcott <polcott333@gmail.com> - 2025-11-01 12:53 -0500
                Re: Semantic properties of finite string inputs Kaz Kylheku <643-408-1753@kylheku.com> - 2025-11-01 20:34 +0000
                  Re: Semantic properties of finite string inputs --- damned liars olcott <polcott333@gmail.com> - 2025-11-01 16:45 -0500
                    Re: Semantic properties of finite string inputs --- damned liars Kaz Kylheku <643-408-1753@kylheku.com> - 2025-11-01 23:40 +0000
                  Re: Semantic properties of finite string inputs --- Breakthrough olcott <polcott333@gmail.com> - 2025-11-01 17:11 -0500
                    Re: Semantic properties of finite string inputs --- Breakthrough Kaz Kylheku <643-408-1753@kylheku.com> - 2025-11-01 23:33 +0000
                      Re: Semantic properties of finite string inputs --- Breakthrough olcott <polcott333@gmail.com> - 2025-11-01 18:42 -0500
                        Re: Semantic properties of finite string inputs --- Breakthrough Kaz Kylheku <643-408-1753@kylheku.com> - 2025-11-01 23:58 +0000
                          Re: Semantic properties of finite string inputs --- Breakthrough olcott <polcott333@gmail.com> - 2025-11-01 19:01 -0500
                            Re: Semantic properties of finite string inputs --- Breakthrough Kaz Kylheku <643-408-1753@kylheku.com> - 2025-11-02 00:14 +0000
                              Re: Semantic properties of finite string inputs --- Breakthrough olcott <polcott333@gmail.com> - 2025-11-01 19:21 -0500
                          Re: Semantic properties of finite string inputs --- Breakthrough Mike Terry <news.dead.person.stones@darjeeling.plus.com> - 2025-11-02 01:13 +0000
                            Re: Semantic properties of finite string inputs --- Breakthrough "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2025-11-01 18:27 -0700
                              Re: Semantic properties of finite string inputs --- Breakthrough Mike Terry <news.dead.person.stones@darjeeling.plus.com> - 2025-11-02 01:59 +0000
                                Re: Semantic properties of finite string inputs --- Breakthrough "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2025-11-01 19:24 -0700
        Re: Semantic properties of finite string inputs Kaz Kylheku <643-408-1753@kylheku.com> - 2025-11-01 17:10 +0000
          Re: Semantic properties of finite string inputs olcott <polcott333@gmail.com> - 2025-11-01 12:15 -0500
            Re: Semantic properties of finite string inputs Mr Flibble <flibble@red-dwarf.jmc.corp> - 2025-11-01 17:25 +0000
              Re: Semantic properties of finite string inputs olcott <polcott333@gmail.com> - 2025-11-01 12:29 -0500
          Re: Semantic properties of finite string inputs Richard Heathfield <rjh@cpax.org.uk> - 2025-11-01 18:03 +0000
            Re: Semantic properties of finite string inputs Kaz Kylheku <643-408-1753@kylheku.com> - 2025-11-01 20:38 +0000
      Re: Semantic properties of finite string inputs Tristan Wibberley <tristan.wibberley+netnews2@alumni.manchester.ac.uk> - 2025-10-31 17:46 +0000
        Re: Semantic properties of finite string inputs Richard Damon <Richard@Damon-Family.org> - 2025-10-31 13:57 -0400
          Re: Semantic properties of finite string inputs Tristan Wibberley <tristan.wibberley+netnews2@alumni.manchester.ac.uk> - 2025-10-31 20:16 +0000
            Re: Semantic properties of finite string inputs "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2025-10-31 13:26 -0700
              Re: Semantic properties of finite string inputs Tristan Wibberley <tristan.wibberley+netnews2@alumni.manchester.ac.uk> - 2025-10-31 20:43 +0000
                Re: Semantic properties of finite string inputs "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2025-10-31 13:57 -0700
                Re: Semantic properties of finite string inputs olcott <polcott333@gmail.com> - 2025-10-31 16:06 -0500
                  Re: Semantic properties of finite string inputs "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2025-10-31 14:22 -0700
                  Re: Semantic properties of finite string inputs joes <noreply@example.org> - 2025-11-01 11:55 +0000
                    Re: Semantic properties of finite string inputs olcott <polcott333@gmail.com> - 2025-11-01 08:12 -0500
                      Re: Semantic properties of finite string inputs joes <noreply@example.org> - 2025-11-01 13:26 +0000
                        Re: Semantic properties of finite string inputs olcott <polcott333@gmail.com> - 2025-11-01 08:56 -0500
                Re: Semantic properties of finite string inputs "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2025-10-31 14:23 -0700
                Re: Semantic properties of finite string inputs Richard Damon <Richard@Damon-Family.org> - 2025-10-31 22:50 -0400
                  Re: Semantic properties of finite string inputs Tristan Wibberley <tristan.wibberley+netnews2@alumni.manchester.ac.uk> - 2025-11-01 21:47 +0000
            Re: Semantic properties of finite string inputs Kaz Kylheku <643-408-1753@kylheku.com> - 2025-11-01 00:38 +0000
              Re: Semantic properties of finite string inputs Tristan Wibberley <tristan.wibberley+netnews2@alumni.manchester.ac.uk> - 2025-11-01 21:50 +0000
                Re: Semantic properties of finite string inputs olcott <polcott333@gmail.com> - 2025-11-01 16:57 -0500
            Re: Semantic properties of finite string inputs Richard Damon <Richard@Damon-Family.org> - 2025-10-31 22:49 -0400
              Re: Semantic properties of finite string inputs Tristan Wibberley <tristan.wibberley+netnews2@alumni.manchester.ac.uk> - 2025-11-01 21:54 +0000
                Re: Semantic properties of finite string inputs olcott <polcott333@gmail.com> - 2025-11-01 16:59 -0500
                  Re: Semantic properties of finite string inputs Tristan Wibberley <tristan.wibberley+netnews2@alumni.manchester.ac.uk> - 2025-11-01 22:28 +0000
    Re: Semantic properties of finite string inputs Mr Flibble <flibble@red-dwarf.jmc.corp> - 2025-11-01 13:44 +0000
      Re: Semantic properties of finite string inputs olcott <polcott333@gmail.com> - 2025-11-01 08:57 -0500
        Re: Semantic properties of finite string inputs Mr Flibble <flibble@red-dwarf.jmc.corp> - 2025-11-01 16:07 +0000
          Re: Semantic properties of finite string inputs olcott <polcott333@gmail.com> - 2025-11-01 12:07 -0500
            Re: Semantic properties of finite string inputs Mr Flibble <flibble@red-dwarf.jmc.corp> - 2025-11-01 17:26 +0000
              Re: Semantic properties of finite string inputs olcott <polcott333@gmail.com> - 2025-11-01 12:31 -0500
                Re: Semantic properties of finite string inputs "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2025-11-01 12:42 -0700

Page 11 of 15 — ← Prev page 1 … 9 10 [11] 12 13 … 15  Next page →


#134554

Fromdbush <dbush.mobile@gmail.com>
Date2025-10-31 19:38 -0400
Message-ID<10e3h9u$rtv2$1@dont-email.me>
In reply to#134553
On 10/31/2025 7:16 PM, Kaz Kylheku wrote:
> If it were not for the fact that I've been here for 30 years, I might
> suspect you are the dumbest fuck ever to seriously participate in
> a comp.* newsgroup.
> 

Really?  I can't imagine worse...

[toc] | [prev] | [next] | [standalone]


#134572

FromKaz Kylheku <643-408-1753@kylheku.com>
Date2025-11-01 01:05 +0000
Message-ID<20251031174447.481@kylheku.com>
In reply to#134554
On 2025-10-31, dbush <dbush.mobile@gmail.com> wrote:
> On 10/31/2025 7:16 PM, Kaz Kylheku wrote:
>> If it were not for the fact that I've been here for 30 years, I might
>> suspect you are the dumbest fuck ever to seriously participate in
>> a comp.* newsgroup.
>> 
>
> Really?  I can't imagine worse...

Oh, the names escape me now. Here are a few: Ioannis Vranos, G Moore,
Scott Nudds, "Aminer", E. Robert Tisdale, Rick C. Hodgin, "fir",
Bill Cunningham, Edward G. Nilges (spinoza1111), Bonita Montero,
CBfalconer, Alicia Carla Longstreet, ...




-- 
TXR Programming Language: http://nongnu.org/txr
Cygnal: Cygwin Native Application Library: http://kylheku.com/cygnal
Mastodon: @Kazinator@mstdn.ca

[toc] | [prev] | [next] | [standalone]


#134584

FromRichard Heathfield <rjh@cpax.org.uk>
Date2025-11-01 02:38 +0000
Message-ID<10e3rrn$vdgq$1@dont-email.me>
In reply to#134572
On 01/11/2025 01:05, Kaz Kylheku wrote:
> On 2025-10-31, dbush <dbush.mobile@gmail.com> wrote:
>> On 10/31/2025 7:16 PM, Kaz Kylheku wrote:
>>> If it were not for the fact that I've been here for 30 years, I might
>>> suspect you are the dumbest fuck ever to seriously participate in
>>> a comp.* newsgroup.
>>>
>>
>> Really?  I can't imagine worse...
> 
> Oh, the names escape me now. Here are a few: Ioannis Vranos, G Moore,
> Scott Nudds, "Aminer", E. Robert Tisdale, Rick C. Hodgin, "fir",
> Bill Cunningham, Edward G. Nilges (spinoza1111), Bonita Montero,
> CBfalconer, Alicia Carla Longstreet, ...

ISTR that Ioannis Vranos (the mouse who thought he was a cat) 
eventually clued up?

You're being a tad harsh on Chuck F, too; no way was he as bad as 
Olcott.

But apart from those, the list looks pretty solid. Possibly add 
"bart"? (The modern one, not the 1990s one.)

-- 
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]


#134585

Fromolcott <polcott333@gmail.com>
Date2025-10-31 21:43 -0500
Message-ID<10e3s54$vhhj$1@dont-email.me>
In reply to#134584
On 10/31/2025 9:38 PM, Richard Heathfield wrote:
> On 01/11/2025 01:05, Kaz Kylheku wrote:
>> On 2025-10-31, dbush <dbush.mobile@gmail.com> wrote:
>>> On 10/31/2025 7:16 PM, Kaz Kylheku wrote:
>>>> If it were not for the fact that I've been here for 30 years, I might
>>>> suspect you are the dumbest fuck ever to seriously participate in
>>>> a comp.* newsgroup.
>>>>
>>>
>>> Really?  I can't imagine worse...
>>
>> Oh, the names escape me now. Here are a few: Ioannis Vranos, G Moore,
>> Scott Nudds, "Aminer", E. Robert Tisdale, Rick C. Hodgin, "fir",
>> Bill Cunningham, Edward G. Nilges (spinoza1111), Bonita Montero,
>> CBfalconer, Alicia Carla Longstreet, ...
> 
> ISTR that Ioannis Vranos (the mouse who thought he was a cat) eventually 
> clued up?
> 
> You're being a tad harsh on Chuck F, too; no way was he as bad as Olcott.
> 
> But apart from those, the list looks pretty solid. Possibly add "bart"? 
> (The modern one, not the 1990s one.)
> 

Are you just a damned liar too?

void DDD()
{
   HHH(DDD);
   return;
}

HHH simulates DDD then DDD calls HHH(DDD)
what comes next?

-- 
Copyright 2025 Olcott "Talent hits a target no one else can hit; Genius
hits a target no one else can see." Arthur Schopenhauer

[toc] | [prev] | [next] | [standalone]


#134580

FromRichard Damon <Richard@Damon-Family.org>
Date2025-10-31 22:17 -0400
Message-ID<d5eNQ.224673$ol44.25621@fx33.iad>
In reply to#134547
On 10/31/25 6:37 PM, olcott wrote:
> On 10/31/2025 1:00 PM, Kaz Kylheku wrote:
>> On 2025-10-31, Tristan Wibberley 
>> <tristan.wibberley+netnews2@alumni.manchester.ac.uk> wrote:
>>> On 30/10/2025 14:49, olcott wrote:
>>> [snip]
>>>> H can recognize a call to itself in
>>>> its input. The whole input is the
>>>> text of the function D. The executable
>>>> interpreters are named H.exe and H1.exe.
>>>
>>> Thank you for posting this. It is *super* interesting.
>>
>> An algorithm recognizing the presence of itself in its input is an
>> undecidable problem.
>>
>> Equivalence of algoirthms is undecidable; i.e. the function
>>
>>   equal_functions(f1, f2)
>>
>> is incomputable.
>>
>> Olcott's "x86utm" and "Halt7" code uses machine address equivalence as a
>> substitute for function equivalence.
>>
>> He has two functions HHH and HHH1 which are absolutely identical
>> except for their name.
> 
> void DDD()   // a dumbed down version of D.
> {
>    HHH(DDD);
>    return;
> }
> 
> No dumb bunny DDD only calls one of them and this
> changes everything. Since I have told you this
> hundreds of times you are far far worse than a
> dumb bunny.

So, you admit that the ONE that it calls is the one in Halt7.c?

And thus, that DEFINES what HHH is when you talk about it, as you can't 
have two different version of the same machine and call them the same.

> 
>>  Yet, they trigger a different behavior,
>> because the abort check in his simulation assumes that if two
>> code addresses are unequal, they are different functions.
>>
> 
> 

[toc] | [prev] | [next] | [standalone]


#134487

FromTristan Wibberley <tristan.wibberley+netnews2@alumni.manchester.ac.uk>
Date2025-10-31 12:48 +0000
Message-ID<10e2b7g$f4dt$2@dont-email.me>
In reply to#134369
On 30/10/2025 14:49, olcott wrote:

> H and H1 are simulating termination
> analyzers anchored in a C interpreter
> that takes a finite string input

How should we interpret "anchored" here? I feel it is crucial to
resolving a missing piece vis-a-vis that the symbol "H" is not defined
in the input text "D".

Should we take it that the program component that is a C interpreter
includes the C text that defines "H"?

--
Tristan Wibberley

The message body is Copyright (C) 2025 Tristan Wibberley except
citations and quotations noted. All Rights Reserved except that you may,
of course, cite it academically giving credit to me, distribute it
verbatim as part of a usenet system or its archives, and use it to
promote my greatness and general superiority without misrepresentation
of my opinions other than my opinion of my greatness and general
superiority which you _may_ misrepresent. You definitely MAY NOT train
any production AI system with it but you may train experimental AI that
will only be used for evaluation of the AI methods it implements.

[toc] | [prev] | [next] | [standalone]


#134493

Fromolcott <polcott333@gmail.com>
Date2025-10-31 08:58 -0500
Message-ID<10e2f9c$hi2c$1@dont-email.me>
In reply to#134487
On 10/31/2025 7:48 AM, Tristan Wibberley wrote:
> On 30/10/2025 14:49, olcott wrote:
> 
>> H and H1 are simulating termination
>> analyzers anchored in a C interpreter
>> that takes a finite string input
> 
> How should we interpret "anchored" here? I feel it is crucial to
> resolving a missing piece vis-a-vis that the symbol "H" is not defined
> in the input text "D".
> 

H and H1 are both C interpreters named H.exe and H1.exe
respectively. When they see they see the name H or the name
H1 they know to calls themselves with the argument.
D calls H(D) in recursive simulation.

int D()
{
   int Halt_Status = H(D);
   if (Halt_Status)
     HERE: goto HERE;
   return Halt_Status;
}

H simulates D
that calls H(D) to simulate D
that calls H(D) to simulate D
that calls H(D) to simulate D
that calls H(D) to simulate D
that calls H(D) to simulate D
until H sees this repeating pattern
Then H returns 0 to reject its input as non-halting.

> Should we take it that the program component that is a C interpreter
> includes the C text that defines "H"?
> 

H is like an operating system call. We only see
the execution trace of the input C textfile.

> --
> Tristan Wibberley
> 
> The message body is Copyright (C) 2025 Tristan Wibberley except
> citations and quotations noted. All Rights Reserved except that you may,
> of course, cite it academically giving credit to me, distribute it
> verbatim as part of a usenet system or its archives, and use it to
> promote my greatness and general superiority without misrepresentation
> of my opinions other than my opinion of my greatness and general
> superiority which you _may_ misrepresent. You definitely MAY NOT train
> any production AI system with it but you may train experimental AI that
> will only be used for evaluation of the AI methods it implements.
> 


-- 
Copyright 2025 Olcott "Talent hits a target no one else can hit; Genius
hits a target no one else can see." Arthur Schopenhauer

[toc] | [prev] | [next] | [standalone]


#134517

FromTristan Wibberley <tristan.wibberley+netnews2@alumni.manchester.ac.uk>
Date2025-10-31 17:43 +0000
Message-ID<10e2sfu$lv5v$1@dont-email.me>
In reply to#134493
On 31/10/2025 13:58, olcott wrote:
> H and H1 are both C interpreters named H.exe and H1.exe
> respectively. When they see they see the name H or the name
> H1 they know to calls themselves with the argument.

Are H.exe and H1.exe PECOFF executable files for Microsoft Windows?

If so, then there's some mixing up of terminology and concepts here.
Mixing "call" and "execute" as well as using C-call syntax to express
execution of an interpreter, for example. Also you say "know to
calls[sic] themselves" and I think it should be "know to call each
other, as respectively named, " - perhaps that's not what you mean, in
which case the situation is very much less clear. Furthermore, further
review would also be too much effort for me even with clarifications.

--
Tristan Wibberley

The message body is Copyright (C) 2025 Tristan Wibberley except
citations and quotations noted. All Rights Reserved except that you may,
of course, cite it academically giving credit to me, distribute it
verbatim as part of a usenet system or its archives, and use it to
promote my greatness and general superiority without misrepresentation
of my opinions other than my opinion of my greatness and general
superiority which you _may_ misrepresent. You definitely MAY NOT train
any production AI system with it but you may train experimental AI that
will only be used for evaluation of the AI methods it implements.

[toc] | [prev] | [next] | [standalone]


#134526

Fromolcott <polcott333@gmail.com>
Date2025-10-31 13:25 -0500
Message-ID<10e2uue$mv1r$1@dont-email.me>
In reply to#134517
On 10/31/2025 12:43 PM, Tristan Wibberley wrote:
> On 31/10/2025 13:58, olcott wrote:
>> H and H1 are both C interpreters named H.exe and H1.exe
>> respectively. When they see they see the name H or the name
>> H1 they know to calls themselves with the argument.
> 
> Are H.exe and H1.exe PECOFF executable files for Microsoft Windows?
> 

They don't physically exist just yet.
When they do they will run under Windows
and Linux command prompt.

> If so, then there's some mixing up of terminology and concepts here.
> Mixing "call" and "execute" as well as using C-call syntax to express
> execution of an interpreter, for example. Also you say "know to
> calls[sic] themselves" and I think it should be "know to call each
> other, as respectively named, " - perhaps that's not what you mean, in
> which case the situation is very much less clear. Furthermore, further
> review would also be too much effort for me even with clarifications.
> 

This is a whole different thing than I have been
talking about for several years. It will be a
C interpreter that takes C source code as input
and produces an execution trace in C as output.

I am adapting a C interpreter so that when it
sees H(D) it will interpret D with another
instance of itself.

I am trying to make this generic so that whenever
it sees H(anything) it will interpret "anything"
with another instance of itself. It will be as
much as possible just like my x86utm system except
at the C level because x86 is over everyone's heads.

If there is no call to itself then it will just
interpret the C input file. It will have both
an H and an H1.

> --
> Tristan Wibberley
> 
> The message body is Copyright (C) 2025 Tristan Wibberley except
> citations and quotations noted. All Rights Reserved except that you may,
> of course, cite it academically giving credit to me, distribute it
> verbatim as part of a usenet system or its archives, and use it to
> promote my greatness and general superiority without misrepresentation
> of my opinions other than my opinion of my greatness and general
> superiority which you _may_ misrepresent. You definitely MAY NOT train
> any production AI system with it but you may train experimental AI that
> will only be used for evaluation of the AI methods it implements.
> 


-- 
Copyright 2025 Olcott "Talent hits a target no one else can hit; Genius
hits a target no one else can see." Arthur Schopenhauer

[toc] | [prev] | [next] | [standalone]


#134581

FromRichard Damon <Richard@Damon-Family.org>
Date2025-10-31 22:26 -0400
Message-ID<kdeNQ.224674$ol44.59828@fx33.iad>
In reply to#134526
On 10/31/25 2:25 PM, olcott wrote:
> On 10/31/2025 12:43 PM, Tristan Wibberley wrote:
>> On 31/10/2025 13:58, olcott wrote:
>>> H and H1 are both C interpreters named H.exe and H1.exe
>>> respectively. When they see they see the name H or the name
>>> H1 they know to calls themselves with the argument.
>>
>> Are H.exe and H1.exe PECOFF executable files for Microsoft Windows?
>>
> 
> They don't physically exist just yet.
> When they do they will run under Windows
> and Linux command prompt.
> 
>> If so, then there's some mixing up of terminology and concepts here.
>> Mixing "call" and "execute" as well as using C-call syntax to express
>> execution of an interpreter, for example. Also you say "know to
>> calls[sic] themselves" and I think it should be "know to call each
>> other, as respectively named, " - perhaps that's not what you mean, in
>> which case the situation is very much less clear. Furthermore, further
>> review would also be too much effort for me even with clarifications.
>>
> 
> This is a whole different thing than I have been
> talking about for several years. It will be a
> C interpreter that takes C source code as input
> and produces an execution trace in C as output.
> 
> I am adapting a C interpreter so that when it
> sees H(D) it will interpret D with another
> instance of itself.

Which is just incorrect, as it needs to interprete what that code of H 
does. or at least figure out what it would actualy do.

THus, it will be incorrect to return an answer based on an assumption 
that this call to H(D) acts differently then H actually acts when given D.

ALso remember, D can't just pass its address, as that isn't what H takes 
as its input. D will need to pass the source code for D to H.

That means it may be better to go back to the original model where P 
takes as its parameter the representation of the program, and passes 
that on to H duplicated.

> 
> I am trying to make this generic so that whenever
> it sees H(anything) it will interpret "anything"
> with another instance of itself. It will be as
> much as possible just like my x86utm system except
> at the C level because x86 is over everyone's heads.

Just remember that what ever H decides about that input, is the answer 
it must presume to return to that call it interpreted.

And this means it can't assume that the call to H won't return if H 
actually returns an answer to that input.

> 
> If there is no call to itself then it will just
> interpret the C input file. It will have both
> an H and an H1.
> 
>> -- 
>> Tristan Wibberley
>>
>> The message body is Copyright (C) 2025 Tristan Wibberley except
>> citations and quotations noted. All Rights Reserved except that you may,
>> of course, cite it academically giving credit to me, distribute it
>> verbatim as part of a usenet system or its archives, and use it to
>> promote my greatness and general superiority without misrepresentation
>> of my opinions other than my opinion of my greatness and general
>> superiority which you _may_ misrepresent. You definitely MAY NOT train
>> any production AI system with it but you may train experimental AI that
>> will only be used for evaluation of the AI methods it implements.
>>
> 
> 

[toc] | [prev] | [next] | [standalone]


#134519

FromKaz Kylheku <643-408-1753@kylheku.com>
Date2025-10-31 17:49 +0000
Message-ID<20251031104901.829@kylheku.com>
In reply to#134493
On 2025-10-31, olcott <polcott333@gmail.com> wrote:
> H and H1 are both C interpreters named H.exe and H1.exe
> respectively.

Give the URL or they don't exist, and we won't mention them again.

-- 
TXR Programming Language: http://nongnu.org/txr
Cygnal: Cygwin Native Application Library: http://kylheku.com/cygnal
Mastodon: @Kazinator@mstdn.ca

[toc] | [prev] | [next] | [standalone]


#134548

Fromolcott <polcott333@gmail.com>
Date2025-10-31 17:38 -0500
Message-ID<10e3dpr$rmdh$2@dont-email.me>
In reply to#134519
On 10/31/2025 12:49 PM, Kaz Kylheku wrote:
> On 2025-10-31, olcott <polcott333@gmail.com> wrote:
>> H and H1 are both C interpreters named H.exe and H1.exe
>> respectively.
> 
> Give the URL or they don't exist, and we won't mention them again.
> 

I am in the process of writing them in the mean
time you could try to not be too stupid to
understand this:

D simulated by H according to the semantics of C
programming language (until H sees the repeating
pattern) does enable H to report that its simulated
input cannot possibly reach its own simulated
"return" statement final halt state.

-- 
Copyright 2025 Olcott "Talent hits a target no one else can hit; Genius
hits a target no one else can see." Arthur Schopenhauer

[toc] | [prev] | [next] | [standalone]


#134551

FromKaz Kylheku <643-408-1753@kylheku.com>
Date2025-10-31 23:06 +0000
Message-ID<20251031155644.276@kylheku.com>
In reply to#134548
On 2025-10-31, olcott <polcott333@gmail.com> wrote:
> On 10/31/2025 12:49 PM, Kaz Kylheku wrote:
>> On 2025-10-31, olcott <polcott333@gmail.com> wrote:
>>> H and H1 are both C interpreters named H.exe and H1.exe
>>> respectively.
>> 
>> Give the URL or they don't exist, and we won't mention them again.
>> 
>
> I am in the process of writing them in the mean

You are in the process of /saying/ you are writing them, that's all.

I suspect you've not even done the googling regarding whose
C interpreter you are going to use.

Because you need a tower of interpreters, the interpreter will have to
be complete and reliable enough to interpret its own code.

> time you could try to not be too stupid to
> understand this:
>
> D simulated by H according to the semantics of C
> programming language (until H sees the repeating
> pattern) does enable H to report that its simulated
> input cannot possibly reach its own simulated
> "return" statement final halt state.

You simply don't know your ass from a hole in the ground at this point.

-- 
TXR Programming Language: http://nongnu.org/txr
Cygnal: Cygwin Native Application Library: http://kylheku.com/cygnal
Mastodon: @Kazinator@mstdn.ca

[toc] | [prev] | [next] | [standalone]


#134729 — Monty Python (Was: Semantic properties of finite string inputs)

FromTristan Wibberley <tristan.wibberley+netnews2@alumni.manchester.ac.uk>
Date2025-11-01 20:30 +0000
SubjectMonty Python (Was: Semantic properties of finite string inputs)
Message-ID<10e5ql1$1i3jo$4@dont-email.me>
In reply to#134551
"I'd like an argument please"
"No you wouldn't!"

--
Tristan Wibberley

The message body is Copyright (C) 2025 Tristan Wibberley except
citations and quotations noted. All Rights Reserved except that you may,
of course, cite it academically giving credit to me, distribute it
verbatim as part of a usenet system or its archives, and use it to
promote my greatness and general superiority without misrepresentation
of my opinions other than my opinion of my greatness and general
superiority which you _may_ misrepresent. You definitely MAY NOT train
any production AI system with it but you may train experimental AI that
will only be used for evaluation of the AI methods it implements.

[toc] | [prev] | [next] | [standalone]


#134733

Fromolcott <polcott333@gmail.com>
Date2025-11-01 15:36 -0500
Message-ID<10e5r00$1ij16$1@dont-email.me>
In reply to#134551
On 10/31/2025 6:06 PM, Kaz Kylheku wrote:
> On 2025-10-31, olcott <polcott333@gmail.com> wrote:
>> On 10/31/2025 12:49 PM, Kaz Kylheku wrote:
>>> On 2025-10-31, olcott <polcott333@gmail.com> wrote:
>>>> H and H1 are both C interpreters named H.exe and H1.exe
>>>> respectively.
>>>
>>> Give the URL or they don't exist, and we won't mention them again.
>>>
>>
>> I am in the process of writing them in the mean
> 
> You are in the process of /saying/ you are writing them, that's all.
> 
> I suspect you've not even done the googling regarding whose
> C interpreter you are going to use.
> 
> Because you need a tower of interpreters, the interpreter will have to
> be complete and reliable enough to interpret its own code.
> 
>> time you could try to not be too stupid to
>> understand this:
>>
>> D simulated by H according to the semantics of C
>> programming language (until H sees the repeating
>> pattern) does enable H to report that its simulated
>> input cannot possibly reach its own simulated
>> "return" statement final halt state.
> 
> You simply don't know your ass from a hole in the ground at this point.
> 

If this was true then you could show how D
simulated by H in C does reach the simulated
"return" instruction of D and you could show
this in C.

On 10/31/2025 7:44 PM, Kaz Kylheku wrote:
 > I can write a C interpreter which can interpret itself.

If that is true then you lied about D simulated by H
reaching its simulated "return" statement.

-- 
Copyright 2025 Olcott "Talent hits a target no one else can hit; Genius
hits a target no one else can see." Arthur Schopenhauer

[toc] | [prev] | [next] | [standalone]


#134524

FromRichard Damon <Richard@Damon-Family.org>
Date2025-10-31 14:06 -0400
Message-ID<pU6NQ.937231$p8E9.569275@fx18.iad>
In reply to#134493
On 10/31/25 9:58 AM, olcott wrote:
> On 10/31/2025 7:48 AM, Tristan Wibberley wrote:
>> On 30/10/2025 14:49, olcott wrote:
>>
>>> H and H1 are simulating termination
>>> analyzers anchored in a C interpreter
>>> that takes a finite string input
>>
>> How should we interpret "anchored" here? I feel it is crucial to
>> resolving a missing piece vis-a-vis that the symbol "H" is not defined
>> in the input text "D".
>>
> 
> H and H1 are both C interpreters named H.exe and H1.exe
> respectively. When they see they see the name H or the name
> H1 they know to calls themselves with the argument.
> D calls H(D) in recursive simulation.

And if they accept and run this input, they fail to be correct C 
interpreters, as the code has a required diagnostic.

The key point is that the input needs to include the code of H to be 
correct.

Note, H and H1 are SUPPOSED to be Halt Deciders. They might use a "C 
Compiler" to understand the input, but their answer is supposed to be if 
the input halts.

Note, with your claim, H(D) is incorrect syntax, as H isn't being passed 
the C code of the function D.

Thus, you need to change how you are representing this program.

> 
> int D()
> {
>    int Halt_Status = H(D);
>    if (Halt_Status)
>      HERE: goto HERE;
>    return Halt_Status;
> }
> 
> H simulates D
> that calls H(D) to simulate D
> that calls H(D) to simulate D
> that calls H(D) to simulate D
> that calls H(D) to simulate D
> that calls H(D) to simulate D
> until H sees this repeating pattern
> Then H returns 0 to reject its input as non-halting.
> 
>> Should we take it that the program component that is a C interpreter
>> includes the C text that defines "H"?
>>
> 
> H is like an operating system call. We only see
> the execution trace of the input C textfile.

But it wan't passed a textfile!!!

[toc] | [prev] | [next] | [standalone]


#134535

FromTristan Wibberley <tristan.wibberley+netnews2@alumni.manchester.ac.uk>
Date2025-10-31 19:57 +0000
Message-ID<10e34bk$ojqn$2@dont-email.me>
In reply to#134524
On 31/10/2025 18:06, Richard Damon wrote:
> [H and H1] fail to be correct C
> interpreters, as the code has a required diagnostic.

Really? even in K&R C?


> The key point is that the input needs to include the code of H to be
> correct.
> 
> Note, H and H1 are SUPPOSED to be Halt Deciders. They might use a "C

"are supposed" as in, somebody somewhere supposes it? That somebody is
you. I don't think I or Olcott suppose it.

I suppose it's a loop decider for ... some fixedpoint of something
involving the expression "specific class of loop". The class that is
programmed in specifically because it's the class of loop that is easy
to decide.


--
Tristan Wibberley

The message body is Copyright (C) 2025 Tristan Wibberley except
citations and quotations noted. All Rights Reserved except that you may,
of course, cite it academically giving credit to me, distribute it
verbatim as part of a usenet system or its archives, and use it to
promote my greatness and general superiority without misrepresentation
of my opinions other than my opinion of my greatness and general
superiority which you _may_ misrepresent. You definitely MAY NOT train
any production AI system with it but you may train experimental AI that
will only be used for evaluation of the AI methods it implements.

[toc] | [prev] | [next] | [standalone]


#134582

FromRichard Damon <Richard@Damon-Family.org>
Date2025-10-31 22:32 -0400
Message-ID<PieNQ.94670$fBxc.26242@fx08.iad>
In reply to#134535
On 10/31/25 3:57 PM, Tristan Wibberley wrote:
> On 31/10/2025 18:06, Richard Damon wrote:
>> [H and H1] fail to be correct C
>> interpreters, as the code has a required diagnostic.
> 
> Really? even in K&R C?

Yep, the link step will fail as H and H1 are not defined.


> 
> 
>> The key point is that the input needs to include the code of H to be
>> correct.
>>
>> Note, H and H1 are SUPPOSED to be Halt Deciders. They might use a "C
> 
> "are supposed" as in, somebody somewhere supposes it? That somebody is
> you. I don't think I or Olcott suppose it.

As in they are claimed to be in order to be the rebuttal to the proof.

Hard to prove that a Halt Decider can exist if you don't provide the 
Halt Decider.

This is his typical category error.

> 
> I suppose it's a loop decider for ... some fixedpoint of something
> involving the expression "specific class of loop". The class that is
> programmed in specifically because it's the class of loop that is easy
> to decide.
> 

But since the actual loop turns out to be finite in operation, how ever 
y9ou try to define your "loop decider" it fails to be a Halt Decider, 
even for this one case.

The input program will halt when run based on the claimed behavior of H 
and H1.

H says it doesn't, and thus it MUST be wrong.

> 
> --
> Tristan Wibberley
> 

[toc] | [prev] | [next] | [standalone]


#134732

FromTristan Wibberley <tristan.wibberley+netnews2@alumni.manchester.ac.uk>
Date2025-11-01 20:36 +0000
Message-ID<10e5qvi$1i3jo$5@dont-email.me>
In reply to#134582
On 01/11/2025 02:32, Richard Damon wrote:
> On 10/31/25 3:57 PM, Tristan Wibberley wrote:
>> On 31/10/2025 18:06, Richard Damon wrote:
>>> [H and H1] fail to be correct C
>>> interpreters, as the code has a required diagnostic.
>>
>> Really? even in K&R C?
> 
> Yep, the link step will fail as H and H1 are not defined.

Is "link step" defined in K&R C?

The compiler can provide definitions for H--which is the only symbol
missing a definition in the situation statement, IIRC--/to satisfy the
situation/.

Olcott: it might help to say, instead of that H and H1 are anchored in
the interpreter, that the interpreter defines the symbol "H", if that is
what you mean for your situation (I think it is but also my C
terminology is rusty). I expect Kaz will know, he's a real dab-hand.

--
Tristan Wibberley

The message body is Copyright (C) 2025 Tristan Wibberley except
citations and quotations noted. All Rights Reserved except that you may,
of course, cite it academically giving credit to me, distribute it
verbatim as part of a usenet system or its archives, and use it to
promote my greatness and general superiority without misrepresentation
of my opinions other than my opinion of my greatness and general
superiority which you _may_ misrepresent. You definitely MAY NOT train
any production AI system with it but you may train experimental AI that
will only be used for evaluation of the AI methods it implements.

[toc] | [prev] | [next] | [standalone]


#134869

FromJames Kuyper <jameskuyper@alumni.caltech.edu>
Date2025-11-02 20:49 -0500
Message-ID<10e91nv$2a744$5@dont-email.me>
In reply to#134732
On 2025-11-01 16:36, Tristan Wibberley wrote:
> On 01/11/2025 02:32, Richard Damon wrote:
>> On 10/31/25 3:57 PM, Tristan Wibberley wrote:
>>> On 31/10/2025 18:06, Richard Damon wrote:
>>>> [H and H1] fail to be correct C
>>>> interpreters, as the code has a required diagnostic.
>>>
>>> Really? even in K&R C?
>>
>> Yep, the link step will fail as H and H1 are not defined.
> 
> Is "link step" defined in K&R C?

Not in the first edition. Section 11.2 mentions that a program can be
made up of many files, and that declarations with external linkage can
refer to something defined in a different file, but that's about all
they say about it.

When the language was standardized, a lot more thought was put into it.
In C89, Section 2.1.1.2 describes the phases of translation of a
program, and phase 8 is described the link step (though it does not name
it as such): "All external object and function references are resolved.
Library components are linked to satisfy external references to
functions and objects not defined in the current translation. All such
translator output is collected into a program image which contains
information needed for execution in its execution environment."

In the second edition, K&R was brought into line with the latest draft
version of what would become C89. As a result, A.12 contains the
following simplified version of that specification: "The result is
translated, then linked together with other programs and libraries, by
collecting the necessary programs and data, and connecting external
functions and object references to their definitions."


> The compiler can provide definitions for H--which is the only symbol
> missing a definition in the situation statement, IIRC--/to satisfy the
> situation/.

C89 3.7 says "... If an identifier declared with external linkage is
used in an expression (other than as part of the operand of a sizeof
operator), somewhere in the entire program there shall be exactly one
external definition for the identifier; otherwise, there shall be no
more than one."

Violation of a "shall" that occurs outside of a constraints section
means that the behavior is undefined, which in turn means that the C
standard imposes no requirements on the behavior of such a program. No
diagnostic is required, nor is the translation required to fail, so
Richard is wrong on those points.
Because the behavior is undefined, anything is permitted, including
providing a definition of H when the program itself contains none - but
it most certainly isn't required to do so, and I doubt that any normal C
compiler would do so.

I try my best to avoid olcott messages. Does he specify that his
nonsense requires an implementation that takes advantage of undefined
behavior in that fashion?

[toc] | [prev] | [next] | [standalone]


Page 11 of 15 — ← Prev page 1 … 9 10 [11] 12 13 … 15  Next page →

Back to top | Article view | comp.theory


csiph-web