XPost: comp.theory, sci.logic   
   From: F.Zwarts@HetNet.nl   
      
   Op 21.jul.2025 om 16:07 schreef olcott:   
   > On 7/21/2025 4:38 AM, Mikko wrote:   
   >> On 2025-07-20 15:04:34 +0000, olcott said:   
   >>   
   >>> On 7/20/2025 3:46 AM, Mikko wrote:   
   >>>> On 2025-07-19 14:59:41 +0000, olcott said:   
   >>>>   
   >>>>> On 7/19/2025 4:02 AM, Mikko wrote:   
   >>>>>> On 2025-07-18 22:11:50 +0000, Mr Flibble said:   
   >>>>>>   
   >>>>>>> On Thu, 17 Jul 2025 13:01:31 -0500, olcott wrote:   
   >>>>>>>   
   >>>>>>>> Claude.ai agrees that the halting problem as defined is a category   
   >>>>>>>> error.   
   >>>>>>>>   
   >>>>>>>> https://claude.ai/share/0b784d2a-447e-441f-b3f0-a204fa17135a   
   >>>>>>>>   
   >>>>>>>> This can only be directly seen within my notion of a simulating   
   >>>>>>>> halt   
   >>>>>>>> decider. I used the Linz proof as my basis.   
   >>>>>>>>   
   >>>>>>>> Sorrowfully Peter Linz passed away 2 days less than one year ago   
   >>>>>>>> on my   
   >>>>>>>> Mom's birthday July 19, 2024.   
   >>>>>>>   
   >>>>>>> I was the first to state that the halting problem as defined is a   
   >>>>>>> category   
   >>>>>>> error and I stated it in this forum.   
   >>>>>>   
   >>>>>> Indeed you stated that but failed to identify the actual error. You   
   >>>>>> did not say which word in the problem statement is wrong or what is   
   >>>>>> the wrong category or what would be the right one.   
   >>>>>   
   >>>>> I conclusively proved the actual category error yet   
   >>>>> people that are only interested in rebuttal want no   
   >>>>> part of any proof that I am correct.   
   >>>>   
   >>>> Is it the same error as Flibble found?   
   >>>   
   >>> Flibble's category error is stated abstractly.   
   >>> My version is stated concretely.   
   >>   
   >> Could you post a pointer to your version?   
   >>   
   >   
   > The category error is a type mismatch error where   
   > a Turing Machine decider is required to report on   
   > the behavior of a directly executed machine yet   
   > cannot take a directly executed machine as an input.   
   >   
      
   Nobody requires it. So, you fail to prove the category error.   
   It should report about the program specified in the input. This   
   specifies a halting program. If the decider fails to see that, it is   
   incorrect. In this case we can present exactly the same input to other   
   deciders and we see that they correctly report the halting behaviour.   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)