Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.theory > #135045
| From | Kaz Kylheku <643-408-1753@kylheku.com> |
|---|---|
| Newsgroups | comp.theory |
| Subject | Re: Kaz does not understand his own code. |
| Date | 2025-11-05 03:33 +0000 |
| Organization | A noiseless patient Spider |
| Message-ID | <20251104192046.639@kylheku.com> (permalink) |
| References | (5 earlier) <20251104134343.652@kylheku.com> <10ee8pf$2rds$1@dont-email.me> <10eebun$3lq7$1@dont-email.me> <20251104183329.967@kylheku.com> <10eeevn$4anq$1@dont-email.me> |
On 2025-11-05, olcott <polcott333@gmail.com> wrote:
> On 11/4/2025 8:43 PM, Kaz Kylheku wrote:
>> On 2025-11-05, olcott <polcott333@gmail.com> wrote:
>>> On 11/4/2025 7:20 PM, Mike Terry wrote:
>>>>
>>>> I don't really see that PO has declined recently - It seems to me he's
>>>> been the way he is for as long as I recall. I would say he's become
>>>> markedly ruder of late, though! Maybe that's all related to his LLMs
>>>> pandering to his delusions and giving him a renewed confidence.
>>>>
>>>>
>>>> Mike.
>>>>
>>>>
>>>
>>> news://news.eternal-september.org/20251103195844.661@kylheku.com
>>>
>>> On 11/3/2025 10:28 PM, Kaz Kylheku wrote:
>>>>
>>>> How about this minimal viable H:
>>>>
>>>> #include <interpret.h> // C interpreter's own API
>>>>
>>>> bool H(fptr P)
>>>> {
>>>> interp *s = interp_init(P);
>>>>
>>>> for (int i = 0; i < 3; i++) {
>>>> if (interp_step(s))
>>>> return true;
>>>> }
>>>>
>>>> return false;
>>>> }
>>>>
>>>> H initializes an interpreter for its argument P.
>>>> Then it applies a very simple abort logic: it
>>>> steps the interpreter state three times. If
>>>> during those three steps, P terminates, it returns
>>>> true. Otherwise it assumes P is nonterminating and
>>>> returns false.
>>>>
>>>> (Pretend that more complicated abort criteria are there.)
>>>>
>>>> The interpreter API consists of primitives built
>>>> into the system, so it isn't traced.
>>>>
>>>> So then we have D:
>>>>
>>>> void D(void)
>>>> {
>>>> if (H(D)) { for (;;); }
>>>> return;
>>>> }
>>>>
>>>> Let's trace H(D). We indicate the simulation levels from 0,
>>>> step numbers from 1 within each level, with a bit of indentation
>>>> to tell apart the levels:
>>>>
>>>
>>> *This is the part that Kaz does not understand*
>>>
>>> i == 0 reaches if (interp_step(s))
>>> i == 1 reaches if (interp_step(s))
>>> i == 2 reaches if (interp_step(s))
>>> i == 3 NEVER reaches if (interp_step(s))
>>>
>>> The whole point is that D simulated by H
>>> cannot possbly reach its own simulated
>>> "return" statement no matter what H does.
>>
>> Yes; this doesn't happen while H is running.
>>
>> So while H does /something/, no matter what H does, that D simulation
>> won't reach the return statement.
>>
>> H has to return zero first and terminate, leaving the simulation
>> abandoned.
>>
>
> Just like leaving the Infinite_loop() abandoned.
Indeed, with the above H, a simulation of /anything/ that does not
terminate within three inter_step steps is abandoned in order
to return false, whether that false is correct or not.
>> That's the one thing that H can "do" which then lets D
>> reach its return statement.
>>
>
> When H has stopped simulating D then a resumption
> of the exact same machine state of this simulation
> would simply be the point where H rejected D.
Yes, but that point is not special to D.
There is nothing in D's specification indicating that it should
stop at that point.
D doesn't even "experience" the stop since it has no real-time
clock or any other world reference.
In our case here, it turns out that three interp_step steps
of D just get D to the start of the for loop inside H.
So that is where it will be restarted.
If we used 4 instead of 3, then D would be stopped more
in the loop, where it has initialized i to 0.
>
>> Then the simulation framework itself picks up that simuation
>> and does the stepping.
>>
>
> If the simulation framework resumes the simulation
> at the exact same machine state with H local i == 3
The simulation state of D is just at the beginning of
the loop inside simualted H; i is about to be initialized
to zero (if I recall correcty; I don't have it quoted in
my edit buffer now).
The i == 3 happened in the "directly executed" H which
has now terminated.
We are not resuming that H!
We are only resuming (== taking over) the simulation
that it left behind.
The top level H is out of the picture. We remember
that it returned false for H(D) though.
> and H already returned to the simulation framework
> then resuming the simulation cannot do anything more
> than immediately return to the simulation framework.
>
>>> If we continue the simulation with the exact
>>> same machine state then H simply returns false
>>> because i == 3.
>>
>> Remember, we are not continuing the top level H,
>> which terminated and returned zero, but the simulated
>> D which is calling the simulated H.
>>
>
> When we actually literally resume the simulation
> then it must be the exact same machine state of
> the whole system at the point just after H returned
> false to the simulation framework.
No, it is not the machine state of the whole system; it is just the
object #<interp0> that was returned to the top-level H when it called
interp_init(P).
This is similar to the slave_state, and slave_stack and other simulation
parameters in the x86_utm.
The simulation carried out by H was never of the whole system, just a
simulation of D. Why would its continuation suddenly be the "the whole
system"?
Anyway, that is not the idea at all.
The framework obtains #<interp0> (because it keeps track of such
objects) and behaves as if it were calling interp_step() on it.
That is all.
> If we don't do exactly this then we are not actually
> resuming anything.
You are talking about capturing a continuation at the point
where H returned, and calling it. That's something else entirely,
and wouldn't make sense.
That would just be repeating the calculation consisting of H
returning to the main function, returning to the framework,
causing that to happen twice.
(I work with languages in which you can do exactly that sort
of thing, incidentally.)
--
TXR Programming Language: http://nongnu.org/txr
Cygnal: Cygwin Native Application Library: http://kylheku.com/cygnal
Mastodon: @Kazinator@mstdn.ca
Back to comp.theory | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
x86utm with "reckoning" code: git repo with published commit. Kaz Kylheku <643-408-1753@kylheku.com> - 2025-10-26 05:29 +0000
Re: x86utm with "reckoning" code: git repo with published commit. Tristan Wibberley <tristan.wibberley+netnews2@alumni.manchester.ac.uk> - 2025-10-26 09:52 +0000
Re: x86utm with "reckoning" code: git repo with published commit. Kaz Kylheku <643-408-1753@kylheku.com> - 2025-10-26 15:20 +0000
Re: x86utm with "reckoning" code: git repo with published commit. "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2025-10-26 12:37 -0700
Re: x86utm with "reckoning" code: git repo with published commit. Kaz Kylheku <643-408-1753@kylheku.com> - 2025-10-26 20:30 +0000
Re: x86utm with "reckoning" code: git repo with published commit. "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2025-10-26 13:43 -0700
Re: x86utm with "reckoning" code: git repo with published commit. "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2025-10-26 13:49 -0700
Re: x86utm with "reckoning" code: git repo with published commit. Kaz Kylheku <643-408-1753@kylheku.com> - 2025-10-26 21:46 +0000
Re: x86utm with "reckoning" code: git repo with published commit. "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2025-10-26 22:16 -0700
Re: x86utm with "reckoning" code: git repo with published commit. "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2025-10-26 22:17 -0700
Re: x86utm with "reckoning" code: git repo with published commit. Mike Terry <news.dead.person.stones@darjeeling.plus.com> - 2025-10-31 04:51 +0000
Re: x86utm with "reckoning" code: git repo with published commit. Kaz Kylheku <643-408-1753@kylheku.com> - 2025-10-31 05:18 +0000
Re: x86utm with "reckoning" code: git repo with published commit. Mike Terry <news.dead.person.stones@darjeeling.plus.com> - 2025-10-31 15:38 +0000
Re: x86utm with "reckoning" code: git repo with published commit. olcott <polcott333@gmail.com> - 2025-10-31 11:14 -0500
Re: x86utm with "reckoning" code: git repo with published commit. Mike Terry <news.dead.person.stones@darjeeling.plus.com> - 2025-10-31 16:35 +0000
Re: x86utm with "reckoning" code: git repo with published commit. olcott <polcott333@gmail.com> - 2025-10-31 11:55 -0500
Re: x86utm with "reckoning" code: git repo with published commit. Richard Damon <Richard@Damon-Family.org> - 2025-10-31 13:51 -0400
Re: x86utm with "reckoning" code: git repo with published commit. Kaz Kylheku <643-408-1753@kylheku.com> - 2025-10-31 18:03 +0000
Re: x86utm with "reckoning" code: git repo with published commit. Richard Damon <Richard@Damon-Family.org> - 2025-10-31 14:10 -0400
Re: x86utm with "reckoning" code: git repo with published commit. olcott <polcott333@gmail.com> - 2025-10-31 11:23 -0500
Re: x86utm with "reckoning" code: git repo with published commit. Richard Damon <Richard@Damon-Family.org> - 2025-10-31 13:19 -0400
Re: x86utm with "reckoning" code: git repo with published commit. Kaz Kylheku <643-408-1753@kylheku.com> - 2025-10-31 17:37 +0000
Re: x86utm with "reckoning" code: git repo with published commit. Mike Terry <news.dead.person.stones@darjeeling.plus.com> - 2025-11-04 18:04 +0000
Re: x86utm with "reckoning" code: git repo with published commit. Kaz Kylheku <643-408-1753@kylheku.com> - 2025-11-04 18:36 +0000
Re: x86utm with "reckoning" code: git repo with published commit. Mike Terry <news.dead.person.stones@darjeeling.plus.com> - 2025-11-04 18:59 +0000
Re: x86utm with "reckoning" code: git repo with published commit. Kaz Kylheku <643-408-1753@kylheku.com> - 2025-11-04 19:36 +0000
Re: x86utm with "reckoning" code: git repo with published commit. Mike Terry <news.dead.person.stones@darjeeling.plus.com> - 2025-11-04 21:03 +0000
Re: x86utm with "reckoning" code: git repo with published commit. Kaz Kylheku <643-408-1753@kylheku.com> - 2025-11-04 21:58 +0000
Re: x86utm with "reckoning" code: git repo with published commit. Mike Terry <news.dead.person.stones@darjeeling.plus.com> - 2025-11-05 01:20 +0000
Kaz does not understand his own code. olcott <polcott333@gmail.com> - 2025-11-04 20:14 -0600
Re: Kaz does not understand his own code. Kaz Kylheku <643-408-1753@kylheku.com> - 2025-11-05 02:43 +0000
Re: Kaz does not understand his own code. olcott <polcott333@gmail.com> - 2025-11-04 21:06 -0600
Re: Kaz does not understand his own code. Kaz Kylheku <643-408-1753@kylheku.com> - 2025-11-05 03:33 +0000
Re: Kaz does not understand his own code. joes <noreply@example.org> - 2025-11-05 07:47 +0000
Re: Kaz does not understand his own code --- I AM PROVED EXACTLY CORRECT olcott <polcott333@gmail.com> - 2025-11-04 21:51 -0600
Re: Kaz does not understand his own code --- I AM PROVED EXACTLY CORRECT Kaz Kylheku <643-408-1753@kylheku.com> - 2025-11-05 05:12 +0000
Re: Kaz does not understand his own code. --- I AM PROVED EXACTLY CORRECT. olcott <polcott333@gmail.com> - 2025-11-04 23:23 -0600
Re: Kaz does not understand his own code. --- I AM PROVED EXACTLY CORRECT. Kaz Kylheku <643-408-1753@kylheku.com> - 2025-11-05 07:01 +0000
Re: Kaz does not understand his own code. --- I AM PROVED EXACTLY CORRECT. olcott <polcott333@gmail.com> - 2025-11-05 08:55 -0600
Re: Kaz does not understand his own code. --- I AM PROVED EXACTLY CORRECT. Kaz Kylheku <643-408-1753@kylheku.com> - 2025-11-05 17:35 +0000
Re: Kaz does not understand his own code. --- I AM PROVED EXACTLY CORRECT. olcott <polcott333@gmail.com> - 2025-11-05 12:17 -0600
Re: Kaz does not understand his own code. --- I AM PROVED EXACTLY CORRECT. dbush <dbush.mobile@gmail.com> - 2025-11-05 13:43 -0500
Re: Kaz does not understand his own code. --- I AM PROVED EXACTLY CORRECT. olcott <polcott333@gmail.com> - 2025-11-05 19:24 -0600
Re: Kaz does not understand his own code. --- I AM PROVED EXACTLY CORRECT. dbush <dbush.mobile@gmail.com> - 2025-11-05 20:39 -0500
Re: Kaz does not understand his own code. --- I AM PROVED EXACTLY CORRECT. olcott <polcott333@gmail.com> - 2025-11-05 19:43 -0600
Re: Kaz does not understand his own code. --- I AM PROVED EXACTLY CORRECT. Kaz Kylheku <643-408-1753@kylheku.com> - 2025-11-06 01:56 +0000
Re: Kaz does not understand his own code. --- I AM PROVED EXACTLY CORRECT. olcott <polcott333@gmail.com> - 2025-11-05 20:21 -0600
Re: Kaz does not understand his own code. --- I AM PROVED EXACTLY CORRECT. Kaz Kylheku <643-408-1753@kylheku.com> - 2025-11-06 04:36 +0000
Re: Kaz does not understand his own code. --- I AM PROVED EXACTLY CORRECT. olcott <polcott333@gmail.com> - 2025-11-05 23:12 -0600
Re: Kaz does not understand his own code. --- I AM PROVED EXACTLY CORRECT. dbush <dbush.mobile@gmail.com> - 2025-11-06 07:54 -0500
Re: Kaz does not understand his own code. --- I AM PROVED EXACTLY CORRECT. olcott <polcott333@gmail.com> - 2025-11-06 09:19 -0600
Re: Kaz does not understand his own code. --- I AM PROVED EXACTLY CORRECT. Mike Terry <news.dead.person.stones@darjeeling.plus.com> - 2025-11-06 16:39 +0000
Re: Kaz does not understand his own code. --- I AM PROVED EXACTLY CORRECT. olcott <polcott333@gmail.com> - 2025-11-06 11:10 -0600
Re: Kaz does not understand his own code. --- I AM PROVED EXACTLY CORRECT. Kaz Kylheku <643-408-1753@kylheku.com> - 2025-11-06 17:16 +0000
Re: Kaz does not understand his own code. --- I AM PROVED EXACTLY CORRECT. olcott <polcott333@gmail.com> - 2025-11-06 11:26 -0600
Re: Kaz does not understand his own code. --- I AM PROVED EXACTLY CORRECT. dbush <dbush.mobile@gmail.com> - 2025-11-06 12:34 -0500
Re: Kaz does not understand his own code. --- I AM PROVED EXACTLY CORRECT. olcott <polcott333@gmail.com> - 2025-11-06 11:58 -0600
Re: Kaz does not understand his own code. --- I AM PROVED EXACTLY CORRECT. dbush <dbush.mobile@gmail.com> - 2025-11-06 13:01 -0500
Re: Kaz does not understand his own code. --- I AM PROVED EXACTLY CORRECT. olcott <polcott333@gmail.com> - 2025-11-06 12:04 -0600
Re: Kaz does not understand his own code. --- I AM PROVED EXACTLY CORRECT. dbush <dbush.mobile@gmail.com> - 2025-11-06 13:15 -0500
Re: Kaz does not understand his own code. --- I AM PROVED EXACTLY CORRECT. Kaz Kylheku <643-408-1753@kylheku.com> - 2025-11-06 18:37 +0000
Re: Kaz does not understand his own code. --- I AM PROVED EXACTLY CORRECT. Mike Terry <news.dead.person.stones@darjeeling.plus.com> - 2025-11-06 20:03 +0000
Re: Kaz does not understand his own code. --- I AM PROVED EXACTLY CORRECT. olcott <polcott333@gmail.com> - 2025-11-06 14:24 -0600
Re: Kaz does not understand his own code. --- I AM PROVED EXACTLY CORRECT. Kaz Kylheku <643-408-1753@kylheku.com> - 2025-11-06 21:16 +0000
Re: Kaz does not understand his own code. --- I AM PROVED EXACTLY CORRECT. Kaz Kylheku <643-408-1753@kylheku.com> - 2025-11-06 21:39 +0000
Re: Kaz does not understand his own code. --- I AM PROVED EXACTLY CORRECT. Kaz Kylheku <643-408-1753@kylheku.com> - 2025-11-06 22:10 +0000
Re: Kaz does not understand his own code. --- I AM PROVED EXACTLY CORRECT. olcott <polcott333@gmail.com> - 2025-11-06 14:04 -0600
Re: Kaz does not understand his own code. --- I AM PROVED EXACTLY CORRECT. Kaz Kylheku <643-408-1753@kylheku.com> - 2025-11-06 20:45 +0000
Re: Kaz does not understand his own code. --- I AM PROVED EXACTLY CORRECT. olcott <polcott333@gmail.com> - 2025-11-06 14:57 -0600
Re: Kaz does not understand his own code. --- I AM PROVED EXACTLY CORRECT. Kaz Kylheku <643-408-1753@kylheku.com> - 2025-11-06 18:14 +0000
Re: Kaz does not understand his own code. --- I AM PROVED EXACTLY CORRECT. olcott <polcott333@gmail.com> - 2025-11-06 12:27 -0600
Re: Kaz does not understand his own code. --- I AM PROVED EXACTLY CORRECT. Kaz Kylheku <643-408-1753@kylheku.com> - 2025-11-06 18:46 +0000
Re: Kaz does not understand his own code. --- I AM PROVED EXACTLY CORRECT. olcott <polcott333@gmail.com> - 2025-11-06 14:10 -0600
Re: Kaz does not understand his own code. --- I AM PROVED EXACTLY CORRECT. Kaz Kylheku <643-408-1753@kylheku.com> - 2025-11-06 21:03 +0000
Re: Kaz does not understand his own code. --- I AM PROVED EXACTLY CORRECT. olcott <polcott333@gmail.com> - 2025-11-05 19:54 -0600
Re: Kaz does not understand his own code. --- I AM PROVED EXACTLY CORRECT. dbush <dbush.mobile@gmail.com> - 2025-11-05 21:08 -0500
Re: Kaz does not understand his own code. --- I AM PROVED EXACTLY CORRECT. olcott <polcott333@gmail.com> - 2025-11-05 20:24 -0600
Re: Kaz does not understand his own code. --- I AM PROVED EXACTLY CORRECT. dbush <dbush.mobile@gmail.com> - 2025-11-05 22:05 -0500
Re: Kaz does not understand his own code. --- I AM PROVED EXACTLY CORRECT. olcott <polcott333@gmail.com> - 2025-11-05 21:15 -0600
Olcott proves he's not interested in an honest dialogue by actively avoiding being clear dbush <dbush.mobile@gmail.com> - 2025-11-05 22:18 -0500
Re: Olcott proves he's not interested in an honest dialogue by actively avoiding being clear olcott <polcott333@gmail.com> - 2025-11-05 21:27 -0600
Re: Olcott proves he's not interested in an honest dialogue by actively avoiding being clear dbush <dbush.mobile@gmail.com> - 2025-11-05 22:32 -0500
Re: Olcott proves he's not interested in an honest dialogue by actively avoiding being clear olcott <polcott333@gmail.com> - 2025-11-05 21:38 -0600
Re: Olcott proves he's not interested in an honest dialogue by actively avoiding being clear dbush <dbush.mobile@gmail.com> - 2025-11-05 22:39 -0500
Re: Olcott proves he's not interested in an honest dialogue by actively avoiding being clear olcott <polcott333@gmail.com> - 2025-11-05 21:50 -0600
Re: Olcott proves he's not interested in an honest dialogue by actively avoiding being clear dbush <dbush.mobile@gmail.com> - 2025-11-05 22:53 -0500
Re: Olcott proves he's not interested in an honest dialogue by actively avoiding being clear "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2025-11-05 19:57 -0800
Re: Olcott proves he's not interested in an honest dialogue by actively avoiding being clear olcott <polcott333@gmail.com> - 2025-11-05 21:57 -0600
Re: Olcott proves he's not interested in an honest dialogue by actively avoiding being clear dbush <dbush.mobile@gmail.com> - 2025-11-05 23:04 -0500
Re: Olcott proves he's not interested in an honest dialogue by actively avoiding being clear olcott <polcott333@gmail.com> - 2025-11-05 22:15 -0600
Re: Olcott proves he's not interested in an honest dialogue by actively avoiding being clear dbush <dbush.mobile@gmail.com> - 2025-11-05 23:25 -0500
Re: Olcott proves he's not interested in an honest dialogue by actively avoiding being clear olcott <polcott333@gmail.com> - 2025-11-05 23:00 -0600
Re: Olcott proves he's not interested in an honest dialogue by actively avoiding being clear dbush <dbush.mobile@gmail.com> - 2025-11-06 07:51 -0500
Re: Olcott proves he's not interested in an honest dialogue by actively avoiding being clear olcott <polcott333@gmail.com> - 2025-11-06 09:16 -0600
Re: Olcott proves he's not interested in an honest dialogue by actively avoiding being clear dbush <dbush.mobile@gmail.com> - 2025-11-06 10:22 -0500
Re: Olcott proves he's not interested in an honest dialogue by actively avoiding being clear olcott <polcott333@gmail.com> - 2025-11-06 10:08 -0600
Re: Olcott proves he's not interested in an honest dialogue by actively avoiding being clear dbush <dbush.mobile@gmail.com> - 2025-11-06 11:26 -0500
Re: Olcott proves he's not interested in an honest dialogue by actively avoiding being clear olcott <polcott333@gmail.com> - 2025-11-06 10:49 -0600
Re: Olcott proves he's not interested in an honest dialogue by actively avoiding being clear dbush <dbush.mobile@gmail.com> - 2025-11-06 11:56 -0500
Re: Olcott proves he's not interested in an honest dialogue by actively avoiding being clear olcott <polcott333@gmail.com> - 2025-11-06 11:16 -0600
Re: Kaz does not understand his own code. --- I AM PROVED EXACTLY CORRECT. dbush <dbush.mobile@gmail.com> - 2025-11-05 13:49 -0500
Re: Kaz does not understand his own code. --- I AM PROVED EXACTLY CORRECT. joes <noreply@example.org> - 2025-11-05 18:55 +0000
Re: Kaz does not understand his own code. --- I AM PROVED EXACTLY CORRECT. olcott <polcott333@gmail.com> - 2025-11-05 19:23 -0600
Re: Kaz does not understand his own code. --- I AM PROVED EXACTLY CORRECT. joes <noreply@example.org> - 2025-11-06 14:33 +0000
Re: Kaz does not understand his own code. --- I AM PROVED EXACTLY CORRECT. olcott <polcott333@gmail.com> - 2025-11-06 09:13 -0600
Re: Kaz does not understand his own code. --- I AM PROVED EXACTLY CORRECT. Kaz Kylheku <643-408-1753@kylheku.com> - 2025-11-05 21:38 +0000
Re: Kaz does not understand his own code. --- I AM PROVED EXACTLY CORRECT. olcott <polcott333@gmail.com> - 2025-11-05 19:15 -0600
Re: Kaz does not understand his own code. --- I AM PROVED EXACTLY CORRECT. olcott <polcott333@gmail.com> - 2025-11-05 19:41 -0600
Re: Kaz does not understand his own code. --- I AM PROVED EXACTLY CORRECT. dbush <dbush.mobile@gmail.com> - 2025-11-05 20:45 -0500
Re: Kaz does not understand his own code. --- I AM PROVED EXACTLY CORRECT. "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2025-11-05 18:39 -0800
Re: Kaz does not understand his own code. --- I AM PROVED EXACTLY CORRECT. "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2025-11-05 12:04 -0800
Re: Kaz does not understand his own code. --- I AM PROVED EXACTLY CORRECT. joes <noreply@example.org> - 2025-11-05 07:42 +0000
Re: Kaz does not understand his own code. --- I AM PROVED EXACTLY CORRECT. olcott <polcott333@gmail.com> - 2025-11-05 05:33 -0600
Re: Kaz does not understand his own code. --- I AM PROVED EXACTLY CORRECT. Mike Terry <news.dead.person.stones@darjeeling.plus.com> - 2025-11-05 16:43 +0000
Re: Kaz does not understand his own code. --- I AM PROVED EXACTLY CORRECT. olcott <polcott333@gmail.com> - 2025-11-05 10:56 -0600
csiph-web