home bbs files messages ]

Forums before death by AOL, social media and spammers... "We can't have nice things"

   comp.lang.c      Meh, in C you gotta define EVERYTHING      243,242 messages   

[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]

   Message 241,941 of 243,242   
   olcott to Kenny McCormack   
   Re: Any article that contains the string   
   13 Nov 25 09:24:16   
   
   XPost: comp.theory, comp.lang.c++   
   From: polcott333@gmail.com   
      
   On 11/13/2025 6:36 AM, Kenny McCormack wrote:   
   > In article <87a50qpp5n.fsf@example.invalid>,   
   > Keith Thompson   wrote:   
   >> [...]   
   >>   
   >> I note that a substantial fraction of the articles recently posted   
   >> to comp.lang.c (and probably comp.lang.c++) are cross-posted to   
   >> comp.theory, and are about the Halting Problem.   
   >>   
   >> Some of these articles contain small fragments of C-like source code,   
   >> but I suggest that doesn't make them either topical or interesting   
   >> to most participants in the C and C++ newsgroups.   
   >>   
   >> I humbly suggest, yet again, that these discussions be restricted   
   >> to comp.theory, and that users try to edit the "Newsgroups:" header   
   >> even when replying to a cross-posted article.   
   >   
   > Wouldn't it be better (and easier and more likely to work) to setup your   
   > killfile to kill any article (in C.L.C) that contains the string "olcott" ?   
   >   
   > I have not done this (yet); my killfile kills only articles *by* olcott.  I   
   > still have to manually kill any responses to his posts.  It would, of   
   > course, be nice if we could get people to stop responding to his junk, but   
   > that'd be like expecting the tides to turn.   
   >   
   > But I think it (killing any article that contains the string) is the right   
   > thing to do (*), and will do so when I get around to it.   
   >   
   > (*) I don't know (yet) if there is a more direct way to kill (in trn) any   
   > article from a given user and plus all followups - in a single go.   
   > Obviously, that would be the real/ideal solution to this problem.   
   >   
      
   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);   
   }   
      
   This code has been fully operational   
   for three years so I know what it does.   
      
   That no one else has been able to confirm   
   that DD simulated by HHH cannot possibly   
   reach its own "return" instruction has been   
   the issue that everyone has ignored or lied   
   about for three years.   
      
   I am a forever poster to this group until   
   I get a correct reply to the above.   
      
   --   
   Copyright 2025 Olcott "Talent hits a target no one else can hit; Genius   
   hits a target no one else can see." Arthur Schopenhauer   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)   

[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]


(c) 1994,  bbs@darkrealms.ca