Sujet : Re: How do simulating termination analyzers work? (in C and C++)
De : 643-408-1753 (at) *nospam* kylheku.com (Kaz Kylheku)
Groupes : comp.lang.c comp.lang.c++Date : 19. Jun 2025, 21:41:13
Autres entêtes
Organisation : A noiseless patient Spider
Message-ID : <20250619133112.290@kylheku.com>
References : 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
User-Agent : slrn/pre1.0.4-9 (Linux)
On 2025-06-19, olcott <
polcott333@gmail.com> wrote:
On 6/19/2025 1:55 PM, Bonita Montero wrote:
Am 19.06.2025 um 20:32 schrieb olcott:
On 6/19/2025 1:20 PM, Bonita Montero wrote:
Am 19.06.2025 um 19:07 schrieb olcott:
That's not ad hominem. Anyone who asks the same question
thousands of times in a forum is mentally ill.
Not when one understands the importance of the question.
The importance of the question is off-topic for this
group.
>
You really need a doctor.
>
If that was true then you could point to an actual
error in my work.
If that wasn't true, you would /believe/ it when someone pointed
out an actual error in your work. I've not seen evidence that
you are prepared to receive such a report in good faith.
That has been done numerous times by different people; unfortunately,
you refuse to believe or understand it.
For instance, it came to light a few years ago that you don't understand
the traces of your own x86 program; what conclusions they allow and what
conclusions they don't allow.
You are confused by situations in which multiple self-similar dynamic
contexts have to be identified as separate and unrelated.
(Analogy: someone who doesn't understand function call semantics
won't understand that a recursive function has multiple simultaneous
activations, with different instances of local variables and parameters,
possibly holding different values. This is not you, but your confusion
along this vein in matters related to halting. You conflate different
instances of the same function with different parameters as being
the same one, and such. These are rookie mistakes that computer
scientists wash themselves of before finishing undergrad.)
-- TXR Programming Language: http://nongnu.org/txrCygnal: Cygwin Native Application Library: http://kylheku.com/cygnalMastodon: @Kazinator@mstdn.ca