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,370 messages   

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

   Message 242,339 of 243,370   
   olcott to Kaz Kylheku   
   Olcott is provably correct --- no one ca   
   03 Dec 25 19:55:59   
   
   XPost: comp.theory, comp.ai.philosophy, comp.lang.c++   
   From: polcott333@gmail.com   
      
   On 11/30/2025 11:34 PM, Kaz Kylheku wrote:   
   > On 2025-12-01, olcott  wrote:   
   >> On 11/30/2025 7:44 PM, Kaz Kylheku wrote:   
   >>> On 2025-11-30, olcott  wrote:   
   >>>> HHH does correctly report that DD simulated   
   >>>> by HHH (according to the semantics of the C   
   >>>> programming language) does not halt.   
   >>>   
   >>   
   >> (1) It is a fact that this input to HHH(DD) does specify   
   >>       non-halting behavior according to this definition   
   >>       that you erased:   
   >>   
   >> An input DD that halts for a simulating termination   
   >> analyzer HHH is defined as DD reaching its own simulated   
   >> "return" statement while DD is being simulated by HHH.   
   >>   
   >> (2) It is a fact that HHH reports this.   
   >>   
   >> The key most important fact is that the halting   
   >> problem *is* a category error because it requires   
   >   
   > If you think the problem is a "category error", then ... fucking   
   > stop discussing cases of it, with elaborate claims about   
   > termination behavors.   
   >   
   > If it is the case that the whole problem is a category error,   
   > then everything that follows is erroneous and that is that.   
   >   
   >> a halt decider to report on different behavior   
   >> than the actual behavior that its actual input   
   >> actually specifies.   
   >   
   > If you believe that, then stop trying to make halt deciders   
   > which do that, and then claim they are correct.   
   >   
   >> This makes everything else that you say below moot   
   >> AKA totally beside the point and irrelevant.   
   >   
   > But that would only be because it refers to your simulation work   
   > and the claims you have based on it, which under the assumption that   
   > halting is errneous, are all erroneous.   
   >   
      
   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);   
   }   
      
   *Proof that HHH correctly rejects HHH*   
      
   (a) DD simulated by HHH according to the   
        semantics of the C programming language   
      
   (b) Cannot possibly reach its own "return"   
        statement final halt state   
      
   (c) While being simulated by HHH   
      
   Conclusively proves that behavior that the   
   input to HHH(DD) specifies is non-halting behavior.   
      
   That   
   (a) Turing machine deciders only compute the mapping   
        from their [finite string] inputs   
      
   (b) To an accept or reject state   
      
   (c) On the basis that this [finite string] input specifies   
        or fails to specify a semantic or syntactic property.   
      
   Proves that the halting problem, itself is incorrect   
   when it requires something else.   
      
   --   
   Copyright 2025 Olcott   
      
   My 28 year goal has been to make   
   "true on the basis of meaning" computable.   
      
   This required establishing a new foundation   
   for correct reasoning.   
      
   --- 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