Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.theory > #117472 > unrolled thread
| Started by | olcott <polcott333@gmail.com> |
|---|---|
| First post | 2025-05-04 21:23 -0500 |
| Last post | 2025-05-06 22:07 -0400 |
| Articles | 20 on this page of 628 — 16 participants |
Back to article view | Back to comp.theory
Formal systems that cannot possibly be incomplete except for unknowns and unknowable olcott <polcott333@gmail.com> - 2025-05-04 21:23 -0500
Re: Formal systems that cannot possibly be incomplete except for unknowns and unknowable Mikko <mikko.levanto@iki.fi> - 2025-05-05 10:01 +0300
Re: Formal systems that cannot possibly be incomplete except for unknowns and unknowable Alan Mackenzie <acm@muc.de> - 2025-05-05 10:47 +0000
Re: Formal systems that cannot possibly be incomplete except for unknowns and unknowable olcott <polcott333@gmail.com> - 2025-05-05 10:33 -0500
Re: Formal systems that cannot possibly be incomplete except for unknowns and unknowable Alan Mackenzie <acm@muc.de> - 2025-05-05 16:05 +0000
Re: Formal systems that cannot possibly be incomplete except for unknowns and unknowable olcott <polcott333@gmail.com> - 2025-05-05 12:30 -0500
Re: Formal systems that cannot possibly be incomplete except for unknowns and unknowable Alan Mackenzie <acm@muc.de> - 2025-05-05 18:19 +0000
Re: Formal systems that cannot possibly be incomplete except for unknowns and unknowable olcott <polcott333@gmail.com> - 2025-05-05 13:44 -0500
Re: Formal systems that cannot possibly be incomplete except for unknowns and unknowable Alan Mackenzie <acm@muc.de> - 2025-05-05 18:52 +0000
Re: Formal systems that cannot possibly be incomplete except for unknowns and unknowable olcott <polcott333@gmail.com> - 2025-05-05 14:22 -0500
Re: Formal systems that cannot possibly be incomplete except for unknowns and unknowable Alan Mackenzie <acm@muc.de> - 2025-05-05 19:34 +0000
Re: Formal systems that cannot possibly be incomplete except for unknowns and unknowable olcott <polcott333@gmail.com> - 2025-05-05 14:52 -0500
Re: Formal systems that cannot possibly be incomplete except for unknowns and unknowable Alan Mackenzie <acm@muc.de> - 2025-05-05 20:12 +0000
Re: Formal systems that cannot possibly be incomplete except for unknowns and unknowable olcott <polcott333@gmail.com> - 2025-05-05 16:03 -0500
Re: Formal systems that cannot possibly be incomplete except for unknowns and unknowable Alan Mackenzie <acm@muc.de> - 2025-05-06 08:30 +0000
Re: Formal systems that cannot possibly be incomplete except for unknowns and unknowable olcott <polcott333@gmail.com> - 2025-05-06 09:43 -0500
Re: Formal systems that cannot possibly be incomplete except for unknowns and unknowable Richard Damon <richard@damon-family.org> - 2025-05-06 21:57 -0400
Re: Formal systems that cannot possibly be incomplete except for unknowns and unknowable joes <noreply@example.org> - 2025-05-06 10:04 +0000
Re: Formal systems that cannot possibly be incomplete except for unknowns and unknowable olcott <polcott333@gmail.com> - 2025-05-06 12:14 -0500
Re: Formal systems that cannot possibly be incomplete except for unknowns and unknowable Richard Damon <richard@damon-family.org> - 2025-05-06 22:01 -0400
Re: Formal systems that cannot possibly be incomplete except for unknowns and unknowable Mikko <mikko.levanto@iki.fi> - 2025-05-07 10:52 +0300
Re: Formal systems that cannot possibly be incomplete except for unknowns and unknowable Richard Damon <richard@damon-family.org> - 2025-05-05 07:04 -0400
Re: Formal systems that cannot possibly be incomplete except for unknowns and unknowable Mr Flibble <flibble@red-dwarf.jmc.corp> - 2025-05-05 14:46 +0000
Re: Formal systems that cannot possibly be incomplete except for unknowns and unknowable Richard Heathfield <rjh@cpax.org.uk> - 2025-05-05 16:51 +0100
Re: Formal systems that cannot possibly be incomplete except for unknowns and unknowable Mr Flibble <flibble@red-dwarf.jmc.corp> - 2025-05-05 16:10 +0000
Re: Formal systems that cannot possibly be incomplete except for unknowns and unknowable Richard Heathfield <rjh@cpax.org.uk> - 2025-05-05 17:59 +0100
Re: Formal systems that cannot possibly be incomplete except for unknowns and unknowable Richard Damon <richard@damon-family.org> - 2025-05-05 21:08 -0400
Re: Formal systems that cannot possibly be incomplete except for unknowns and unknowable olcott <polcott333@gmail.com> - 2025-05-05 10:31 -0500
Re: Formal systems that cannot possibly be incomplete except for unknowns and unknowable Richard Damon <richard@damon-family.org> - 2025-05-05 21:11 -0400
Re: Formal systems that cannot possibly be incomplete except for unknowns and unknowable olcott <polcott333@gmail.com> - 2025-05-05 21:26 -0500
Re: Formal systems that cannot possibly be incomplete except for unknowns and unknowable Richard Damon <richard@damon-family.org> - 2025-05-06 07:16 -0400
Re: Formal systems that cannot possibly be incomplete except for unknowns and unknowable olcott <polcott333@gmail.com> - 2025-05-05 23:27 -0500
Re: Formal systems that cannot possibly be incomplete except for unknowns and unknowable Alan Mackenzie <acm@muc.de> - 2025-05-06 08:17 +0000
Re: Formal systems that cannot possibly be incomplete except for unknowns and unknowable olcott <polcott333@gmail.com> - 2025-05-06 09:36 -0500
Re: Formal systems that cannot possibly be incomplete except for unknowns and unknowable Alan Mackenzie <acm@muc.de> - 2025-05-06 15:38 +0000
Re: Formal systems that cannot possibly be incomplete except for unknowns and unknowable Richard Heathfield <rjh@cpax.org.uk> - 2025-05-06 17:16 +0100
Re: Formal systems that cannot possibly be incomplete except for unknowns and unknowable Ben Bacarisse <ben@bsb.me.uk> - 2025-05-07 17:01 +0100
Re: Formal systems that cannot possibly be incomplete except for unknowns and unknowable Richard Heathfield <rjh@cpax.org.uk> - 2025-05-07 17:22 +0100
Re: Formal systems that cannot possibly be incomplete except for unknowns and unknowable Mr Flibble <flibble@red-dwarf.jmc.corp> - 2025-05-07 17:11 +0000
Re: Formal systems that cannot possibly be incomplete except for unknowns and unknowable Richard Heathfield <rjh@cpax.org.uk> - 2025-05-07 18:51 +0100
Re: Formal systems that cannot possibly be incomplete except for unknowns and unknowable Richard Heathfield <rjh@cpax.org.uk> - 2025-05-07 18:59 +0100
Re: Formal systems that cannot possibly be incomplete except for unknowns and unknowable Ben Bacarisse <ben@bsb.me.uk> - 2025-05-09 01:58 +0100
Re: Formal systems that cannot possibly be incomplete except for unknowns and unknowable Richard Heathfield <rjh@cpax.org.uk> - 2025-05-09 05:43 +0100
Re: Formal systems that cannot possibly be incomplete except for unknowns and unknowable olcott <polcott333@gmail.com> - 2025-05-07 12:55 -0500
Re: Formal systems that cannot possibly be incomplete except for unknowns and unknowable Richard Heathfield <rjh@cpax.org.uk> - 2025-05-07 19:14 +0100
Re: Formal systems that cannot possibly be incomplete except for unknowns and unknowable Mr Flibble <flibble@red-dwarf.jmc.corp> - 2025-05-07 18:17 +0000
Re: Formal systems that cannot possibly be incomplete except for unknowns and unknowable Richard Heathfield <rjh@cpax.org.uk> - 2025-05-07 19:32 +0100
Re: Formal systems that cannot possibly be incomplete except for unknowns and unknowable Mr Flibble <flibble@red-dwarf.jmc.corp> - 2025-05-07 19:11 +0000
Re: Formal systems that cannot possibly be incomplete except for unknowns and unknowable Richard Heathfield <rjh@cpax.org.uk> - 2025-05-07 22:23 +0100
Re: Formal systems that cannot possibly be incomplete except for unknowns and unknowable olcott <polcott333@gmail.com> - 2025-05-07 13:31 -0500
Re: Formal systems that cannot possibly be incomplete except for unknowns and unknowable dbush <dbush.mobile@gmail.com> - 2025-05-07 14:32 -0400
Re: Formal systems that cannot possibly be incomplete except for unknowns and unknowable Richard Heathfield <rjh@cpax.org.uk> - 2025-05-07 19:59 +0100
Re: Formal systems that cannot possibly be incomplete except for unknowns and unknowable olcott <polcott333@gmail.com> - 2025-05-07 14:35 -0500
Re: Formal systems that cannot possibly be incomplete except for unknowns and unknowable Richard Heathfield <rjh@cpax.org.uk> - 2025-05-07 22:30 +0100
Re: Formal systems that cannot possibly be incomplete except for unknowns and unknowable olcott <polcott333@gmail.com> - 2025-05-07 16:46 -0500
Re: Formal systems that cannot possibly be incomplete except for unknowns and unknowable dbush <dbush.mobile@gmail.com> - 2025-05-07 17:47 -0400
Re: Formal systems that cannot possibly be incomplete except for unknowns and unknowable olcott <polcott333@gmail.com> - 2025-05-07 16:56 -0500
Re: Formal systems that cannot possibly be incomplete except for unknowns and unknowable dbush <dbush.mobile@gmail.com> - 2025-05-07 18:05 -0400
Re: Formal systems that cannot possibly be incomplete except for unknowns and unknowable olcott <polcott333@gmail.com> - 2025-05-07 18:05 -0500
Re: Formal systems that cannot possibly be incomplete except for unknowns and unknowable dbush <dbush.mobile@gmail.com> - 2025-05-07 19:10 -0400
Re: Formal systems that cannot possibly be incomplete except for unknowns and unknowable olcott <polcott333@gmail.com> - 2025-05-07 18:16 -0500
Re: Formal systems that cannot possibly be incomplete except for unknowns and unknowable dbush <dbush.mobile@gmail.com> - 2025-05-07 19:18 -0400
Re: Formal systems that cannot possibly be incomplete except for unknowns and unknowable olcott <polcott333@gmail.com> - 2025-05-07 18:26 -0500
Re: Formal systems that cannot possibly be incomplete except for unknowns and unknowable dbush <dbush.mobile@gmail.com> - 2025-05-07 19:31 -0400
Re: Formal systems that cannot possibly be incomplete except for unknowns and unknowable olcott <polcott333@gmail.com> - 2025-05-07 18:39 -0500
Re: Formal systems that cannot possibly be incomplete except for unknowns and unknowable dbush <dbush.mobile@gmail.com> - 2025-05-07 20:14 -0400
Re: Formal systems that cannot possibly be incomplete except for unknowns and unknowable olcott <polcott333@gmail.com> - 2025-05-07 18:40 -0500
Re: Formal systems that cannot possibly be incomplete except for unknowns and unknowable dbush <dbush.mobile@gmail.com> - 2025-05-07 20:15 -0400
Re: Formal systems that cannot possibly be incomplete except for unknowns and unknowable olcott <polcott333@gmail.com> - 2025-05-07 19:19 -0500
Re: Formal systems that cannot possibly be incomplete except for unknowns and unknowable dbush <dbush.mobile@gmail.com> - 2025-05-07 20:44 -0400
Re: Formal systems that cannot possibly be incomplete except for unknowns and unknowable olcott <polcott333@gmail.com> - 2025-05-07 20:20 -0500
Re: Formal systems that cannot possibly be incomplete except for unknowns and unknowable dbush <dbush.mobile@gmail.com> - 2025-05-07 21:30 -0400
Re: Formal systems that cannot possibly be incomplete except for unknowns and unknowable olcott <polcott333@gmail.com> - 2025-05-07 20:48 -0500
Re: Formal systems that cannot possibly be incomplete except for unknowns and unknowable dbush <dbush.mobile@gmail.com> - 2025-05-07 21:59 -0400
Re: Formal systems that cannot possibly be incomplete except for unknowns and unknowable Richard Heathfield <rjh@cpax.org.uk> - 2025-05-08 05:09 +0100
Re: Formal systems that cannot possibly be incomplete except for unknowns and unknowable olcott <polcott333@gmail.com> - 2025-05-08 00:22 -0500
Re: Formal systems that cannot possibly be incomplete except for unknowns and unknowable Richard Heathfield <rjh@cpax.org.uk> - 2025-05-08 06:33 +0100
Re: Formal systems that cannot possibly be incomplete except for unknowns and unknowable Mike Terry <news.dead.person.stones@darjeeling.plus.com> - 2025-05-08 17:14 +0100
Incorrect requirements --- Computing the mapping from the input to HHH(DD) olcott <polcott333@gmail.com> - 2025-05-08 12:00 -0500
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) "Fred. Zwarts" <F.Zwarts@HetNet.nl> - 2025-05-08 21:04 +0200
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) olcott <polcott333@gmail.com> - 2025-05-08 14:42 -0500
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) Richard Heathfield <rjh@cpax.org.uk> - 2025-05-08 21:01 +0100
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) Mr Flibble <flibble@red-dwarf.jmc.corp> - 2025-05-08 21:35 +0000
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) Richard Heathfield <rjh@cpax.org.uk> - 2025-05-08 23:12 +0100
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2025-05-08 15:26 -0700
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2025-05-08 15:31 -0700
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) olcott <polcott333@gmail.com> - 2025-05-08 17:47 -0500
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2025-05-08 16:45 -0700
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) olcott <polcott333@gmail.com> - 2025-05-08 18:53 -0500
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2025-05-08 17:00 -0700
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) olcott <polcott333@gmail.com> - 2025-05-08 19:14 -0500
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) Richard Damon <richard@damon-family.org> - 2025-05-08 21:07 -0400
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) olcott <polcott333@gmail.com> - 2025-05-08 20:33 -0500
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) Richard Damon <richard@damon-family.org> - 2025-05-08 22:11 -0400
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2025-05-08 18:54 -0700
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) Richard Heathfield <rjh@cpax.org.uk> - 2025-05-09 05:50 +0100
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) olcott <polcott333@gmail.com> - 2025-05-09 00:01 -0500
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) Richard Heathfield <rjh@cpax.org.uk> - 2025-05-09 06:23 +0100
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) Richard Damon <richard@damon-family.org> - 2025-05-09 06:52 -0400
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) "Fred. Zwarts" <F.Zwarts@HetNet.nl> - 2025-05-09 10:41 +0200
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) olcott <polcott333@gmail.com> - 2025-05-09 10:39 -0500
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) Richard Damon <richard@damon-family.org> - 2025-05-09 12:50 -0400
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) "Fred. Zwarts" <F.Zwarts@HetNet.nl> - 2025-05-10 09:39 +0200
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) Richard Damon <richard@damon-family.org> - 2025-05-08 21:02 -0400
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2025-05-08 19:23 -0700
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) olcott <polcott333@gmail.com> - 2025-05-08 21:28 -0500
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2025-05-08 21:18 -0700
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) Richard Damon <news.x.richarddamon@xoxy.net> - 2025-05-08 23:01 -0400
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2025-05-08 21:22 -0700
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) olcott <polcott333@gmail.com> - 2025-05-08 23:56 -0500
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) Richard Damon <richard@damon-family.org> - 2025-05-09 07:00 -0400
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) Richard Damon <richard@damon-family.org> - 2025-05-09 06:59 -0400
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) olcott <polcott333@gmail.com> - 2025-05-09 10:16 -0500
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) Richard Damon <richard@damon-family.org> - 2025-05-09 12:52 -0400
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) olcott <polcott333@gmail.com> - 2025-05-09 09:52 -0500
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) Richard Damon <richard@damon-family.org> - 2025-05-09 12:57 -0400
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) "Fred. Zwarts" <F.Zwarts@HetNet.nl> - 2025-05-10 09:59 +0200
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) "Fred. Zwarts" <F.Zwarts@HetNet.nl> - 2025-05-09 10:47 +0200
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) olcott <polcott333@gmail.com> - 2025-05-09 10:48 -0500
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) Richard Damon <richard@damon-family.org> - 2025-05-09 13:00 -0400
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) olcott <polcott333@gmail.com> - 2025-05-09 14:46 -0500
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) Richard Heathfield <rjh@cpax.org.uk> - 2025-05-09 21:07 +0100
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) olcott <polcott333@gmail.com> - 2025-05-09 15:15 -0500
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) Richard Damon <richard@damon-family.org> - 2025-05-09 17:35 -0400
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) Richard Heathfield <rjh@cpax.org.uk> - 2025-05-09 22:40 +0100
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) olcott <polcott333@gmail.com> - 2025-05-09 17:18 -0500
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) dbush <dbush.mobile@gmail.com> - 2025-05-09 18:31 -0400
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) Richard Damon <richard@damon-family.org> - 2025-05-09 19:34 -0400
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) Richard Heathfield <rjh@cpax.org.uk> - 2025-05-10 01:26 +0100
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2025-05-09 20:14 -0700
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2025-05-09 19:40 -0700
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) wij <wyniijj5@gmail.com> - 2025-05-10 11:13 +0800
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) olcott <polcott333@gmail.com> - 2025-05-09 22:24 -0500
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) wij <wyniijj5@gmail.com> - 2025-05-10 11:43 +0800
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) olcott <polcott333@gmail.com> - 2025-05-09 23:18 -0500
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) wij <wyniijj5@gmail.com> - 2025-05-10 12:32 +0800
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) olcott <polcott333@gmail.com> - 2025-05-09 23:44 -0500
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) wij <wyniijj5@gmail.com> - 2025-05-10 12:51 +0800
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) olcott <polcott333@gmail.com> - 2025-05-10 00:06 -0500
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) wij <wyniijj5@gmail.com> - 2025-05-10 13:13 +0800
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) olcott <polcott333@gmail.com> - 2025-05-10 00:19 -0500
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) wij <wyniijj5@gmail.com> - 2025-05-10 13:27 +0800
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) olcott <polcott333@gmail.com> - 2025-05-10 00:41 -0500
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) wij <wyniijj5@gmail.com> - 2025-05-10 14:00 +0800
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) olcott <polcott333@gmail.com> - 2025-05-10 01:06 -0500
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) wij <wyniijj5@gmail.com> - 2025-05-10 14:19 +0800
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) olcott <polcott333@gmail.com> - 2025-05-10 09:51 -0500
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) dbush <dbush.mobile@gmail.com> - 2025-05-10 11:01 -0400
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) "Fred. Zwarts" <F.Zwarts@HetNet.nl> - 2025-05-10 17:14 +0200
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) wij <wyniijj5@gmail.com> - 2025-05-10 23:14 +0800
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) olcott <polcott333@gmail.com> - 2025-05-10 10:43 -0500
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) wij <wyniijj5@gmail.com> - 2025-05-11 00:00 +0800
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) olcott <polcott333@gmail.com> - 2025-05-10 11:15 -0500
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) dbush <dbush.mobile@gmail.com> - 2025-05-10 12:18 -0400
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) wij <wyniijj5@gmail.com> - 2025-05-11 00:21 +0800
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) olcott <polcott333@gmail.com> - 2025-05-10 11:44 -0500
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) dbush <dbush.mobile@gmail.com> - 2025-05-10 12:55 -0400
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) Richard Heathfield <rjh@cpax.org.uk> - 2025-05-10 17:34 +0100
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) "Fred. Zwarts" <F.Zwarts@HetNet.nl> - 2025-05-10 18:05 +0200
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) Richard Heathfield <rjh@cpax.org.uk> - 2025-05-10 17:07 +0100
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) "Fred. Zwarts" <F.Zwarts@HetNet.nl> - 2025-05-10 10:30 +0200
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) dbush <dbush.mobile@gmail.com> - 2025-05-10 08:39 -0400
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) dbush <dbush.mobile@gmail.com> - 2025-05-10 08:37 -0400
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) dbush <dbush.mobile@gmail.com> - 2025-05-10 08:36 -0400
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) Richard Damon <richard@damon-family.org> - 2025-05-10 15:16 -0400
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) Richard Damon <richard@damon-family.org> - 2025-05-10 08:54 -0400
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) Richard Damon <richard@damon-family.org> - 2025-05-10 08:53 -0400
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) Richard Damon <richard@damon-family.org> - 2025-05-09 23:53 -0400
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) olcott <polcott333@gmail.com> - 2025-05-09 23:13 -0500
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) dbush <dbush.mobile@gmail.com> - 2025-05-10 00:18 -0400
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) "Fred. Zwarts" <F.Zwarts@HetNet.nl> - 2025-05-10 10:25 +0200
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) Richard Damon <richard@damon-family.org> - 2025-05-10 08:59 -0400
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) "Fred. Zwarts" <F.Zwarts@HetNet.nl> - 2025-05-10 10:22 +0200
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) Richard Damon <richard@damon-family.org> - 2025-05-09 23:31 -0400
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) olcott <polcott333@gmail.com> - 2025-05-09 23:21 -0500
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) "Fred. Zwarts" <F.Zwarts@HetNet.nl> - 2025-05-10 10:34 +0200
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) Richard Heathfield <rjh@cpax.org.uk> - 2025-05-10 09:42 +0100
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) Richard Damon <richard@damon-family.org> - 2025-05-10 09:09 -0400
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) olcott <polcott333@gmail.com> - 2025-05-09 22:13 -0500
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) Richard Damon <richard@damon-family.org> - 2025-05-09 23:45 -0400
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) "Fred. Zwarts" <F.Zwarts@HetNet.nl> - 2025-05-10 10:18 +0200
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) Richard Heathfield <rjh@cpax.org.uk> - 2025-05-10 11:24 +0100
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) Richard Damon <richard@damon-family.org> - 2025-05-09 17:34 -0400
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) "Fred. Zwarts" <F.Zwarts@HetNet.nl> - 2025-05-10 10:05 +0200
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) Richard Heathfield <rjh@cpax.org.uk> - 2025-05-10 11:18 +0100
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) Richard Damon <news.x.richarddamon@xoxy.net> - 2025-05-09 13:59 -0400
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) Mike Terry <news.dead.person.stones@darjeeling.plus.com> - 2025-05-10 01:23 +0100
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) olcott <polcott333@gmail.com> - 2025-05-09 19:48 -0500
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) Richard Damon <richard@damon-family.org> - 2025-05-09 22:20 -0400
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) olcott <polcott333@gmail.com> - 2025-05-09 21:41 -0500
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) Richard Heathfield <rjh@cpax.org.uk> - 2025-05-10 03:59 +0100
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) Richard Damon <richard@damon-family.org> - 2025-05-09 23:06 -0400
Repetitive posting [ Was: Incorrect requirements --- Computing the mapping from the input to HHH(DD)] Alan Mackenzie <acm@muc.de> - 2025-05-10 10:21 +0000
Re: Repetitive posting [ Was: Incorrect requirements --- Computing the mapping from the input to HHH(DD)] olcott <polcott333@gmail.com> - 2025-05-10 09:30 -0500
Re: Repetitive posting [ Was: Incorrect requirements --- Computing the mapping from the input to HHH(DD)] dbush <dbush.mobile@gmail.com> - 2025-05-10 10:57 -0400
Re: Repetitive posting [ Was: Incorrect requirements --- Computing the mapping from the input to HHH(DD)] "Fred. Zwarts" <F.Zwarts@HetNet.nl> - 2025-05-10 16:57 +0200
Re: Repetitive posting [ Was: Incorrect requirements --- Computing the mapping from the input to HHH(DD)] Richard Damon <richard@damon-family.org> - 2025-05-10 15:21 -0400
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) "Fred. Zwarts" <F.Zwarts@HetNet.nl> - 2025-05-10 10:38 +0200
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2025-05-09 20:12 -0700
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) olcott <polcott333@gmail.com> - 2025-05-09 22:17 -0500
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) Richard Damon <richard@damon-family.org> - 2025-05-09 23:29 -0400
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) olcott <polcott333@gmail.com> - 2025-05-09 23:27 -0500
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) "Fred. Zwarts" <F.Zwarts@HetNet.nl> - 2025-05-10 10:44 +0200
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) Richard Damon <richard@damon-family.org> - 2025-05-10 09:15 -0400
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) Richard Damon <richard@damon-family.org> - 2025-05-10 15:23 -0400
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) "Fred. Zwarts" <F.Zwarts@HetNet.nl> - 2025-05-10 10:42 +0200
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) Richard Heathfield <rjh@cpax.org.uk> - 2025-05-09 05:35 +0100
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2025-05-08 22:18 -0700
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) Richard Heathfield <rjh@cpax.org.uk> - 2025-05-09 06:41 +0100
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) "Fred. Zwarts" <F.Zwarts@HetNet.nl> - 2025-05-09 10:39 +0200
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) olcott <polcott333@gmail.com> - 2025-05-09 10:33 -0500
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) joes <noreply@example.org> - 2025-05-09 15:42 +0000
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) olcott <polcott333@gmail.com> - 2025-05-09 10:53 -0500
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) Richard Damon <richard@damon-family.org> - 2025-05-09 14:06 -0400
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) Richard Damon <richard@damon-family.org> - 2025-05-09 13:58 -0400
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) "Fred. Zwarts" <F.Zwarts@HetNet.nl> - 2025-05-10 10:46 +0200
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) olcott <polcott333@gmail.com> - 2025-05-09 10:41 -0500
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) Richard Damon <richard@damon-family.org> - 2025-05-09 14:08 -0400
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) olcott <polcott333@gmail.com> - 2025-05-08 17:50 -0500
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) Richard Heathfield <rjh@cpax.org.uk> - 2025-05-09 00:30 +0100
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) olcott <polcott333@gmail.com> - 2025-05-08 18:41 -0500
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) Richard Heathfield <rjh@cpax.org.uk> - 2025-05-09 00:46 +0100
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2025-05-08 16:54 -0700
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) olcott <polcott333@gmail.com> - 2025-05-08 19:05 -0500
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) Richard Damon <richard@damon-family.org> - 2025-05-08 21:13 -0400
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) olcott <polcott333@gmail.com> - 2025-05-08 20:35 -0500
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2025-05-08 19:14 -0700
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) Richard Heathfield <rjh@cpax.org.uk> - 2025-05-09 06:10 +0100
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2025-05-08 22:37 -0700
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) Richard Damon <richard@damon-family.org> - 2025-05-08 22:13 -0400
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) "Fred. Zwarts" <F.Zwarts@HetNet.nl> - 2025-05-09 11:03 +0200
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) olcott <polcott333@gmail.com> - 2025-05-09 11:02 -0500
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) Richard Damon <richard@damon-family.org> - 2025-05-09 14:09 -0400
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) "Fred. Zwarts" <F.Zwarts@HetNet.nl> - 2025-05-10 10:49 +0200
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2025-05-08 19:02 -0700
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) olcott <polcott333@gmail.com> - 2025-05-08 21:22 -0500
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) Richard Damon <richard@damon-family.org> - 2025-05-08 22:30 -0400
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) Bonita Montero <Bonita.Montero@gmail.com> - 2025-05-10 14:37 +0200
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) olcott <polcott333@gmail.com> - 2025-05-10 09:33 -0500
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) "Fred. Zwarts" <F.Zwarts@HetNet.nl> - 2025-05-10 16:54 +0200
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) wij <wyniijj5@gmail.com> - 2025-05-10 23:28 +0800
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) olcott <polcott333@gmail.com> - 2025-05-10 10:45 -0500
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) wij <wyniijj5@gmail.com> - 2025-05-11 00:06 +0800
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) olcott <polcott333@gmail.com> - 2025-05-10 11:19 -0500
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) dbush <dbush.mobile@gmail.com> - 2025-05-10 12:21 -0400
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) wij <wyniijj5@gmail.com> - 2025-05-11 00:29 +0800
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) olcott <polcott333@gmail.com> - 2025-05-10 11:47 -0500
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) wij <wyniijj5@gmail.com> - 2025-05-11 01:01 +0800
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) olcott <polcott333@gmail.com> - 2025-05-10 12:17 -0500
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) dbush <dbush.mobile@gmail.com> - 2025-05-10 13:19 -0400
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) wij <wyniijj5@gmail.com> - 2025-05-11 02:09 +0800
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) olcott <polcott333@gmail.com> - 2025-05-10 13:17 -0500
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) dbush <dbush.mobile@gmail.com> - 2025-05-10 14:24 -0400
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) wij <wyniijj5@gmail.com> - 2025-05-11 02:37 +0800
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) olcott <polcott333@gmail.com> - 2025-05-10 13:47 -0500
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) wij <wyniijj5@gmail.com> - 2025-05-11 03:02 +0800
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) olcott <polcott333@gmail.com> - 2025-05-10 14:29 -0500
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) wij <wyniijj5@gmail.com> - 2025-05-11 05:44 +0800
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) olcott <polcott333@gmail.com> - 2025-05-10 17:03 -0500
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) dbush <dbush.mobile@gmail.com> - 2025-05-10 18:39 -0400
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) Mr Flibble <flibble@red-dwarf.jmc.corp> - 2025-05-10 22:55 +0000
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) dbush <dbush.mobile@gmail.com> - 2025-05-10 19:03 -0400
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) Mr Flibble <flibble@red-dwarf.jmc.corp> - 2025-05-10 23:35 +0000
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) Richard Damon <richard@damon-family.org> - 2025-05-10 18:57 -0400
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) wij <wyniijj5@gmail.com> - 2025-05-11 09:17 +0800
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) olcott <polcott333@gmail.com> - 2025-05-10 20:26 -0500
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) Richard Heathfield <rjh@cpax.org.uk> - 2025-05-11 02:43 +0100
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) wij <wyniijj5@gmail.com> - 2025-05-11 09:44 +0800
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) olcott <polcott333@gmail.com> - 2025-05-10 20:56 -0500
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) wij <wyniijj5@gmail.com> - 2025-05-11 10:09 +0800
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) olcott <polcott333@gmail.com> - 2025-05-10 21:19 -0500
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) Richard Damon <richard@damon-family.org> - 2025-05-11 07:03 -0400
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) wij <wyniijj5@gmail.com> - 2025-05-11 22:34 +0800
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) olcott <polcott333@gmail.com> - 2025-05-11 10:38 -0500
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) wij <wyniijj5@gmail.com> - 2025-05-12 00:28 +0800
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) olcott <polcott333@gmail.com> - 2025-05-11 12:00 -0500
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) wij <wyniijj5@gmail.com> - 2025-05-12 01:21 +0800
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) olcott <polcott333@gmail.com> - 2025-05-11 12:40 -0500
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) dbush <dbush.mobile@gmail.com> - 2025-05-11 13:44 -0400
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) wij <wyniijj5@gmail.com> - 2025-05-12 02:38 +0800
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) olcott <polcott333@gmail.com> - 2025-05-11 15:19 -0500
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) dbush <dbush.mobile@gmail.com> - 2025-05-11 16:21 -0400
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) wij <wyniijj5@gmail.com> - 2025-05-12 04:23 +0800
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) olcott <polcott333@gmail.com> - 2025-05-11 15:50 -0500
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) olcott <polcott333@gmail.com> - 2025-05-11 15:53 -0500
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) dbush <dbush.mobile@gmail.com> - 2025-05-11 17:01 -0400
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) wij <wyniijj5@gmail.com> - 2025-05-12 05:48 +0800
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) olcott <polcott333@gmail.com> - 2025-05-11 17:00 -0500
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) olcott <polcott333@gmail.com> - 2025-05-11 17:05 -0500
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) wij <wyniijj5@gmail.com> - 2025-05-12 06:11 +0800
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) olcott <polcott333@gmail.com> - 2025-05-11 17:30 -0500
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) wij <wyniijj5@gmail.com> - 2025-05-12 06:50 +0800
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) olcott <polcott333@gmail.com> - 2025-05-11 18:08 -0500
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) wij <wyniijj5@gmail.com> - 2025-05-12 08:33 +0800
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) olcott <polcott333@gmail.com> - 2025-05-11 19:51 -0500
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) Richard Damon <richard@damon-family.org> - 2025-05-11 21:15 -0400
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) olcott <polcott333@gmail.com> - 2025-05-11 20:51 -0500
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) dbush <dbush.mobile@gmail.com> - 2025-05-11 21:56 -0400
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) Richard Damon <richard@damon-family.org> - 2025-05-12 22:30 -0400
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) joes <noreply@example.org> - 2025-05-16 15:38 +0000
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) olcott <polcott333@gmail.com> - 2025-05-16 10:50 -0500
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) Richard Damon <richard@damon-family.org> - 2025-05-16 12:04 -0400
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) Mikko <mikko.levanto@iki.fi> - 2025-05-17 11:09 +0300
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) dbush <dbush.mobile@gmail.com> - 2025-05-11 19:59 -0400
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) --- DOS detector olcott <polcott333@gmail.com> - 2025-05-11 19:57 -0500
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) --- DOS detector dbush <dbush.mobile@gmail.com> - 2025-05-11 21:01 -0400
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) --- DOS detector joes <noreply@example.org> - 2025-05-12 09:22 +0000
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) --- DOS detector olcott <polcott333@gmail.com> - 2025-05-12 10:58 -0500
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) Richard Damon <richard@damon-family.org> - 2025-05-11 19:34 -0400
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) Richard Damon <richard@damon-family.org> - 2025-05-11 17:06 -0400
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) Mikko <mikko.levanto@iki.fi> - 2025-05-12 11:03 +0300
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) olcott <polcott333@gmail.com> - 2025-05-12 10:04 -0500
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) dbush <dbush.mobile@gmail.com> - 2025-05-12 11:06 -0400
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) olcott <polcott333@gmail.com> - 2025-05-12 11:19 -0500
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) dbush <dbush.mobile@gmail.com> - 2025-05-12 12:41 -0400
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) olcott <polcott333@gmail.com> - 2025-05-12 11:54 -0500
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) dbush <dbush.mobile@gmail.com> - 2025-05-12 13:07 -0400
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) olcott <polcott333@gmail.com> - 2025-05-12 12:16 -0500
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) dbush <dbush.mobile@gmail.com> - 2025-05-12 13:30 -0400
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) olcott <polcott333@gmail.com> - 2025-05-12 12:58 -0500
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) dbush <dbush.mobile@gmail.com> - 2025-05-12 14:19 -0400
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) "Fred. Zwarts" <F.Zwarts@HetNet.nl> - 2025-05-13 13:23 +0200
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) Mikko <mikko.levanto@iki.fi> - 2025-05-13 13:19 +0300
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) joes <noreply@example.org> - 2025-05-12 21:29 +0000
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) Richard Damon <Richard@Damon-Family.org> - 2025-05-12 23:10 -0400
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) Richard Damon <richard@damon-family.org> - 2025-05-11 16:25 -0400
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) Ben Bacarisse <ben@bsb.me.uk> - 2025-05-12 17:46 +0100
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) olcott <polcott333@gmail.com> - 2025-05-12 12:23 -0500
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) Richard Damon <richard@damon-family.org> - 2025-05-12 22:38 -0400
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) Richard Damon <Richard@Damon-Family.org> - 2025-05-12 23:11 -0400
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) Richard Damon <richard@damon-family.org> - 2025-05-10 22:12 -0400
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) Richard Damon <richard@damon-family.org> - 2025-05-10 21:54 -0400
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) joes <noreply@example.org> - 2025-05-11 11:07 +0000
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) olcott <polcott333@gmail.com> - 2025-05-11 11:37 -0500
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) Richard Damon <richard@damon-family.org> - 2025-05-11 16:36 -0400
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) olcott <polcott333@gmail.com> - 2025-05-11 16:13 -0500
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) Richard Damon <richard@damon-family.org> - 2025-05-11 19:36 -0400
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) "Fred. Zwarts" <F.Zwarts@HetNet.nl> - 2025-05-13 13:20 +0200
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) Richard Damon <richard@damon-family.org> - 2025-05-10 18:52 -0400
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) Richard Damon <richard@damon-family.org> - 2025-05-10 15:32 -0400
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) Richard Damon <richard@damon-family.org> - 2025-05-10 15:25 -0400
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) Alan Mackenzie <acm@muc.de> - 2025-05-10 18:48 +0000
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) olcott <polcott333@gmail.com> - 2025-05-10 13:56 -0500
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) dbush <dbush.mobile@gmail.com> - 2025-05-10 15:03 -0400
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) Richard Damon <richard@damon-family.org> - 2025-05-10 15:33 -0400
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) Mr Flibble <flibble@red-dwarf.jmc.corp> - 2025-05-10 18:58 +0000
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) Alan Mackenzie <acm@muc.de> - 2025-05-10 20:07 +0000
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) Mr Flibble <flibble@red-dwarf.jmc.corp> - 2025-05-10 20:17 +0000
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) olcott <polcott333@gmail.com> - 2025-05-10 15:29 -0500
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) Richard Damon <richard@damon-family.org> - 2025-05-10 18:58 -0400
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) Alan Mackenzie <acm@muc.de> - 2025-05-11 10:34 +0000
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) Mr Flibble <flibble@red-dwarf.jmc.corp> - 2025-05-11 11:48 +0000
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) Richard Heathfield <rjh@cpax.org.uk> - 2025-05-11 12:57 +0100
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) Mr Flibble <flibble@red-dwarf.jmc.corp> - 2025-05-11 12:09 +0000
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) Richard Heathfield <rjh@cpax.org.uk> - 2025-05-11 13:12 +0100
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) Mr Flibble <flibble@red-dwarf.jmc.corp> - 2025-05-11 12:17 +0000
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) Richard Heathfield <rjh@cpax.org.uk> - 2025-05-11 13:36 +0100
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) Mr Flibble <flibble@red-dwarf.jmc.corp> - 2025-05-11 12:41 +0000
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) Richard Heathfield <rjh@cpax.org.uk> - 2025-05-11 14:58 +0100
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) olcott <polcott333@gmail.com> - 2025-05-11 10:44 -0500
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) Richard Heathfield <rjh@cpax.org.uk> - 2025-05-11 16:49 +0100
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) Richard Damon <richard@damon-family.org> - 2025-05-11 16:50 -0400
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) olcott <polcott333@gmail.com> - 2025-05-11 10:14 -0500
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) Richard Heathfield <rjh@cpax.org.uk> - 2025-05-11 16:27 +0100
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) olcott <polcott333@gmail.com> - 2025-05-10 15:26 -0500
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) Alan Mackenzie <acm@muc.de> - 2025-05-10 20:45 +0000
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) olcott <polcott333@gmail.com> - 2025-05-10 15:58 -0500
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) dbush <dbush.mobile@gmail.com> - 2025-05-10 17:01 -0400
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) Richard Damon <richard@damon-family.org> - 2025-05-10 19:23 -0400
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) Richard Damon <richard@damon-family.org> - 2025-05-10 19:04 -0400
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) Richard Heathfield <rjh@cpax.org.uk> - 2025-05-10 21:27 +0100
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) Alan Mackenzie <acm@muc.de> - 2025-05-10 20:22 +0000
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) olcott <polcott333@gmail.com> - 2025-05-10 15:42 -0500
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) dbush <dbush.mobile@gmail.com> - 2025-05-10 16:50 -0400
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) Richard Damon <richard@damon-family.org> - 2025-05-10 19:27 -0400
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) joes <noreply@example.org> - 2025-05-11 11:13 +0000
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) olcott <polcott333@gmail.com> - 2025-05-11 11:44 -0500
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) dbush <dbush.mobile@gmail.com> - 2025-05-11 12:52 -0400
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) olcott <polcott333@gmail.com> - 2025-05-11 12:35 -0500
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) dbush <dbush.mobile@gmail.com> - 2025-05-11 13:43 -0400
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) "Fred. Zwarts" <F.Zwarts@HetNet.nl> - 2025-05-13 13:10 +0200
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) Richard Heathfield <rjh@cpax.org.uk> - 2025-05-11 18:11 +0100
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) Mike Terry <news.dead.person.stones@darjeeling.plus.com> - 2025-05-12 01:38 +0100
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) olcott <polcott333@gmail.com> - 2025-05-11 19:48 -0500
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) dbush <dbush.mobile@gmail.com> - 2025-05-11 20:58 -0400
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) olcott <polcott333@gmail.com> - 2025-05-11 20:05 -0500
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) dbush <dbush.mobile@gmail.com> - 2025-05-11 21:07 -0400
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) Richard Damon <richard@damon-family.org> - 2025-05-11 21:40 -0400
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) olcott <polcott333@gmail.com> - 2025-05-11 21:11 -0500
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) Richard Damon <richard@damon-family.org> - 2025-05-12 22:39 -0400
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) Richard Damon <richard@damon-family.org> - 2025-05-11 21:27 -0400
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) olcott <polcott333@gmail.com> - 2025-05-11 20:56 -0500
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) dbush <dbush.mobile@gmail.com> - 2025-05-11 21:59 -0400
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) olcott <polcott333@gmail.com> - 2025-05-11 21:14 -0500
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) dbush <dbush.mobile@gmail.com> - 2025-05-11 22:28 -0400
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) olcott <polcott333@gmail.com> - 2025-05-11 21:36 -0500
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) dbush <dbush.mobile@gmail.com> - 2025-05-11 22:38 -0400
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) olcott <polcott333@gmail.com> - 2025-05-11 21:46 -0500
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) dbush <dbush.mobile@gmail.com> - 2025-05-11 22:49 -0400
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) olcott <polcott333@gmail.com> - 2025-05-11 21:56 -0500
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) dbush <dbush.mobile@gmail.com> - 2025-05-11 22:57 -0400
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) olcott <polcott333@gmail.com> - 2025-05-11 22:00 -0500
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) dbush <dbush.mobile@gmail.com> - 2025-05-11 23:03 -0400
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) olcott <polcott333@gmail.com> - 2025-05-11 22:36 -0500
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) dbush <dbush.mobile@gmail.com> - 2025-05-11 23:39 -0400
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) olcott <polcott333@gmail.com> - 2025-05-11 22:50 -0500
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) dbush <dbush.mobile@gmail.com> - 2025-05-11 23:54 -0400
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) olcott <polcott333@gmail.com> - 2025-05-11 23:11 -0500
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) dbush <dbush.mobile@gmail.com> - 2025-05-12 07:46 -0400
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) olcott <polcott333@gmail.com> - 2025-05-12 11:32 -0500
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) dbush <dbush.mobile@gmail.com> - 2025-05-12 12:45 -0400
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) joes <noreply@example.org> - 2025-05-12 21:27 +0000
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) "Fred. Zwarts" <F.Zwarts@HetNet.nl> - 2025-05-13 13:01 +0200
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) "Fred. Zwarts" <F.Zwarts@HetNet.nl> - 2025-05-13 13:05 +0200
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) Richard Damon <richard@damon-family.org> - 2025-05-12 22:44 -0400
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) Richard Damon <richard@damon-family.org> - 2025-05-12 22:42 -0400
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) Richard Heathfield <rjh@cpax.org.uk> - 2025-05-12 02:25 +0100
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) Ben Bacarisse <ben@bsb.me.uk> - 2025-05-12 18:03 +0100
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) Ben Bacarisse <ben@bsb.me.uk> - 2025-05-12 18:05 +0100
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) Richard Heathfield <rjh@cpax.org.uk> - 2025-05-12 19:13 +0100
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) Ben Bacarisse <ben@bsb.me.uk> - 2025-05-13 01:18 +0100
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) Richard Heathfield <rjh@cpax.org.uk> - 2025-05-13 03:38 +0100
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) Richard Heathfield <rjh@cpax.org.uk> - 2025-05-12 19:06 +0100
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) Mike Terry <news.dead.person.stones@darjeeling.plus.com> - 2025-05-13 03:17 +0100
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) olcott <polcott333@gmail.com> - 2025-05-12 21:32 -0500
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) Richard Damon <richard@damon-family.org> - 2025-05-12 22:59 -0400
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) "Fred. Zwarts" <F.Zwarts@HetNet.nl> - 2025-05-13 12:58 +0200
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) Richard Heathfield <rjh@cpax.org.uk> - 2025-05-13 03:41 +0100
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) joes <noreply@example.org> - 2025-05-13 09:01 +0000
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) Mike Terry <news.dead.person.stones@darjeeling.plus.com> - 2025-05-13 18:46 +0100
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) olcott <polcott333@gmail.com> - 2025-05-13 16:04 -0500
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) Richard Damon <richard@damon-family.org> - 2025-05-13 18:45 -0400
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) dbush <dbush.mobile@gmail.com> - 2025-05-13 20:58 -0400
How the requirements that Professor Sipser agreed to are exactly met olcott <polcott333@gmail.com> - 2025-05-13 20:07 -0500
Re: How the requirements that Professor Sipser agreed to are exactly met dbush <dbush.mobile@gmail.com> - 2025-05-13 21:19 -0400
Re: How the requirements that Professor Sipser agreed to are exactly met olcott <polcott333@gmail.com> - 2025-05-13 20:40 -0500
Re: How the requirements that Professor Sipser agreed to are exactly met dbush <dbush.mobile@gmail.com> - 2025-05-13 21:45 -0400
Re: How the requirements that Professor Sipser agreed to are exactly met olcott <polcott333@gmail.com> - 2025-05-13 20:55 -0500
Re: How the requirements that Professor Sipser agreed to are exactly met dbush <dbush.mobile@gmail.com> - 2025-05-13 21:58 -0400
Re: How the requirements that Professor Sipser agreed to are exactly met olcott <polcott333@gmail.com> - 2025-05-13 21:43 -0500
Re: How the requirements that Professor Sipser agreed to are exactly met dbush <dbush.mobile@gmail.com> - 2025-05-13 22:44 -0400
Re: How the requirements that Professor Sipser agreed to are exactly met olcott <polcott333@gmail.com> - 2025-05-13 22:18 -0500
Re: How the requirements that Professor Sipser agreed to are exactly met dbush <dbush.mobile@gmail.com> - 2025-05-13 23:35 -0400
Re: How the requirements that Professor Sipser agreed to are exactly met joes <noreply@example.org> - 2025-05-14 08:17 +0000
Re: How the requirements that Professor Sipser agreed to are exactly met olcott <polcott333@gmail.com> - 2025-05-14 10:06 -0500
Re: How the requirements that Professor Sipser agreed to are exactly met joes <noreply@example.org> - 2025-05-14 18:37 +0000
Re: How the requirements that Professor Sipser agreed to are exactly met olcott <polcott333@gmail.com> - 2025-05-14 13:42 -0500
Re: How the requirements that Professor Sipser agreed to are exactly met Richard Heathfield <rjh@cpax.org.uk> - 2025-05-14 19:56 +0100
Re: How the requirements that Professor Sipser agreed to are exactly met olcott <polcott333@gmail.com> - 2025-05-14 14:02 -0500
Re: How the requirements that Professor Sipser agreed to are exactly met Richard Heathfield <rjh@cpax.org.uk> - 2025-05-14 20:17 +0100
Re: How the requirements that Professor Sipser agreed to are exactly met olcott <polcott333@gmail.com> - 2025-05-14 14:21 -0500
Re: How the requirements that Professor Sipser agreed to are exactly met Richard Heathfield <rjh@cpax.org.uk> - 2025-05-14 20:49 +0100
Re: How the requirements that Professor Sipser agreed to are exactly met olcott <polcott333@gmail.com> - 2025-05-14 15:00 -0500
Re: How the requirements that Professor Sipser agreed to are exactly met Richard Heathfield <rjh@cpax.org.uk> - 2025-05-14 21:18 +0100
Re: How the requirements that Professor Sipser agreed to are exactly met olcott <polcott333@gmail.com> - 2025-05-14 15:25 -0500
Re: How the requirements that Professor Sipser agreed to are exactly met Richard Heathfield <rjh@cpax.org.uk> - 2025-05-14 21:26 +0100
Re: How the requirements that Professor Sipser agreed to are exactly met joes <noreply@example.org> - 2025-05-14 20:28 +0000
Re: How the requirements that Professor Sipser agreed to are exactly met olcott <polcott333@gmail.com> - 2025-05-14 15:40 -0500
Re: How the requirements that Professor Sipser agreed to are exactly met Richard Heathfield <rjh@cpax.org.uk> - 2025-05-14 21:54 +0100
Re: How the requirements that Professor Sipser agreed to are exactly met Richard Heathfield <rjh@cpax.org.uk> - 2025-05-14 21:51 +0100
Re: How the requirements that Professor Sipser agreed to are exactly met Ben Bacarisse <ben@bsb.me.uk> - 2025-05-14 20:20 +0100
Re: How the requirements that Professor Sipser agreed to are exactly met olcott <polcott333@gmail.com> - 2025-05-14 14:46 -0500
Re: How the requirements that Professor Sipser agreed to are exactly met dbush <dbush.mobile@gmail.com> - 2025-05-14 17:18 -0400
Re: How the requirements that Professor Sipser agreed to are exactly met Richard Damon <richard@damon-family.org> - 2025-05-14 21:51 -0400
Re: How the requirements that Professor Sipser agreed to are exactly met Mike Terry <news.dead.person.stones@darjeeling.plus.com> - 2025-05-15 00:02 +0100
Re: How the requirements that Professor Sipser agreed to are exactly met olcott <polcott333@gmail.com> - 2025-05-14 18:17 -0500
Re: How the requirements that Professor Sipser agreed to are exactly met olcott <polcott333@gmail.com> - 2025-05-14 18:27 -0500
Re: How the requirements that Professor Sipser agreed to are exactly met Ben Bacarisse <ben@bsb.me.uk> - 2025-05-15 01:02 +0100
Re: How the requirements that Professor Sipser agreed to are exactly met olcott <polcott333@gmail.com> - 2025-05-14 19:09 -0500
Re: How the requirements that Professor Sipser agreed to are exactly met Richard Damon <richard@damon-family.org> - 2025-05-14 07:46 -0400
Re: How the requirements that Professor Sipser agreed to are exactly met olcott <polcott333@gmail.com> - 2025-05-14 10:23 -0500
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) joes <noreply@example.org> - 2025-05-11 19:54 +0000
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) Richard Damon <richard@damon-family.org> - 2025-05-11 17:02 -0400
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) olcott <polcott333@gmail.com> - 2025-05-11 16:15 -0500
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) Richard Damon <richard@damon-family.org> - 2025-05-11 19:39 -0400
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) olcott <polcott333@gmail.com> - 2025-05-11 19:29 -0500
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) Richard Damon <richard@damon-family.org> - 2025-05-11 21:31 -0400
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) olcott <polcott333@gmail.com> - 2025-05-11 21:03 -0500
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) dbush <dbush.mobile@gmail.com> - 2025-05-11 22:05 -0400
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) Richard Damon <richard@damon-family.org> - 2025-05-12 22:49 -0400
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) "Fred. Zwarts" <F.Zwarts@HetNet.nl> - 2025-05-13 12:46 +0200
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) "Fred. Zwarts" <F.Zwarts@HetNet.nl> - 2025-05-13 12:48 +0200
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) "Fred. Zwarts" <F.Zwarts@HetNet.nl> - 2025-05-13 13:16 +0200
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) Alan Mackenzie <acm@muc.de> - 2025-05-11 12:26 +0000
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) Mr Flibble <flibble@red-dwarf.jmc.corp> - 2025-05-11 12:34 +0000
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) Alan Mackenzie <acm@muc.de> - 2025-05-11 14:38 +0000
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) olcott <polcott333@gmail.com> - 2025-05-11 10:26 -0500
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) Richard Heathfield <rjh@cpax.org.uk> - 2025-05-11 16:38 +0100
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) dbush <dbush.mobile@gmail.com> - 2025-05-11 11:58 -0400
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) Richard Damon <richard@damon-family.org> - 2025-05-10 15:25 -0400
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) olcott <polcott333@gmail.com> - 2025-05-09 09:45 -0500
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) Richard Damon <richard@damon-family.org> - 2025-05-09 14:13 -0400
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) "Fred. Zwarts" <F.Zwarts@HetNet.nl> - 2025-05-09 11:00 +0200
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) olcott <polcott333@gmail.com> - 2025-05-09 10:59 -0500
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) Richard Damon <richard@damon-family.org> - 2025-05-09 14:15 -0400
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) "Fred. Zwarts" <F.Zwarts@HetNet.nl> - 2025-05-10 10:52 +0200
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2025-05-08 16:49 -0700
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) olcott <polcott333@gmail.com> - 2025-05-08 18:59 -0500
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) Richard Damon <richard@damon-family.org> - 2025-05-08 21:15 -0400
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) olcott <polcott333@gmail.com> - 2025-05-08 20:41 -0500
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) Richard Damon <richard@damon-family.org> - 2025-05-08 22:18 -0400
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2025-05-08 18:30 -0700
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) olcott <polcott333@gmail.com> - 2025-05-08 21:13 -0500
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) Richard Damon <richard@damon-family.org> - 2025-05-08 22:35 -0400
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) Mike Terry <news.dead.person.stones@darjeeling.plus.com> - 2025-05-09 04:14 +0100
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) olcott <polcott333@gmail.com> - 2025-05-08 22:34 -0500
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) joes <noreply@example.org> - 2025-05-09 09:48 +0000
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) olcott <polcott333@gmail.com> - 2025-05-09 10:08 -0500
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) joes <noreply@example.org> - 2025-05-09 15:47 +0000
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) olcott <polcott333@gmail.com> - 2025-05-09 10:57 -0500
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) Richard Damon <richard@damon-family.org> - 2025-05-09 14:22 -0400
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) Richard Damon <richard@damon-family.org> - 2025-05-09 07:12 -0400
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2025-05-08 21:11 -0700
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) olcott <polcott333@gmail.com> - 2025-05-08 23:49 -0500
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2025-05-08 22:31 -0700
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) olcott <polcott333@gmail.com> - 2025-05-09 00:49 -0500
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2025-05-08 23:17 -0700
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) olcott <polcott333@gmail.com> - 2025-05-09 10:03 -0500
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) Richard Damon <richard@damon-family.org> - 2025-05-09 14:24 -0400
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) Richard Damon <richard@damon-family.org> - 2025-05-09 07:21 -0400
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) Richard Damon <richard@damon-family.org> - 2025-05-09 07:18 -0400
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) Richard Damon <richard@damon-family.org> - 2025-05-09 07:15 -0400
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) olcott <polcott333@gmail.com> - 2025-05-09 18:02 -0500
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) Richard Damon <richard@damon-family.org> - 2025-05-09 19:36 -0400
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) olcott <polcott333@gmail.com> - 2025-05-09 18:43 -0500
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) Richard Damon <richard@damon-family.org> - 2025-05-09 20:37 -0400
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) "Fred. Zwarts" <F.Zwarts@HetNet.nl> - 2025-05-10 15:28 +0200
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) Richard Heathfield <rjh@cpax.org.uk> - 2025-05-10 01:29 +0100
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) Richard Damon <richard@damon-family.org> - 2025-05-09 20:38 -0400
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) Richard Heathfield <rjh@cpax.org.uk> - 2025-05-10 01:48 +0100
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) olcott <polcott333@gmail.com> - 2025-05-09 19:54 -0500
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) Richard Damon <richard@damon-family.org> - 2025-05-09 22:25 -0400
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) olcott <polcott333@gmail.com> - 2025-05-09 21:43 -0500
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) Richard Damon <richard@damon-family.org> - 2025-05-09 23:08 -0400
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) olcott <polcott333@gmail.com> - 2025-05-09 19:51 -0500
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) Richard Heathfield <rjh@cpax.org.uk> - 2025-05-10 02:15 +0100
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) olcott <polcott333@gmail.com> - 2025-05-09 20:29 -0500
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) Richard Heathfield <rjh@cpax.org.uk> - 2025-05-10 02:32 +0100
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) olcott <polcott333@gmail.com> - 2025-05-09 20:50 -0500
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) olcott <polcott333@gmail.com> - 2025-05-09 20:48 -0500
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) Richard Heathfield <rjh@cpax.org.uk> - 2025-05-10 03:15 +0100
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) olcott <polcott333@gmail.com> - 2025-05-09 21:20 -0500
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) Richard Damon <richard@damon-family.org> - 2025-05-09 22:39 -0400
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) olcott <polcott333@gmail.com> - 2025-05-09 21:47 -0500
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) Richard Damon <richard@damon-family.org> - 2025-05-09 23:12 -0400
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) olcott <polcott333@gmail.com> - 2025-05-09 23:46 -0500
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) Richard Heathfield <rjh@cpax.org.uk> - 2025-05-10 11:03 +0100
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) "Fred. Zwarts" <F.Zwarts@HetNet.nl> - 2025-05-10 14:57 +0200
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) Richard Damon <richard@damon-family.org> - 2025-05-10 09:17 -0400
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) Richard Damon <richard@damon-family.org> - 2025-05-09 23:10 -0400
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) "Fred. Zwarts" <F.Zwarts@HetNet.nl> - 2025-05-10 14:59 +0200
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) Richard Damon <richard@damon-family.org> - 2025-05-09 22:34 -0400
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) olcott <polcott333@gmail.com> - 2025-05-09 20:50 -0500
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) Richard Heathfield <rjh@cpax.org.uk> - 2025-05-10 03:19 +0100
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) olcott <polcott333@gmail.com> - 2025-05-09 21:27 -0500
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) Richard Damon <richard@damon-family.org> - 2025-05-09 23:17 -0400
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) --- DOUBLE DOG DARE YOU olcott <polcott333@gmail.com> - 2025-05-09 22:29 -0500
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) --- DOUBLE DOG DARE YOU Richard Damon <richard@damon-family.org> - 2025-05-09 23:50 -0400
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) --- DOUBLE DOG DARE YOU olcott <polcott333@gmail.com> - 2025-05-09 23:05 -0500
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) --- DOUBLE DOG DARE YOU Richard Damon <richard@damon-family.org> - 2025-05-10 09:20 -0400
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) "Fred. Zwarts" <F.Zwarts@HetNet.nl> - 2025-05-10 14:55 +0200
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) Richard Damon <richard@damon-family.org> - 2025-05-09 22:32 -0400
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) Richard Damon <richard@damon-family.org> - 2025-05-09 22:30 -0400
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) olcott <polcott333@gmail.com> - 2025-05-09 21:45 -0500
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) Richard Damon <richard@damon-family.org> - 2025-05-09 23:22 -0400
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) "Fred. Zwarts" <F.Zwarts@HetNet.nl> - 2025-05-09 11:14 +0200
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) olcott <polcott333@gmail.com> - 2025-05-09 11:04 -0500
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) Richard Damon <richard@damon-family.org> - 2025-05-09 14:25 -0400
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) olcott <polcott333@gmail.com> - 2025-05-08 16:41 -0500
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) Richard Heathfield <rjh@cpax.org.uk> - 2025-05-08 23:13 +0100
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) olcott <polcott333@gmail.com> - 2025-05-08 17:20 -0500
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) Richard Damon <richard@damon-family.org> - 2025-05-09 07:25 -0400
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) olcott <polcott333@gmail.com> - 2025-05-09 10:55 -0500
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) Richard Damon <richard@damon-family.org> - 2025-05-09 14:29 -0400
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) "Fred. Zwarts" <F.Zwarts@HetNet.nl> - 2025-05-09 10:33 +0200
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) olcott <polcott333@gmail.com> - 2025-05-09 10:29 -0500
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) Richard Damon <richard@damon-family.org> - 2025-05-09 14:32 -0400
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) "Fred. Zwarts" <F.Zwarts@HetNet.nl> - 2025-05-10 09:37 +0200
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) Richard Damon <richard@damon-family.org> - 2025-05-08 19:35 -0400
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) olcott <polcott333@gmail.com> - 2025-05-08 18:48 -0500
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) Richard Damon <richard@damon-family.org> - 2025-05-08 21:18 -0400
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) olcott <polcott333@gmail.com> - 2025-05-08 20:55 -0500
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) Richard Damon <richard@damon-family.org> - 2025-05-08 22:26 -0400
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) "Fred. Zwarts" <F.Zwarts@HetNet.nl> - 2025-05-09 11:28 +0200
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) olcott <polcott333@gmail.com> - 2025-05-09 11:13 -0500
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) Richard Damon <richard@damon-family.org> - 2025-05-09 14:33 -0400
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) "Fred. Zwarts" <F.Zwarts@HetNet.nl> - 2025-05-09 11:25 +0200
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) olcott <polcott333@gmail.com> - 2025-05-09 11:11 -0500
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) Richard Damon <richard@damon-family.org> - 2025-05-09 14:34 -0400
Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) "Fred. Zwarts" <F.Zwarts@HetNet.nl> - 2025-05-10 09:53 +0200
Re: Formal systems that cannot possibly be incomplete except for unknowns and unknowable Richard Heathfield <rjh@cpax.org.uk> - 2025-05-08 18:45 +0100
Re: Formal systems that cannot possibly be incomplete except for unknowns and unknowable Richard Damon <richard@damon-family.org> - 2025-05-08 07:21 -0400
Re: Formal systems that cannot possibly be incomplete except for unknowns and unknowable olcott <polcott333@gmail.com> - 2025-05-07 18:41 -0500
Re: Formal systems that cannot possibly be incomplete except for unknowns and unknowable Richard Heathfield <rjh@cpax.org.uk> - 2025-05-07 22:52 +0100
Re: Formal systems that cannot possibly be incomplete except for unknowns and unknowable olcott <polcott333@gmail.com> - 2025-05-07 16:59 -0500
Re: Formal systems that cannot possibly be incomplete except for unknowns and unknowable Richard Heathfield <rjh@cpax.org.uk> - 2025-05-07 23:16 +0100
Re: Formal systems that cannot possibly be incomplete except for unknowns and unknowable Mr Flibble <flibble@red-dwarf.jmc.corp> - 2025-05-07 22:26 +0000
Re: Formal systems that cannot possibly be incomplete except for unknowns and unknowable Richard Heathfield <rjh@cpax.org.uk> - 2025-05-07 23:29 +0100
Re: Formal systems that cannot possibly be incomplete except for unknowns and unknowable olcott <polcott333@gmail.com> - 2025-05-07 18:09 -0500
Re: Formal systems that cannot possibly be incomplete except for unknowns and unknowable Richard Heathfield <rjh@cpax.org.uk> - 2025-05-08 03:24 +0100
Re: Formal systems that cannot possibly be incomplete except for unknowns and unknowable olcott <polcott333@gmail.com> - 2025-05-07 21:41 -0500
Re: Formal systems that cannot possibly be incomplete except for unknowns and unknowable Richard Heathfield <rjh@cpax.org.uk> - 2025-05-08 05:12 +0100
Re: Formal systems that cannot possibly be incomplete except for unknowns and unknowable Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2025-05-07 21:33 -0700
Re: Formal systems that cannot possibly be incomplete except for unknowns and unknowable olcott <polcott333@gmail.com> - 2025-05-07 23:54 -0500
Re: Formal systems that cannot possibly be incomplete except for unknowns and unknowable Richard Heathfield <rjh@cpax.org.uk> - 2025-05-08 06:02 +0100
Re: faithful simulations [was: Formal systems that cannot possibly be incomplete except for unknowns and unknowable] joes <noreply@example.org> - 2025-05-08 11:07 +0000
Re: Formal systems that cannot possibly be incomplete except for unknowns and unknowable dbush <dbush.mobile@gmail.com> - 2025-05-07 14:18 -0400
Re: Formal systems that cannot possibly be incomplete except for unknowns and unknowable olcott <polcott333@gmail.com> - 2025-05-07 13:35 -0500
Re: Formal systems that cannot possibly be incomplete except for unknowns and unknowable dbush <dbush.mobile@gmail.com> - 2025-05-07 14:38 -0400
Re: Formal systems that cannot possibly be incomplete except for unknowns and unknowable olcott <polcott333@gmail.com> - 2025-05-07 15:03 -0500
Re: Formal systems that cannot possibly be incomplete except for unknowns and unknowable dbush <dbush.mobile@gmail.com> - 2025-05-07 16:07 -0400
Re: Formal systems that cannot possibly be incomplete except for unknowns and unknowable olcott <polcott333@gmail.com> - 2025-05-07 15:39 -0500
Re: Formal systems that cannot possibly be incomplete except for unknowns and unknowable dbush <dbush.mobile@gmail.com> - 2025-05-07 16:53 -0400
Re: Formal systems that cannot possibly be incomplete except for unknowns and unknowable olcott <polcott333@gmail.com> - 2025-05-07 15:58 -0500
Re: Formal systems that cannot possibly be incomplete except for unknowns and unknowable dbush <dbush.mobile@gmail.com> - 2025-05-07 17:03 -0400
Re: Formal systems that cannot possibly be incomplete except for unknowns and unknowable olcott <polcott333@gmail.com> - 2025-05-07 16:24 -0500
Re: Formal systems that cannot possibly be incomplete except for unknowns and unknowable dbush <dbush.mobile@gmail.com> - 2025-05-07 17:29 -0400
Re: Formal systems that cannot possibly be incomplete except for unknowns and unknowable olcott <polcott333@gmail.com> - 2025-05-07 13:03 -0500
Re: Formal systems that cannot possibly be incomplete except for unknowns and unknowable Mikko <mikko.levanto@iki.fi> - 2025-05-08 11:38 +0300
Re: Formal systems that cannot possibly be incomplete except for unknowns and unknowable olcott <polcott333@gmail.com> - 2025-05-06 12:06 -0500
Re: Formal systems that cannot possibly be incomplete except for unknowns and unknowable Mikko <mikko.levanto@iki.fi> - 2025-05-07 11:02 +0300
Re: Formal systems that cannot possibly be incomplete except for unknowns and unknowable Richard Heathfield <rjh@cpax.org.uk> - 2025-05-07 09:19 +0100
Re: Formal systems that cannot possibly be incomplete except for unknowns and unknowable Richard Damon <richard@damon-family.org> - 2025-05-06 22:04 -0400
Re: Formal systems that cannot possibly be incomplete except for unknowns and unknowable Mikko <mikko.levanto@iki.fi> - 2025-05-07 10:57 +0300
Re: Formal systems that cannot possibly be incomplete except for unknowns and unknowable Richard Heathfield <rjh@cpax.org.uk> - 2025-05-07 09:05 +0100
Re: Formal systems that cannot possibly be incomplete except for unknowns and unknowable Richard Damon <richard@damon-family.org> - 2025-05-06 07:20 -0400
Re: Formal systems that cannot possibly be incomplete except for unknowns and unknowable ---ELABORATED olcott <polcott333@gmail.com> - 2025-05-06 12:46 -0500
Re: Formal systems that cannot possibly be incomplete except for unknowns and unknowable ---ELABORATED Richard Damon <richard@damon-family.org> - 2025-05-06 22:07 -0400
Page 21 of 32 — ← Prev page 1 … 19 20 [21] 22 23 … 32 Next page →
| From | dbush <dbush.mobile@gmail.com> |
|---|---|
| Date | 2025-05-11 22:57 -0400 |
| Subject | Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) |
| Message-ID | <vvro20$s0mk$8@dont-email.me> |
| In reply to | #118637 |
On 5/11/2025 10:56 PM, olcott wrote: > On 5/11/2025 9:49 PM, dbush wrote: >> On 5/11/2025 10:46 PM, olcott wrote: >>> On 5/11/2025 9:38 PM, dbush wrote: >>>> On 5/11/2025 10:36 PM, olcott wrote: >>>>> On 5/11/2025 9:28 PM, dbush wrote: >>>>>> On 5/11/2025 10:14 PM, olcott wrote: >>>>>>> On 5/11/2025 8:59 PM, dbush wrote: >>>>>>>> On 5/11/2025 9:56 PM, olcott wrote: >>>>>>>>> On 5/11/2025 8:27 PM, Richard Damon wrote: >>>>>>>>>> On 5/11/25 8:48 PM, olcott wrote: >>>>>>>>>>> On 5/11/2025 7:38 PM, Mike Terry wrote: >>>>>>>>>>>> On 11/05/2025 18:11, Richard Heathfield wrote: >>>>>>>>>>>>> On 11/05/2025 17:44, olcott wrote: >>>>>>>>>>>>>> Any yes/no question where both yes and no are the >>>>>>>>>>>>>> wrong answer is an incorrect polar question. >>>>>>>>>>>>> >>>>>>>>>>>>> Either DD stops or it doesn't (once it's been hacked around >>>>>>>>>>>>> to get it to compile and after we've leeched out all the >>>>>>>>>>>>> dodgy programming). >>>>>>>>>>>> >>>>>>>>>>>> Done that. It still stops. >>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> If the computer cannot correctly decide whether or not DD >>>>>>>>>>>>> halts, >>>>>>>>>>>> >>>>>>>>>>>> The decider says it doesn't stop.. >>>>>>>>>>>> >>>>>>>>>>>>> we have an undecidable computation, >>>>>>>>>>>> >>>>>>>>>>>> No no, that doesn't make sense. DD stops, and there are >>>>>>>>>>>> lots of partial halt deciders that will decide that >>>>>>>>>>>> particular input correctly. PO's DD isn't "undecidable". >>>>>>>>>>>> >>>>>>>>>>>> No single computation can be undecidable, considered on its >>>>>>>>>>>> own! There are only two possibilities: it halts or it >>>>>>>>>>>> doesn't. In either case there is a decider which decides >>>>>>>>>>>> that /one specific input/ correctly. By extension, any >>>>>>>>>>>> finite number of computations is decidable - we just have a >>>>>>>>>>>> giant switch statement followed by returning halts/ >>>>>>>>>>>> neverhalts as appropriate. If the input domain has just n >>>>>>>>>>>> inputs, there are 2^n trivial deciders that together cater >>>>>>>>>>>> for every combination of each input halting or never >>>>>>>>>>>> halting. One of those deciders is a correct decider for >>>>>>>>>>>> that (finite domain) problem. >>>>>>>>>>>> >>>>>>>>>>>> The HP is asking for a TM (or equiv.) that correctly decides >>>>>>>>>>>> EVERY (P,I) in its one finite algorithm. That is what is >>>>>>>>>>>> proven impossible. The trick of having a big switch >>>>>>>>>>>> statement no longer works because there are infinitely many >>>>>>>>>>>> possible inputs. >>>>>>>>>>>> >>>>>>>>>>>> Decidability for just one single input is trivial and not >>>>>>>>>>>> intersting. >>>>>>>>>>>> >>>>>>>>>>>>> and therefore some computations are undecidable, so >>>>>>>>>>>>> Turing's conclusion was right. Who knew? (Apart from >>>>>>>>>>>>> practically everybody else, I mean.) >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> Mike. >>>>>>>>>>> >>>>>>>>>>> DDD emulated by HHH according to the rules of >>>>>>>>>>> the computational language that DD is encoded >>>>>>>>>>> within already proves that the HP "impossible" >>>>>>>>>>> input specifies a non-halting sequence of >>>>>>>>>>> configurations. >>>>>>>>>> >>>>>>>>>> No it doesn't. >>>>>>>>>> >>>>>>>>> >>>>>>>>> _DDD() >>>>>>>>> [00002172] 55 push ebp ; housekeeping >>>>>>>>> [00002173] 8bec mov ebp,esp ; housekeeping >>>>>>>>> [00002175] 6872210000 push 00002172 ; push DDD >>>>>>>>> [0000217a] e853f4ffff call 000015d2 ; call HHH(DDD) >>>>>>>>> [0000217f] 83c404 add esp,+04 >>>>>>>>> [00002182] 5d pop ebp >>>>>>>>> [00002183] c3 ret >>>>>>>>> Size in bytes:(0018) [00002183] >>>>>>>>> >>>>>>>>> Show all the steps of DDD emulated by simulating >>>>>>>>> termination analyzer HHH according to the rules >>>>>>>>> of the x86 language >>>>>>>> >>>>>>>> Which it doesn't do as you have admitted on the record: >>>>>>>> >>>>>>> >>>>>>> I am daring you to show what they should be. >>>>>>> You know you can't because you know you are a liar. >>>>>>> >>>>>> >>>>>> Category error. Algorithm HHH does one thing and one thing only. >>>>>> There is no "what it should be" because it *is* only one thing. >>>>>> >>>>> >>>>> Show the exact sequence of machine address steps of DDD >>>>> such that the DDD emulated by some HHH >>>> >>>> Changing the input is not allowed. >>> >>> There is no change of input you are a liar. >>> >> >> If you change function HHH, you no longer have algorithm DDD, which >> means you're changing the input. >> >> Changing the input is not allowed. > > I am talking about every element of an infinite set > you nitwit. > And in doing so you're changing the input. Changing the input is not allowed.
[toc] | [prev] | [next] | [standalone]
| From | olcott <polcott333@gmail.com> |
|---|---|
| Date | 2025-05-11 22:00 -0500 |
| Subject | Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) |
| Message-ID | <vvro98$sjai$5@dont-email.me> |
| In reply to | #118638 |
On 5/11/2025 9:57 PM, dbush wrote: > On 5/11/2025 10:56 PM, olcott wrote: >> On 5/11/2025 9:49 PM, dbush wrote: >>> On 5/11/2025 10:46 PM, olcott wrote: >>>> On 5/11/2025 9:38 PM, dbush wrote: >>>>> On 5/11/2025 10:36 PM, olcott wrote: >>>>>> On 5/11/2025 9:28 PM, dbush wrote: >>>>>>> On 5/11/2025 10:14 PM, olcott wrote: >>>>>>>> On 5/11/2025 8:59 PM, dbush wrote: >>>>>>>>> On 5/11/2025 9:56 PM, olcott wrote: >>>>>>>>>> On 5/11/2025 8:27 PM, Richard Damon wrote: >>>>>>>>>>> On 5/11/25 8:48 PM, olcott wrote: >>>>>>>>>>>> On 5/11/2025 7:38 PM, Mike Terry wrote: >>>>>>>>>>>>> On 11/05/2025 18:11, Richard Heathfield wrote: >>>>>>>>>>>>>> On 11/05/2025 17:44, olcott wrote: >>>>>>>>>>>>>>> Any yes/no question where both yes and no are the >>>>>>>>>>>>>>> wrong answer is an incorrect polar question. >>>>>>>>>>>>>> >>>>>>>>>>>>>> Either DD stops or it doesn't (once it's been hacked >>>>>>>>>>>>>> around to get it to compile and after we've leeched out >>>>>>>>>>>>>> all the dodgy programming). >>>>>>>>>>>>> >>>>>>>>>>>>> Done that. It still stops. >>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> If the computer cannot correctly decide whether or not DD >>>>>>>>>>>>>> halts, >>>>>>>>>>>>> >>>>>>>>>>>>> The decider says it doesn't stop.. >>>>>>>>>>>>> >>>>>>>>>>>>>> we have an undecidable computation, >>>>>>>>>>>>> >>>>>>>>>>>>> No no, that doesn't make sense. DD stops, and there are >>>>>>>>>>>>> lots of partial halt deciders that will decide that >>>>>>>>>>>>> particular input correctly. PO's DD isn't "undecidable". >>>>>>>>>>>>> >>>>>>>>>>>>> No single computation can be undecidable, considered on its >>>>>>>>>>>>> own! There are only two possibilities: it halts or it >>>>>>>>>>>>> doesn't. In either case there is a decider which decides >>>>>>>>>>>>> that /one specific input/ correctly. By extension, any >>>>>>>>>>>>> finite number of computations is decidable - we just have a >>>>>>>>>>>>> giant switch statement followed by returning halts/ >>>>>>>>>>>>> neverhalts as appropriate. If the input domain has just n >>>>>>>>>>>>> inputs, there are 2^n trivial deciders that together cater >>>>>>>>>>>>> for every combination of each input halting or never >>>>>>>>>>>>> halting. One of those deciders is a correct decider for >>>>>>>>>>>>> that (finite domain) problem. >>>>>>>>>>>>> >>>>>>>>>>>>> The HP is asking for a TM (or equiv.) that correctly >>>>>>>>>>>>> decides EVERY (P,I) in its one finite algorithm. That is >>>>>>>>>>>>> what is proven impossible. The trick of having a big >>>>>>>>>>>>> switch statement no longer works because there are >>>>>>>>>>>>> infinitely many possible inputs. >>>>>>>>>>>>> >>>>>>>>>>>>> Decidability for just one single input is trivial and not >>>>>>>>>>>>> intersting. >>>>>>>>>>>>> >>>>>>>>>>>>>> and therefore some computations are undecidable, so >>>>>>>>>>>>>> Turing's conclusion was right. Who knew? (Apart from >>>>>>>>>>>>>> practically everybody else, I mean.) >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> Mike. >>>>>>>>>>>> >>>>>>>>>>>> DDD emulated by HHH according to the rules of >>>>>>>>>>>> the computational language that DD is encoded >>>>>>>>>>>> within already proves that the HP "impossible" >>>>>>>>>>>> input specifies a non-halting sequence of >>>>>>>>>>>> configurations. >>>>>>>>>>> >>>>>>>>>>> No it doesn't. >>>>>>>>>>> >>>>>>>>>> >>>>>>>>>> _DDD() >>>>>>>>>> [00002172] 55 push ebp ; housekeeping >>>>>>>>>> [00002173] 8bec mov ebp,esp ; housekeeping >>>>>>>>>> [00002175] 6872210000 push 00002172 ; push DDD >>>>>>>>>> [0000217a] e853f4ffff call 000015d2 ; call HHH(DDD) >>>>>>>>>> [0000217f] 83c404 add esp,+04 >>>>>>>>>> [00002182] 5d pop ebp >>>>>>>>>> [00002183] c3 ret >>>>>>>>>> Size in bytes:(0018) [00002183] >>>>>>>>>> >>>>>>>>>> Show all the steps of DDD emulated by simulating >>>>>>>>>> termination analyzer HHH according to the rules >>>>>>>>>> of the x86 language >>>>>>>>> >>>>>>>>> Which it doesn't do as you have admitted on the record: >>>>>>>>> >>>>>>>> >>>>>>>> I am daring you to show what they should be. >>>>>>>> You know you can't because you know you are a liar. >>>>>>>> >>>>>>> >>>>>>> Category error. Algorithm HHH does one thing and one thing only. >>>>>>> There is no "what it should be" because it *is* only one thing. >>>>>>> >>>>>> >>>>>> Show the exact sequence of machine address steps of DDD >>>>>> such that the DDD emulated by some HHH >>>>> >>>>> Changing the input is not allowed. >>>> >>>> There is no change of input you are a liar. >>>> >>> >>> If you change function HHH, you no longer have algorithm DDD, which >>> means you're changing the input. >>> >>> Changing the input is not allowed. >> >> I am talking about every element of an infinite set >> you nitwit. >> > > And in doing so you're changing the input. > > Changing the input is not allowed. OVER YOUR HEAD. All X are Y proves that some X are Y. That some X are Y proves that at least one X is Y. -- Copyright 2024 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]
| From | dbush <dbush.mobile@gmail.com> |
|---|---|
| Date | 2025-05-11 23:03 -0400 |
| Subject | Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) |
| Message-ID | <vvrodu$s0mk$10@dont-email.me> |
| In reply to | #118641 |
On 5/11/2025 11:00 PM, olcott wrote: > On 5/11/2025 9:57 PM, dbush wrote: >> On 5/11/2025 10:56 PM, olcott wrote: >>> On 5/11/2025 9:49 PM, dbush wrote: >>>> On 5/11/2025 10:46 PM, olcott wrote: >>>>> On 5/11/2025 9:38 PM, dbush wrote: >>>>>> On 5/11/2025 10:36 PM, olcott wrote: >>>>>>> On 5/11/2025 9:28 PM, dbush wrote: >>>>>>>> On 5/11/2025 10:14 PM, olcott wrote: >>>>>>>>> On 5/11/2025 8:59 PM, dbush wrote: >>>>>>>>>> On 5/11/2025 9:56 PM, olcott wrote: >>>>>>>>>>> On 5/11/2025 8:27 PM, Richard Damon wrote: >>>>>>>>>>>> On 5/11/25 8:48 PM, olcott wrote: >>>>>>>>>>>>> On 5/11/2025 7:38 PM, Mike Terry wrote: >>>>>>>>>>>>>> On 11/05/2025 18:11, Richard Heathfield wrote: >>>>>>>>>>>>>>> On 11/05/2025 17:44, olcott wrote: >>>>>>>>>>>>>>>> Any yes/no question where both yes and no are the >>>>>>>>>>>>>>>> wrong answer is an incorrect polar question. >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> Either DD stops or it doesn't (once it's been hacked >>>>>>>>>>>>>>> around to get it to compile and after we've leeched out >>>>>>>>>>>>>>> all the dodgy programming). >>>>>>>>>>>>>> >>>>>>>>>>>>>> Done that. It still stops. >>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> If the computer cannot correctly decide whether or not DD >>>>>>>>>>>>>>> halts, >>>>>>>>>>>>>> >>>>>>>>>>>>>> The decider says it doesn't stop.. >>>>>>>>>>>>>> >>>>>>>>>>>>>>> we have an undecidable computation, >>>>>>>>>>>>>> >>>>>>>>>>>>>> No no, that doesn't make sense. DD stops, and there are >>>>>>>>>>>>>> lots of partial halt deciders that will decide that >>>>>>>>>>>>>> particular input correctly. PO's DD isn't "undecidable". >>>>>>>>>>>>>> >>>>>>>>>>>>>> No single computation can be undecidable, considered on >>>>>>>>>>>>>> its own! There are only two possibilities: it halts or it >>>>>>>>>>>>>> doesn't. In either case there is a decider which decides >>>>>>>>>>>>>> that /one specific input/ correctly. By extension, any >>>>>>>>>>>>>> finite number of computations is decidable - we just have >>>>>>>>>>>>>> a giant switch statement followed by returning halts/ >>>>>>>>>>>>>> neverhalts as appropriate. If the input domain has just n >>>>>>>>>>>>>> inputs, there are 2^n trivial deciders that together cater >>>>>>>>>>>>>> for every combination of each input halting or never >>>>>>>>>>>>>> halting. One of those deciders is a correct decider for >>>>>>>>>>>>>> that (finite domain) problem. >>>>>>>>>>>>>> >>>>>>>>>>>>>> The HP is asking for a TM (or equiv.) that correctly >>>>>>>>>>>>>> decides EVERY (P,I) in its one finite algorithm. That is >>>>>>>>>>>>>> what is proven impossible. The trick of having a big >>>>>>>>>>>>>> switch statement no longer works because there are >>>>>>>>>>>>>> infinitely many possible inputs. >>>>>>>>>>>>>> >>>>>>>>>>>>>> Decidability for just one single input is trivial and not >>>>>>>>>>>>>> intersting. >>>>>>>>>>>>>> >>>>>>>>>>>>>>> and therefore some computations are undecidable, so >>>>>>>>>>>>>>> Turing's conclusion was right. Who knew? (Apart from >>>>>>>>>>>>>>> practically everybody else, I mean.) >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> Mike. >>>>>>>>>>>>> >>>>>>>>>>>>> DDD emulated by HHH according to the rules of >>>>>>>>>>>>> the computational language that DD is encoded >>>>>>>>>>>>> within already proves that the HP "impossible" >>>>>>>>>>>>> input specifies a non-halting sequence of >>>>>>>>>>>>> configurations. >>>>>>>>>>>> >>>>>>>>>>>> No it doesn't. >>>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> _DDD() >>>>>>>>>>> [00002172] 55 push ebp ; housekeeping >>>>>>>>>>> [00002173] 8bec mov ebp,esp ; housekeeping >>>>>>>>>>> [00002175] 6872210000 push 00002172 ; push DDD >>>>>>>>>>> [0000217a] e853f4ffff call 000015d2 ; call HHH(DDD) >>>>>>>>>>> [0000217f] 83c404 add esp,+04 >>>>>>>>>>> [00002182] 5d pop ebp >>>>>>>>>>> [00002183] c3 ret >>>>>>>>>>> Size in bytes:(0018) [00002183] >>>>>>>>>>> >>>>>>>>>>> Show all the steps of DDD emulated by simulating >>>>>>>>>>> termination analyzer HHH according to the rules >>>>>>>>>>> of the x86 language >>>>>>>>>> >>>>>>>>>> Which it doesn't do as you have admitted on the record: >>>>>>>>>> >>>>>>>>> >>>>>>>>> I am daring you to show what they should be. >>>>>>>>> You know you can't because you know you are a liar. >>>>>>>>> >>>>>>>> >>>>>>>> Category error. Algorithm HHH does one thing and one thing >>>>>>>> only. There is no "what it should be" because it *is* only one >>>>>>>> thing. >>>>>>>> >>>>>>> >>>>>>> Show the exact sequence of machine address steps of DDD >>>>>>> such that the DDD emulated by some HHH >>>>>> >>>>>> Changing the input is not allowed. >>>>> >>>>> There is no change of input you are a liar. >>>>> >>>> >>>> If you change function HHH, you no longer have algorithm DDD, which >>>> means you're changing the input. >>>> >>>> Changing the input is not allowed. >>> >>> I am talking about every element of an infinite set >>> you nitwit. >>> >> >> And in doing so you're changing the input. >> >> Changing the input is not allowed. > > OVER YOUR HEAD. > All X are Y proves that some X are Y. > That some X are Y proves that at least one X is Y. > > OVER YOUR HEAD. Halt deciders / termination analyzers are required to map the halting function: Given any algorithm (i.e. a fixed immutable sequence of instructions) X described as <X> with input Y: A solution to the halting problem is an algorithm H that computes the following mapping: (<X>,Y) maps to 1 if and only if X(Y) halts when executed directly (<X>,Y) maps to 0 if and only if X(Y) does not halt when executed directly The input to such is a description of an algorithm. Whether or not that algorithm halts when executed directly has a well defined answer. Whether some other algorithm halts or does not halt is irrelevant.
[toc] | [prev] | [next] | [standalone]
| From | olcott <polcott333@gmail.com> |
|---|---|
| Date | 2025-05-11 22:36 -0500 |
| Subject | Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) |
| Message-ID | <vvrqco$sjai$7@dont-email.me> |
| In reply to | #118642 |
On 5/11/2025 10:03 PM, dbush wrote: > On 5/11/2025 11:00 PM, olcott wrote: >> On 5/11/2025 9:57 PM, dbush wrote: >>> On 5/11/2025 10:56 PM, olcott wrote: >>>> On 5/11/2025 9:49 PM, dbush wrote: >>>>> On 5/11/2025 10:46 PM, olcott wrote: >>>>>> On 5/11/2025 9:38 PM, dbush wrote: >>>>>>> On 5/11/2025 10:36 PM, olcott wrote: >>>>>>>> On 5/11/2025 9:28 PM, dbush wrote: >>>>>>>>> On 5/11/2025 10:14 PM, olcott wrote: >>>>>>>>>> On 5/11/2025 8:59 PM, dbush wrote: >>>>>>>>>>> On 5/11/2025 9:56 PM, olcott wrote: >>>>>>>>>>>> On 5/11/2025 8:27 PM, Richard Damon wrote: >>>>>>>>>>>>> On 5/11/25 8:48 PM, olcott wrote: >>>>>>>>>>>>>> On 5/11/2025 7:38 PM, Mike Terry wrote: >>>>>>>>>>>>>>> On 11/05/2025 18:11, Richard Heathfield wrote: >>>>>>>>>>>>>>>> On 11/05/2025 17:44, olcott wrote: >>>>>>>>>>>>>>>>> Any yes/no question where both yes and no are the >>>>>>>>>>>>>>>>> wrong answer is an incorrect polar question. >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> Either DD stops or it doesn't (once it's been hacked >>>>>>>>>>>>>>>> around to get it to compile and after we've leeched out >>>>>>>>>>>>>>>> all the dodgy programming). >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> Done that. It still stops. >>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> If the computer cannot correctly decide whether or not >>>>>>>>>>>>>>>> DD halts, >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> The decider says it doesn't stop.. >>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> we have an undecidable computation, >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> No no, that doesn't make sense. DD stops, and there are >>>>>>>>>>>>>>> lots of partial halt deciders that will decide that >>>>>>>>>>>>>>> particular input correctly. PO's DD isn't "undecidable". >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> No single computation can be undecidable, considered on >>>>>>>>>>>>>>> its own! There are only two possibilities: it halts or it >>>>>>>>>>>>>>> doesn't. In either case there is a decider which decides >>>>>>>>>>>>>>> that /one specific input/ correctly. By extension, any >>>>>>>>>>>>>>> finite number of computations is decidable - we just have >>>>>>>>>>>>>>> a giant switch statement followed by returning halts/ >>>>>>>>>>>>>>> neverhalts as appropriate. If the input domain has just >>>>>>>>>>>>>>> n inputs, there are 2^n trivial deciders that together >>>>>>>>>>>>>>> cater for every combination of each input halting or >>>>>>>>>>>>>>> never halting. One of those deciders is a correct >>>>>>>>>>>>>>> decider for that (finite domain) problem. >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> The HP is asking for a TM (or equiv.) that correctly >>>>>>>>>>>>>>> decides EVERY (P,I) in its one finite algorithm. That is >>>>>>>>>>>>>>> what is proven impossible. The trick of having a big >>>>>>>>>>>>>>> switch statement no longer works because there are >>>>>>>>>>>>>>> infinitely many possible inputs. >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> Decidability for just one single input is trivial and not >>>>>>>>>>>>>>> intersting. >>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> and therefore some computations are undecidable, so >>>>>>>>>>>>>>>> Turing's conclusion was right. Who knew? (Apart from >>>>>>>>>>>>>>>> practically everybody else, I mean.) >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> Mike. >>>>>>>>>>>>>> >>>>>>>>>>>>>> DDD emulated by HHH according to the rules of >>>>>>>>>>>>>> the computational language that DD is encoded >>>>>>>>>>>>>> within already proves that the HP "impossible" >>>>>>>>>>>>>> input specifies a non-halting sequence of >>>>>>>>>>>>>> configurations. >>>>>>>>>>>>> >>>>>>>>>>>>> No it doesn't. >>>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> _DDD() >>>>>>>>>>>> [00002172] 55 push ebp ; housekeeping >>>>>>>>>>>> [00002173] 8bec mov ebp,esp ; housekeeping >>>>>>>>>>>> [00002175] 6872210000 push 00002172 ; push DDD >>>>>>>>>>>> [0000217a] e853f4ffff call 000015d2 ; call HHH(DDD) >>>>>>>>>>>> [0000217f] 83c404 add esp,+04 >>>>>>>>>>>> [00002182] 5d pop ebp >>>>>>>>>>>> [00002183] c3 ret >>>>>>>>>>>> Size in bytes:(0018) [00002183] >>>>>>>>>>>> >>>>>>>>>>>> Show all the steps of DDD emulated by simulating >>>>>>>>>>>> termination analyzer HHH according to the rules >>>>>>>>>>>> of the x86 language >>>>>>>>>>> >>>>>>>>>>> Which it doesn't do as you have admitted on the record: >>>>>>>>>>> >>>>>>>>>> >>>>>>>>>> I am daring you to show what they should be. >>>>>>>>>> You know you can't because you know you are a liar. >>>>>>>>>> >>>>>>>>> >>>>>>>>> Category error. Algorithm HHH does one thing and one thing >>>>>>>>> only. There is no "what it should be" because it *is* only one >>>>>>>>> thing. >>>>>>>>> >>>>>>>> >>>>>>>> Show the exact sequence of machine address steps of DDD >>>>>>>> such that the DDD emulated by some HHH >>>>>>> >>>>>>> Changing the input is not allowed. >>>>>> >>>>>> There is no change of input you are a liar. >>>>>> >>>>> >>>>> If you change function HHH, you no longer have algorithm DDD, which >>>>> means you're changing the input. >>>>> >>>>> Changing the input is not allowed. >>>> >>>> I am talking about every element of an infinite set >>>> you nitwit. >>>> >>> >>> And in doing so you're changing the input. >>> >>> Changing the input is not allowed. >> >> OVER YOUR HEAD. >> All X are Y proves that some X are Y. >> That some X are Y proves that at least one X is Y. >> >> > > OVER YOUR HEAD. > > Halt deciders / termination analyzers are required to map the halting > function: > You try to get away with changing the subject because you know that you are lying about one or more steps of DDD emulated by HHH according to the rules of the x86 language reaching its "ret" instruction simulated final halt state. _DDD() [00002172] 55 push ebp ; housekeeping [00002173] 8bec mov ebp,esp ; housekeeping [00002175] 6872210000 push 00002172 ; push DDD [0000217a] e853f4ffff call 000015d2 ; call HHH(DDD) [0000217f] 83c404 add esp,+04 [00002182] 5d pop ebp [00002183] c3 ret Size in bytes:(0018) [00002183] -- Copyright 2024 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]
| From | dbush <dbush.mobile@gmail.com> |
|---|---|
| Date | 2025-05-11 23:39 -0400 |
| Subject | Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) |
| Message-ID | <vvrqhu$s0mk$11@dont-email.me> |
| In reply to | #118645 |
On 5/11/2025 11:36 PM, olcott wrote: > On 5/11/2025 10:03 PM, dbush wrote: >> On 5/11/2025 11:00 PM, olcott wrote: >>> On 5/11/2025 9:57 PM, dbush wrote: >>>> On 5/11/2025 10:56 PM, olcott wrote: >>>>> On 5/11/2025 9:49 PM, dbush wrote: >>>>>> On 5/11/2025 10:46 PM, olcott wrote: >>>>>>> On 5/11/2025 9:38 PM, dbush wrote: >>>>>>>> On 5/11/2025 10:36 PM, olcott wrote: >>>>>>>>> On 5/11/2025 9:28 PM, dbush wrote: >>>>>>>>>> On 5/11/2025 10:14 PM, olcott wrote: >>>>>>>>>>> On 5/11/2025 8:59 PM, dbush wrote: >>>>>>>>>>>> On 5/11/2025 9:56 PM, olcott wrote: >>>>>>>>>>>>> On 5/11/2025 8:27 PM, Richard Damon wrote: >>>>>>>>>>>>>> On 5/11/25 8:48 PM, olcott wrote: >>>>>>>>>>>>>>> On 5/11/2025 7:38 PM, Mike Terry wrote: >>>>>>>>>>>>>>>> On 11/05/2025 18:11, Richard Heathfield wrote: >>>>>>>>>>>>>>>>> On 11/05/2025 17:44, olcott wrote: >>>>>>>>>>>>>>>>>> Any yes/no question where both yes and no are the >>>>>>>>>>>>>>>>>> wrong answer is an incorrect polar question. >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> Either DD stops or it doesn't (once it's been hacked >>>>>>>>>>>>>>>>> around to get it to compile and after we've leeched out >>>>>>>>>>>>>>>>> all the dodgy programming). >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> Done that. It still stops. >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> If the computer cannot correctly decide whether or not >>>>>>>>>>>>>>>>> DD halts, >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> The decider says it doesn't stop.. >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> we have an undecidable computation, >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> No no, that doesn't make sense. DD stops, and there are >>>>>>>>>>>>>>>> lots of partial halt deciders that will decide that >>>>>>>>>>>>>>>> particular input correctly. PO's DD isn't "undecidable". >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> No single computation can be undecidable, considered on >>>>>>>>>>>>>>>> its own! There are only two possibilities: it halts or >>>>>>>>>>>>>>>> it doesn't. In either case there is a decider which >>>>>>>>>>>>>>>> decides that /one specific input/ correctly. By >>>>>>>>>>>>>>>> extension, any finite number of computations is >>>>>>>>>>>>>>>> decidable - we just have a giant switch statement >>>>>>>>>>>>>>>> followed by returning halts/ neverhalts as appropriate. >>>>>>>>>>>>>>>> If the input domain has just n inputs, there are 2^n >>>>>>>>>>>>>>>> trivial deciders that together cater for every >>>>>>>>>>>>>>>> combination of each input halting or never halting. One >>>>>>>>>>>>>>>> of those deciders is a correct decider for that (finite >>>>>>>>>>>>>>>> domain) problem. >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> The HP is asking for a TM (or equiv.) that correctly >>>>>>>>>>>>>>>> decides EVERY (P,I) in its one finite algorithm. That >>>>>>>>>>>>>>>> is what is proven impossible. The trick of having a big >>>>>>>>>>>>>>>> switch statement no longer works because there are >>>>>>>>>>>>>>>> infinitely many possible inputs. >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> Decidability for just one single input is trivial and >>>>>>>>>>>>>>>> not intersting. >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> and therefore some computations are undecidable, so >>>>>>>>>>>>>>>>> Turing's conclusion was right. Who knew? (Apart from >>>>>>>>>>>>>>>>> practically everybody else, I mean.) >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> Mike. >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> DDD emulated by HHH according to the rules of >>>>>>>>>>>>>>> the computational language that DD is encoded >>>>>>>>>>>>>>> within already proves that the HP "impossible" >>>>>>>>>>>>>>> input specifies a non-halting sequence of >>>>>>>>>>>>>>> configurations. >>>>>>>>>>>>>> >>>>>>>>>>>>>> No it doesn't. >>>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> _DDD() >>>>>>>>>>>>> [00002172] 55 push ebp ; housekeeping >>>>>>>>>>>>> [00002173] 8bec mov ebp,esp ; housekeeping >>>>>>>>>>>>> [00002175] 6872210000 push 00002172 ; push DDD >>>>>>>>>>>>> [0000217a] e853f4ffff call 000015d2 ; call HHH(DDD) >>>>>>>>>>>>> [0000217f] 83c404 add esp,+04 >>>>>>>>>>>>> [00002182] 5d pop ebp >>>>>>>>>>>>> [00002183] c3 ret >>>>>>>>>>>>> Size in bytes:(0018) [00002183] >>>>>>>>>>>>> >>>>>>>>>>>>> Show all the steps of DDD emulated by simulating >>>>>>>>>>>>> termination analyzer HHH according to the rules >>>>>>>>>>>>> of the x86 language >>>>>>>>>>>> >>>>>>>>>>>> Which it doesn't do as you have admitted on the record: >>>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> I am daring you to show what they should be. >>>>>>>>>>> You know you can't because you know you are a liar. >>>>>>>>>>> >>>>>>>>>> >>>>>>>>>> Category error. Algorithm HHH does one thing and one thing >>>>>>>>>> only. There is no "what it should be" because it *is* only one >>>>>>>>>> thing. >>>>>>>>>> >>>>>>>>> >>>>>>>>> Show the exact sequence of machine address steps of DDD >>>>>>>>> such that the DDD emulated by some HHH >>>>>>>> >>>>>>>> Changing the input is not allowed. >>>>>>> >>>>>>> There is no change of input you are a liar. >>>>>>> >>>>>> >>>>>> If you change function HHH, you no longer have algorithm DDD, >>>>>> which means you're changing the input. >>>>>> >>>>>> Changing the input is not allowed. >>>>> >>>>> I am talking about every element of an infinite set >>>>> you nitwit. >>>>> >>>> >>>> And in doing so you're changing the input. >>>> >>>> Changing the input is not allowed. >>> >>> OVER YOUR HEAD. >>> All X are Y proves that some X are Y. >>> That some X are Y proves that at least one X is Y. >>> >>> >> >> OVER YOUR HEAD. >> >> Halt deciders / termination analyzers are required to map the halting >> function: >> > > You try to get away with changing the subject > because you know that you are lying about one > or more steps of DDD emulated by HHH according > to the rules of the x86 language It is you who are changing the subject away from DDD emulated by HHH (not one or more steps of DDD emulated by HHH) which you have admitted for the record is not correct: On 5/5/2025 8:24 AM, dbush wrote: > On 5/4/2025 11:03 PM, dbush wrote: >> On 5/4/2025 10:05 PM, olcott wrote: >>> On 5/4/2025 7:23 PM, Richard Damon wrote: >>>> But HHH doesn't correct emulated DD by those rules, as those rules >>>> do not allow HHH to stop its emulation, >>> >>> Sure they do you freaking moron... >> >> Then show where in the Intel instruction manual that the execution of >> any instruction other than a HLT is allowed to stop instead of >> executing the next instruction. >> >> Failure to do so in your next reply, or within one hour of your next >> post on this newsgroup, will be taken as you official on-the-record >> admission that there is no such allowance and that HHH does NOT >> correctly simulate DD. > > Let the record show that Peter Olcott made the following post in this > newsgroup after the above message: > > On 5/4/2025 11:04 PM, olcott wrote: > > D *WOULD NEVER STOP RUNNING UNLESS* > > indicates that professor Sipser was agreeing > > to hypotheticals AS *NOT CHANGING THE INPUT* > > > > You are taking > > *WOULD NEVER STOP RUNNING UNLESS* > > to mean *NEVER STOPS RUNNING* that is incorrect. > > And has made no attempt after over 9 hours to show where in the Intel > instruction manual that execution is allowed to stop after any > instruction other than HLT. > > Therefore, as per the above criteria: > > LET THE RECORD SHOW > > That Peter Olcott > > Has *officially* admitted > > That DD is NOT correctly simulated by HHH
[toc] | [prev] | [next] | [standalone]
| From | olcott <polcott333@gmail.com> |
|---|---|
| Date | 2025-05-11 22:50 -0500 |
| Subject | Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) |
| Message-ID | <vvrr6u$sjai$8@dont-email.me> |
| In reply to | #118646 |
On 5/11/2025 10:39 PM, dbush wrote: > On 5/11/2025 11:36 PM, olcott wrote: >> >> You try to get away with changing the subject >> because you know that you are lying about one >> or more steps of DDD emulated by HHH according >> to the rules of the x86 language > > It is you who are changing the subject away from DDD emulated by HHH > (not one or more steps of DDD emulated by HHH) which you have admitted > for the record is not correct: > I am only referring to the hypothetical infinite set of pure x86 emulators specified below: One or more steps of DDD emulated by HHH according to the rules of the x86 language cannot possibly reach its "ret" instruction simulated final halt state. _DDD() [00002172] 55 push ebp ; housekeeping [00002173] 8bec mov ebp,esp ; housekeeping [00002175] 6872210000 push 00002172 ; push DDD [0000217a] e853f4ffff call 000015d2 ; call HHH(DDD) [0000217f] 83c404 add esp,+04 [00002182] 5d pop ebp [00002183] c3 ret Size in bytes:(0018) [00002183] -- Copyright 2024 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]
| From | dbush <dbush.mobile@gmail.com> |
|---|---|
| Date | 2025-05-11 23:54 -0400 |
| Subject | Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) |
| Message-ID | <vvrrcr$s0mk$12@dont-email.me> |
| In reply to | #118647 |
On 5/11/2025 11:50 PM, olcott wrote: > On 5/11/2025 10:39 PM, dbush wrote: >> On 5/11/2025 11:36 PM, olcott wrote: >>> >>> You try to get away with changing the subject >>> because you know that you are lying about one >>> or more steps of DDD emulated by HHH according >>> to the rules of the x86 language >> >> It is you who are changing the subject away from DDD emulated by HHH >> (not one or more steps of DDD emulated by HHH) which you have admitted >> for the record is not correct: >> > > I am only referring to the hypothetical infinite > set of pure x86 emulators specified below: > Each of which is processing a distinct, different input. Changing the input is not allowed.
[toc] | [prev] | [next] | [standalone]
| From | olcott <polcott333@gmail.com> |
|---|---|
| Date | 2025-05-11 23:11 -0500 |
| Subject | Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) |
| Message-ID | <vvrse7$sjai$9@dont-email.me> |
| In reply to | #118648 |
On 5/11/2025 10:54 PM, dbush wrote: > On 5/11/2025 11:50 PM, olcott wrote: >> On 5/11/2025 10:39 PM, dbush wrote: >>> On 5/11/2025 11:36 PM, olcott wrote: >>>> >>>> You try to get away with changing the subject >>>> because you know that you are lying about one >>>> or more steps of DDD emulated by HHH according >>>> to the rules of the x86 language >>> >>> It is you who are changing the subject away from DDD emulated by HHH >>> (not one or more steps of DDD emulated by HHH) which you have >>> admitted for the record is not correct: >>> >> >> I am only referring to the hypothetical infinite >> set of pure x86 emulators specified below: >> > > Each of which is processing a distinct, different input. > > Changing the input is not allowed. I am examining all the elements of a infinite set such that each HHH/DDD pair has a specific fixed form. _DDD() [00002172] 55 push ebp ; housekeeping [00002173] 8bec mov ebp,esp ; housekeeping [00002175] 6872210000 push 00002172 ; push DDD [0000217a] e853f4ffff call 000015d2 ; call HHH(DDD) [0000217f] 83c404 add esp,+04 [00002182] 5d pop ebp [00002183] c3 ret Size in bytes:(0018) [00002183] For all x86 emulators HHH that emulate 1 or more x86 instructions of an input there does not exist a DDD (matching the above template) correctly emulated by HHH such that DDD reaches its “ret” instruction final halt state. -- Copyright 2024 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]
| From | dbush <dbush.mobile@gmail.com> |
|---|---|
| Date | 2025-05-12 07:46 -0400 |
| Subject | Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) |
| Message-ID | <vvsn24$12qtp$1@dont-email.me> |
| In reply to | #118649 |
On 5/12/2025 12:11 AM, olcott wrote: > On 5/11/2025 10:54 PM, dbush wrote: >> On 5/11/2025 11:50 PM, olcott wrote: >>> On 5/11/2025 10:39 PM, dbush wrote: >>>> On 5/11/2025 11:36 PM, olcott wrote: >>>>> >>>>> You try to get away with changing the subject >>>>> because you know that you are lying about one >>>>> or more steps of DDD emulated by HHH according >>>>> to the rules of the x86 language >>>> >>>> It is you who are changing the subject away from DDD emulated by HHH >>>> (not one or more steps of DDD emulated by HHH) which you have >>>> admitted for the record is not correct: >>>> >>> >>> I am only referring to the hypothetical infinite >>> set of pure x86 emulators specified below: >>> >> >> Each of which is processing a distinct, different input. >> >> Changing the input is not allowed. > > I am examining all the elements of a infinite set > such that each HHH/DDD pair has a specific fixed form. And each one has a distinctly different input, and as such the halt status of one is unrelated to the halt status of another. Changing the input is not allowed.
[toc] | [prev] | [next] | [standalone]
| From | olcott <polcott333@gmail.com> |
|---|---|
| Date | 2025-05-12 11:32 -0500 |
| Subject | Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) |
| Message-ID | <vvt7qk$14pca$18@dont-email.me> |
| In reply to | #118666 |
On 5/12/2025 6:46 AM, dbush wrote: > On 5/12/2025 12:11 AM, olcott wrote: >> On 5/11/2025 10:54 PM, dbush wrote: >>> On 5/11/2025 11:50 PM, olcott wrote: >>>> On 5/11/2025 10:39 PM, dbush wrote: >>>>> On 5/11/2025 11:36 PM, olcott wrote: >>>>>> >>>>>> You try to get away with changing the subject >>>>>> because you know that you are lying about one >>>>>> or more steps of DDD emulated by HHH according >>>>>> to the rules of the x86 language >>>>> >>>>> It is you who are changing the subject away from DDD emulated by >>>>> HHH (not one or more steps of DDD emulated by HHH) which you have >>>>> admitted for the record is not correct: >>>>> >>>> >>>> I am only referring to the hypothetical infinite >>>> set of pure x86 emulators specified below: >>>> >>> >>> Each of which is processing a distinct, different input. >>> >>> Changing the input is not allowed. >> >> I am examining all the elements of a infinite set >> such that each HHH/DDD pair has a specific fixed form. > > And each one has a distinctly different input, and as such the halt > status of one is unrelated to the halt status of another. > > Changing the input is not allowed. In other words you are clueless about mathematical induction. It is true that when one step of DDD is emulated by HHH that DDD does not halt. It is true that when N steps of DDD are emulated by HHH that DDD does not halt. -- Copyright 2024 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]
| From | dbush <dbush.mobile@gmail.com> |
|---|---|
| Date | 2025-05-12 12:45 -0400 |
| Subject | Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) |
| Message-ID | <vvt8iq$15ceh$11@dont-email.me> |
| In reply to | #118701 |
On 5/12/2025 12:32 PM, olcott wrote: > On 5/12/2025 6:46 AM, dbush wrote: >> On 5/12/2025 12:11 AM, olcott wrote: >>> On 5/11/2025 10:54 PM, dbush wrote: >>>> On 5/11/2025 11:50 PM, olcott wrote: >>>>> On 5/11/2025 10:39 PM, dbush wrote: >>>>>> On 5/11/2025 11:36 PM, olcott wrote: >>>>>>> >>>>>>> You try to get away with changing the subject >>>>>>> because you know that you are lying about one >>>>>>> or more steps of DDD emulated by HHH according >>>>>>> to the rules of the x86 language >>>>>> >>>>>> It is you who are changing the subject away from DDD emulated by >>>>>> HHH (not one or more steps of DDD emulated by HHH) which you have >>>>>> admitted for the record is not correct: >>>>>> >>>>> >>>>> I am only referring to the hypothetical infinite >>>>> set of pure x86 emulators specified below: >>>>> >>>> >>>> Each of which is processing a distinct, different input. >>>> >>>> Changing the input is not allowed. >>> >>> I am examining all the elements of a infinite set >>> such that each HHH/DDD pair has a specific fixed form. >> >> And each one has a distinctly different input, and as such the halt >> status of one is unrelated to the halt status of another. >> >> Changing the input is not allowed. > > In other words you are clueless about mathematical induction. > > It is true that when one step of DDD is emulated by HHH that > DDD does not halt. False. When one instruction of algorithm DDD1 is emulated by algorithm HHH1, algorithm HHH1 is unable to simulate to a final state. When algorithm DDD1 is executed directly, it halts. > > It is true that when N steps of DDD are emulated by HHH that > DDD does not halt. > False. When one instruction of algorithm DDDN is emulated by algorithm HHHN, algorithm HHHN is unable to simulate to a final state. When algorithm DDDN is executed directly, it halts.
[toc] | [prev] | [next] | [standalone]
| From | joes <noreply@example.org> |
|---|---|
| Date | 2025-05-12 21:27 +0000 |
| Subject | Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) |
| Message-ID | <7fe0a59852c293bdfbd1c496c88cbbdde890aef9@i2pn2.org> |
| In reply to | #118701 |
Am Mon, 12 May 2025 11:32:20 -0500 schrieb olcott: > On 5/12/2025 6:46 AM, dbush wrote: >> On 5/12/2025 12:11 AM, olcott wrote: >>> I am examining all the elements of a infinite set such that each >>> HHH/DDD pair has a specific fixed form. >> >> And each one has a distinctly different input, and as such the halt >> status of one is unrelated to the halt status of another. >> >> Changing the input is not allowed. > > In other words you are clueless about mathematical induction. > It is true that when one step of DDD is emulated by HHH that DDD does > not halt. > It is true that when N steps of DDD are emulated by HHH that DDD does > not halt. How many steps are simulated doesn't change whether the direct execution halts or not. HHH takes infinitely many steps to simulate DDD halting. -- Am Sat, 20 Jul 2024 12:35:31 +0000 schrieb WM in sci.math: It is not guaranteed that n+1 exists for every n.
[toc] | [prev] | [next] | [standalone]
| From | "Fred. Zwarts" <F.Zwarts@HetNet.nl> |
|---|---|
| Date | 2025-05-13 13:01 +0200 |
| Subject | Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) |
| Message-ID | <vvv8pr$1p49q$1@dont-email.me> |
| In reply to | #118701 |
Op 12.mei.2025 om 18:32 schreef olcott: > On 5/12/2025 6:46 AM, dbush wrote: >> On 5/12/2025 12:11 AM, olcott wrote: >>> On 5/11/2025 10:54 PM, dbush wrote: >>>> On 5/11/2025 11:50 PM, olcott wrote: >>>>> On 5/11/2025 10:39 PM, dbush wrote: >>>>>> On 5/11/2025 11:36 PM, olcott wrote: >>>>>>> >>>>>>> You try to get away with changing the subject >>>>>>> because you know that you are lying about one >>>>>>> or more steps of DDD emulated by HHH according >>>>>>> to the rules of the x86 language >>>>>> >>>>>> It is you who are changing the subject away from DDD emulated by >>>>>> HHH (not one or more steps of DDD emulated by HHH) which you have >>>>>> admitted for the record is not correct: >>>>>> >>>>> >>>>> I am only referring to the hypothetical infinite >>>>> set of pure x86 emulators specified below: >>>>> >>>> >>>> Each of which is processing a distinct, different input. >>>> >>>> Changing the input is not allowed. >>> >>> I am examining all the elements of a infinite set >>> such that each HHH/DDD pair has a specific fixed form. >> >> And each one has a distinctly different input, and as such the halt >> status of one is unrelated to the halt status of another. >> >> Changing the input is not allowed. > > In other words you are clueless about mathematical induction. > > It is true that when one step of DDD is emulated by HHH that > DDD does not halt. > > It is true that when N steps of DDD are emulated by HHH that > DDD does not halt. > But when enough steps of the *unchanged* DDD are emulated, then DDD does halt, as proven by HHH1. Only when you also change the input, then more steps are needed, but changing the input is not allowed.
[toc] | [prev] | [next] | [standalone]
| From | "Fred. Zwarts" <F.Zwarts@HetNet.nl> |
|---|---|
| Date | 2025-05-13 13:05 +0200 |
| Subject | Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) |
| Message-ID | <vvv92g$1ov7e$4@dont-email.me> |
| In reply to | #118649 |
Op 12.mei.2025 om 06:11 schreef olcott: > On 5/11/2025 10:54 PM, dbush wrote: >> On 5/11/2025 11:50 PM, olcott wrote: >>> On 5/11/2025 10:39 PM, dbush wrote: >>>> On 5/11/2025 11:36 PM, olcott wrote: >>>>> >>>>> You try to get away with changing the subject >>>>> because you know that you are lying about one >>>>> or more steps of DDD emulated by HHH according >>>>> to the rules of the x86 language >>>> >>>> It is you who are changing the subject away from DDD emulated by HHH >>>> (not one or more steps of DDD emulated by HHH) which you have >>>> admitted for the record is not correct: >>>> >>> >>> I am only referring to the hypothetical infinite >>> set of pure x86 emulators specified below: >>> >> >> Each of which is processing a distinct, different input. >> >> Changing the input is not allowed. > > I am examining all the elements of a infinite set > such that each HHH/DDD pair has a specific fixed form. > > _DDD() > [00002172] 55 push ebp ; housekeeping > [00002173] 8bec mov ebp,esp ; housekeeping > [00002175] 6872210000 push 00002172 ; push DDD > [0000217a] e853f4ffff call 000015d2 ; call HHH(DDD) > [0000217f] 83c404 add esp,+04 > [00002182] 5d pop ebp > [00002183] c3 ret > Size in bytes:(0018) [00002183] > > For all x86 emulators HHH that emulate 1 or more x86 instructions > of an input there does not exist a DDD (matching the above template) > correctly emulated by HHH such that DDD reaches its “ret” instruction > final halt state. > > > You are not only examining an infinite set of simulators, but also an infinite set of inputs. For each input you choose a simulator that is just too early to abort its simulation.. A few steps more would cause a natural end of the simulation. Unfortunately, you choose an infinite number of wrong tools. That does not prove anything about the correct behaviour of the inputs.
[toc] | [prev] | [next] | [standalone]
| From | Richard Damon <richard@damon-family.org> |
|---|---|
| Date | 2025-05-12 22:44 -0400 |
| Subject | Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) |
| Message-ID | <83f32b72c499f8bb773bae6086d09a1a039db699@i2pn2.org> |
| In reply to | #118623 |
On 5/11/25 10:14 PM, olcott wrote: > On 5/11/2025 8:59 PM, dbush wrote: >> On 5/11/2025 9:56 PM, olcott wrote: >>> On 5/11/2025 8:27 PM, Richard Damon wrote: >>>> On 5/11/25 8:48 PM, olcott wrote: >>>>> On 5/11/2025 7:38 PM, Mike Terry wrote: >>>>>> On 11/05/2025 18:11, Richard Heathfield wrote: >>>>>>> On 11/05/2025 17:44, olcott wrote: >>>>>>>> Any yes/no question where both yes and no are the >>>>>>>> wrong answer is an incorrect polar question. >>>>>>> >>>>>>> Either DD stops or it doesn't (once it's been hacked around to >>>>>>> get it to compile and after we've leeched out all the dodgy >>>>>>> programming). >>>>>> >>>>>> Done that. It still stops. >>>>>> >>>>>>> >>>>>>> If the computer cannot correctly decide whether or not DD halts, >>>>>> >>>>>> The decider says it doesn't stop.. >>>>>> >>>>>>> we have an undecidable computation, >>>>>> >>>>>> No no, that doesn't make sense. DD stops, and there are lots of >>>>>> partial halt deciders that will decide that particular input >>>>>> correctly. PO's DD isn't "undecidable". >>>>>> >>>>>> No single computation can be undecidable, considered on its own! >>>>>> There are only two possibilities: it halts or it doesn't. In >>>>>> either case there is a decider which decides that /one specific >>>>>> input/ correctly. By extension, any finite number of computations >>>>>> is decidable - we just have a giant switch statement followed by >>>>>> returning halts/neverhalts as appropriate. If the input domain >>>>>> has just n inputs, there are 2^n trivial deciders that together >>>>>> cater for every combination of each input halting or never >>>>>> halting. One of those deciders is a correct decider for that >>>>>> (finite domain) problem. >>>>>> >>>>>> The HP is asking for a TM (or equiv.) that correctly decides EVERY >>>>>> (P,I) in its one finite algorithm. That is what is proven >>>>>> impossible. The trick of having a big switch statement no longer >>>>>> works because there are infinitely many possible inputs. >>>>>> >>>>>> Decidability for just one single input is trivial and not intersting. >>>>>> >>>>>>> and therefore some computations are undecidable, so Turing's >>>>>>> conclusion was right. Who knew? (Apart from practically everybody >>>>>>> else, I mean.) >>>>>> >>>>>> >>>>>> Mike. >>>>> >>>>> DDD emulated by HHH according to the rules of >>>>> the computational language that DD is encoded >>>>> within already proves that the HP "impossible" >>>>> input specifies a non-halting sequence of >>>>> configurations. >>>> >>>> No it doesn't. >>>> >>> >>> _DDD() >>> [00002172] 55 push ebp ; housekeeping >>> [00002173] 8bec mov ebp,esp ; housekeeping >>> [00002175] 6872210000 push 00002172 ; push DDD >>> [0000217a] e853f4ffff call 000015d2 ; call HHH(DDD) >>> [0000217f] 83c404 add esp,+04 >>> [00002182] 5d pop ebp >>> [00002183] c3 ret >>> Size in bytes:(0018) [00002183] >>> >>> Show all the steps of DDD emulated by simulating >>> termination analyzer HHH according to the rules >>> of the x86 language >> >> Which it doesn't do as you have admitted on the record: >> > > I am daring you to show what they should be. > You know you can't because you know you are a liar. > Says the master of projection. Since the input can't be emulated correct past the Call HHH instuction, since the code past that point isn't in the input, Thus, the quesiton is just a category error. You can only correctly emulate programs, which must include all their code, missing code, just an error.
[toc] | [prev] | [next] | [standalone]
| From | Richard Damon <richard@damon-family.org> |
|---|---|
| Date | 2025-05-12 22:42 -0400 |
| Subject | Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) |
| Message-ID | <1a237cee25a04881fe362c6cfd4e809b94ae1277@i2pn2.org> |
| In reply to | #118616 |
On 5/11/25 9:56 PM, olcott wrote: > On 5/11/2025 8:27 PM, Richard Damon wrote: >> On 5/11/25 8:48 PM, olcott wrote: >>> On 5/11/2025 7:38 PM, Mike Terry wrote: >>>> On 11/05/2025 18:11, Richard Heathfield wrote: >>>>> On 11/05/2025 17:44, olcott wrote: >>>>>> Any yes/no question where both yes and no are the >>>>>> wrong answer is an incorrect polar question. >>>>> >>>>> Either DD stops or it doesn't (once it's been hacked around to get >>>>> it to compile and after we've leeched out all the dodgy programming). >>>> >>>> Done that. It still stops. >>>> >>>>> >>>>> If the computer cannot correctly decide whether or not DD halts, >>>> >>>> The decider says it doesn't stop.. >>>> >>>>> we have an undecidable computation, >>>> >>>> No no, that doesn't make sense. DD stops, and there are lots of >>>> partial halt deciders that will decide that particular input >>>> correctly. PO's DD isn't "undecidable". >>>> >>>> No single computation can be undecidable, considered on its own! >>>> There are only two possibilities: it halts or it doesn't. In either >>>> case there is a decider which decides that /one specific input/ >>>> correctly. By extension, any finite number of computations is >>>> decidable - we just have a giant switch statement followed by >>>> returning halts/neverhalts as appropriate. If the input domain has >>>> just n inputs, there are 2^n trivial deciders that together cater >>>> for every combination of each input halting or never halting. One >>>> of those deciders is a correct decider for that (finite domain) >>>> problem. >>>> >>>> The HP is asking for a TM (or equiv.) that correctly decides EVERY >>>> (P,I) in its one finite algorithm. That is what is proven >>>> impossible. The trick of having a big switch statement no longer >>>> works because there are infinitely many possible inputs. >>>> >>>> Decidability for just one single input is trivial and not intersting. >>>> >>>>> and therefore some computations are undecidable, so Turing's >>>>> conclusion was right. Who knew? (Apart from practically everybody >>>>> else, I mean.) >>>> >>>> >>>> Mike. >>> >>> DDD emulated by HHH according to the rules of >>> the computational language that DD is encoded >>> within already proves that the HP "impossible" >>> input specifies a non-halting sequence of >>> configurations. >> >> No it doesn't. >> > > _DDD() > [00002172] 55 push ebp ; housekeeping > [00002173] 8bec mov ebp,esp ; housekeeping > [00002175] 6872210000 push 00002172 ; push DDD > [0000217a] e853f4ffff call 000015d2 ; call HHH(DDD) > [0000217f] 83c404 add esp,+04 > [00002182] 5d pop ebp > [00002183] c3 ret > Size in bytes:(0018) [00002183] Not a valid input, > > Show all the steps of DDD emulated by simulating > termination analyzer HHH according to the rules > of the x86 language where the emulated DDD reaches > its "ret" instruction. Why? That isn't the criteria. > > You can't only because you know that you are > lying about this. No, I am pointing out your stupidity, and you just repeat it to make it more obvious. > > Your static data trick was clever yet your HHH > was not a simulating termination analyzer. > Sure it was. At the outer layer it fully emulates its input. That is more than yours does. Of course, your concept of that is just a category error and a lie.
[toc] | [prev] | [next] | [standalone]
| From | Richard Heathfield <rjh@cpax.org.uk> |
|---|---|
| Date | 2025-05-12 02:25 +0100 |
| Subject | Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) |
| Message-ID | <vvrima$nejb$3@dont-email.me> |
| In reply to | #118593 |
On 12/05/2025 01:38, Mike Terry wrote: > On 11/05/2025 18:11, Richard Heathfield wrote: >> On 11/05/2025 17:44, olcott wrote: >>> Any yes/no question where both yes and no are the >>> wrong answer is an incorrect polar question. >> >> Either DD stops or it doesn't (once it's been hacked around to >> get it to compile and after we've leeched out all the dodgy >> programming). > > Done that. And you still had code left? > It still stops. Okay. >> If the computer cannot correctly decide whether or not DD halts, > > The decider says it doesn't stop.. I said "cannot >>>correctly<<< decide". > >> we have an undecidable computation, > > No no, that doesn't make sense. Agreed. Therefore, even *after* taking out all the dodgy code, the decider must be broken. > DD stops, and there are lots of > partial halt deciders that will decide that particular input > correctly. PO's DD isn't "undecidable". I hear what you're saying (or at least I see what you typed), but if DD's result is so decidable, how come his decider can't correctly decide? > No single computation can be undecidable, considered on its own! > There are only two possibilities: it halts or it doesn't. Or both, it seems. You say it halts (and I would not hesitate to take you at your word if the alternative is to dredge up a Windows system from somewhere). Olcott says it is non-halting. And we both know it /can't/ be both... -- 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 | Ben Bacarisse <ben@bsb.me.uk> |
|---|---|
| Date | 2025-05-12 18:03 +0100 |
| Subject | Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) |
| Message-ID | <877c2loj7b.fsf@bsb.me.uk> |
| In reply to | #118605 |
Richard Heathfield <rjh@cpax.org.uk> writes:
> On 12/05/2025 01:38, Mike Terry wrote:
>> On 11/05/2025 18:11, Richard Heathfield wrote:
...
>>> we have an undecidable computation,
>> No no, that doesn't make sense.
>
> Agreed. Therefore, even *after* taking out all the dodgy code, the decider
> must be broken.
>
>> DD stops, and there are lots of partial halt deciders that will decide
>> that particular input correctly. PO's DD isn't "undecidable".
>
> I hear what you're saying (or at least I see what you typed), but if DD's
> result is so decidable, how come his decider can't correctly decide?
This is just a misunderstand about terms. The fact that some program
gets the answer wrong does not mean that this case is not (correctly)
decidable. Every halting problem instance is decidable. One of these
two programs correctly decides every instance:
int main(int argc, char **argv) { return 0; }
int main(int argc, char **argv) { return 1; }
>> No single computation can be undecidable, considered on its own! There
>> are only two possibilities: it halts or it doesn't.
>
> Or both, it seems. You say it halts (and I would not hesitate to take you at
> your word if the alternative is to dredge up a Windows system from
> somewhere). Olcott says it is non-halting.
>
> And we both know it /can't/ be both...
--
Ben.
[toc] | [prev] | [next] | [standalone]
| From | Ben Bacarisse <ben@bsb.me.uk> |
|---|---|
| Date | 2025-05-12 18:05 +0100 |
| Subject | Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) |
| Message-ID | <871pstoj2n.fsf@bsb.me.uk> |
| In reply to | #118713 |
Ben Bacarisse <ben@bsb.me.uk> writes:
> Richard Heathfield <rjh@cpax.org.uk> writes:
>
>> On 12/05/2025 01:38, Mike Terry wrote:
>>> On 11/05/2025 18:11, Richard Heathfield wrote:
> ...
>>>> we have an undecidable computation,
>>> No no, that doesn't make sense.
>>
>> Agreed. Therefore, even *after* taking out all the dodgy code, the decider
>> must be broken.
>>
>>> DD stops, and there are lots of partial halt deciders that will decide
>>> that particular input correctly. PO's DD isn't "undecidable".
>>
>> I hear what you're saying (or at least I see what you typed), but if DD's
>> result is so decidable, how come his decider can't correctly decide?
>
> This is just a misunderstand about terms. The fact that some program
> gets the answer wrong does not mean that this case is not (correctly)
> decidable. Every halting problem instance is decidable. One of these
> two programs correctly decides every instance:
>
> int main(int argc, char **argv) { return 0; }
> int main(int argc, char **argv) { return 1; }
Sorry. I did not read far enough. Mike makes the same point:
>>> No single computation can be undecidable, considered on its own! There
>>> are only two possibilities: it halts or it doesn't.
>>
>> Or both, it seems. You say it halts (and I would not hesitate to take you at
>> your word if the alternative is to dredge up a Windows system from
>> somewhere). Olcott says it is non-halting.
This is very odd. You know it either halts or it does not halt so what
do you mean by "Or both, it seems."?
>> And we both know it /can't/ be both...
--
Ben.
[toc] | [prev] | [next] | [standalone]
| From | Richard Heathfield <rjh@cpax.org.uk> |
|---|---|
| Date | 2025-05-12 19:13 +0100 |
| Subject | Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) |
| Message-ID | <vvtdou$17c1i$4@dont-email.me> |
| In reply to | #118714 |
On 12/05/2025 18:05, Ben Bacarisse wrote: > Ben Bacarisse <ben@bsb.me.uk> writes: > >> Richard Heathfield <rjh@cpax.org.uk> writes: >> >>> On 12/05/2025 01:38, Mike Terry wrote: <snip> >>>> No single computation can be undecidable, considered on its own! There >>>> are only two possibilities: it halts or it doesn't. >>> >>> Or both, it seems. You say it halts (and I would not hesitate to take you at >>> your word if the alternative is to dredge up a Windows system from >>> somewhere). Olcott says it is non-halting. > > This is very odd. You know it either halts or it does not halt so what > do you mean by "Or both, it seems."? 'Odd' is exactly the word. Mr Olcott claims it never halts, and Mike Terry claims that it halts almost immediately. Perhaps we should send DDD to a robopsychiatrist. More prosaically: In the absence of any Windows systems on which to run the code and see for myself, I'm more inclined to believe Mike Terry than Mr Olcott, so I think we have to conclude that it halts, don't we? -- 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]
Page 21 of 32 — ← Prev page 1 … 19 20 [21] 22 23 … 32 Next page →
Back to top | Article view | comp.theory
csiph-web