Liste des Groupes | Revenir à theory |
olcott <polcott333@gmail.com> writes:I need the "return statement" to explicitlyOn 5/8/2025 6:54 PM, Keith Thompson wrote:You see, this is something you've gotten wrong, and you need somebodyolcott <polcott333@gmail.com> writes:>On 5/8/2025 6:30 PM, Richard Heathfield wrote:[...]On 08/05/2025 23:50, olcott wrote:No, what you need is someone who is an expert in mathematical logic>If you are a competent C programmerKeith Thompson is a highly-respected and very competent C
programmer.
*Then he is just who I need*
(I am not) who can explain to you, in terms you can understand and
accept, where you've gone wrong. Some expertise in C could also
be helpful.
The key gap in my proof is that none of the comp.sci
people seems to have a slight clue about simple C
programming.
who can explain that to you in terms you can understand and accept.
void DDD()Is there any reason you couldn't have written that as follows?
{
HHH(DDD);
return;
}
>
*THIS IS THE C PART THAT NO ONE HERE UNDERSTANDS*
DDD correctly simulated by HHH cannot possibly
reach its own "return" instruction.
void DDD(void)
{
HHH(DDD);
}
You could then talk about it not reaching its closing brace rather
than not reaching its "return" instruction. BTW, it's correctly
called a "return statement" in C; dropping it would make it easier
to avoid your incorrect use of terminology. (Assembly or machine
code has "instructions"; C has "statements" and "declarations".)
Richard provided the same kind of fake "rebuttal"DDD correctly simulated by HHH is the same thingSure, infinite recursion is infinite, regardless of how it's
as infinite recursion between HHH and DDD yet is
implemented as recursive simulation.
implemented, assuming it's implemented correctly. That's so trivally
obvious that I simply don't believe that "the comp.sci" people are
failing to understand it -- though I can believe that you believe it.
Les messages affichés proviennent d'usenet.