On 2025-10-31 13:50:12 +0000, olcott said:I got the Vax 11-780 compiler stuck in an infinite
On 10/31/2025 7:02 AM, Mikko wrote:I started with the complier my professor gave me and told to use.On 2025-10-30 13:17:26 +0000, olcott said:>
>On 10/30/2025 5:29 AM, Mikko wrote:>On 2025-10-29 16:29:54 +0000, olcott said:>
>On 10/29/2025 6:03 AM, Mikko wrote:>On 2025-10-28 14:55:21 +0000, olcott said:>
>On 10/28/2025 4:09 AM, Mikko wrote:>On 2025-10-27 13:45:13 +0000, olcott said:>
>On 10/27/2025 5:10 AM, Mikko wrote:>On 2025-10-25 17:53:27 +0000, olcott said:>
>typedef int (*ptr)();>
int HHH(ptr P);
>
int DD()
{
int Halt_Status = HHH(DD);
if (Halt_Status)
HERE: goto HERE;
return Halt_Status;
}
>
int main()
{
HHH(DD);
}
Olcott has showm many times that he cannot correctly determine what
other people understand and what they don't. Sometimes he assumes
nobody understands what others see sas obvious and well known, ar
other times he thinks others understand what actually is nonsense
without any meaningful content to be understood.
Now that four different LLM systems have been able
reverse-engineer the non-halting result by merely
being told to faithfully simulate DD with HHH and
see what happens this proves that all of my reviewers
have been dishonest with me for three years.
Another skill Olcott has shown to lack is to determine whether someone
is honest. To determine honesty is not solely a matter of skill as the
information necessary for the determination is not always avoalable.
int D()
{
int Halt_Status = H(D);
if (Halt_Status)
HERE: goto HERE;
return Halt_Status;
}
>
H simulates D
that calls H(D) to simulate D
that calls H(D) to simulate D
that calls H(D) to simulate D
that calls H(D) to simulate D
that calls H(D) to simulate D
until H sees this repeating pattern.
>
Anyone that knows C and denies this is dishonest.
Thank you for the example.
That is the clearest that I could make it
after nearly 21 years.
Maybe, but for a long time it has been sufficiently clear that you
lack the skills to determine whether someone is honest and what
someone understands.
(a) Do you know C?
Yes, but not the latest revision.
I started with K & R back when it was brand new.
I quickly found out that there was a serious bug in the compiler.
Fortunately I found a work-around so that I could proceed while
waiting for a corrected compiler.
loop trying to compile my code that implemented
cons and cdr of Lisp with lots of recursion.
Don't tolerate such languages.Yes, that is an important idea both in mathematics and in programming.>(b) Do you deny that D simulated by H cannot reach>
its own simulated "return" statement?
The question is ambiguous. The usual meaning of "D simulated by H"
is the particular D that H simulates or tries to simulate. But there
is only one D in the context of the question so it seems a little
odd to be so verbose oabout its identity.
Lets back up a step. Do you know what ordinary recursion is:
>
int factorial(int n)
{
if (n >= 1)
return n*factorial(n-1);
else
return 1;
}
For programming one must also know what to do when recurion is not
supperted by the language or is prohibited for some reason.
They are mostly all simply damned liars.Not very many people. Likewise, I don't think many people misinterpreteHowever, some poeple may>
interprete it to mean something that only has the behavour H has
simulated and not the behavour specified by the input to H.
Some people think that cats are dogs, they are simply wrong.
"D simulated by H" to mean the simulation of D by H. But I have seen at
least one who does.
Kaz is trying to get away with the idea
that D simulated by H reaches its own
simulated "return" statement.
--
Copyright 2025 Olcott "Talent hits a target no one else can hit; Genius
hits a target no one else can see." Arthur Schopenhauer
Les messages affichés proviennent d'usenet.