XPost: comp.theory, comp.lang.c++, comp.lang.c   
   From: chris.m.thomasson.1@gmail.com   
      
   On 10/27/2025 11:36 AM, Kaz Kylheku wrote:   
   > On 2025-10-27, olcott  wrote:   
   >> On 10/26/2025 11:47 PM, Kaz Kylheku wrote:   
   >>> On 2025-10-27, olcott  wrote:   
   >>>> On 10/26/2025 9:15 PM, André G. Isaak wrote:   
   >>>>> On 2025-10-26 19:58, olcott wrote:   
   >>>>>> On 10/26/2025 8:50 PM, Kaz Kylheku wrote:   
   >>>>>>>>   
   >>>>>>>> And   
   >>>>>> *Kaz is now dishonored in his deceit*   
   >>>>>   
   >>>>> How the hell is that a response to the word 'And'? At least quote enough   
   >>>>> material that its apparent what you are responding to.   
   >>>>>   
   >>>>> André   
   >>>>>   
   >>>>   
   >>>> He is trying to get away with spamming me with   
   >>>> deceit so I erase all of it and keep ridiculing   
   >>>   
   >>> Aha!   
   >>>   
   >>> So you finally appreciate how it looks like spamming when you are on the   
   >>> receiving end of these god-forsaken x86utm execution traces!   
   >>>   
   >>> You pathetic sack of shit, unable to respond to /code/!   
   >>>   
   >>   
   >> Here is the code   
   >>   
   >> A straight forward sequence of steps that any   
   >> C programmer can easily determine:   
   >>   
   >> int DD()   
   >> {   
   >>     int Halt_Status = HHH(DD);   
   >>     if (Halt_Status)   
   >>       HERE: goto HERE;   
   >>     return Halt_Status;   
   >> }   
   >   
   > [ ... ]   
   >   
   >> I am only talking about the HHH in the fifteen   
   >> lines of text immediately above.   
   >   
   > I don't see an HHH in fifteen lines above. Do you?   
   >   
   > (I see a reference to one being /called/. )   
   >   
   >   
   >   
      
   If you have a really long arm and are a skilled plumber... You might be   
   able to find the crap load lodged in the system?   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)