Re: Defining a correct halting decidability decider (Which isn't a valid criteria for a decider)

On 8/7/24 9:12 AM, olcott wrote:

On 8/7/2024 1:59 AM, Mikko wrote:

On 2024-08-04 19:33:36 +0000, olcott said:
>

On 8/4/2024 2:05 PM, Richard Damon wrote:

On 8/4/24 2:49 PM, olcott wrote:

On 8/4/2024 1:38 PM, Richard Damon wrote:

On 8/4/24 10:46 AM, olcott wrote:

When we define an input that does the opposite of whatever
value that its halt decider reports there is a way for the
halt decider to report correctly.
>
int DD()
{
   int Halt_Status = HHH(DD);
   if (Halt_Status)
     HERE: goto HERE;
   return Halt_Status;
}
>
int main()
{
   HHH(DD);
}
>
HHH returns false indicating that it cannot
correctly determine that its input halts.
True would mean that its input halts.
>

>
But false indicates that the input does not halt, but it does.
>

>
I made a mistake that I corrected on a forum that allows
editing: *Defining a correct halting decidability decider*
1=input does halt
0=input cannot be decided to halt

>
And thus, not a halt decider.
>
Sorry, you are just showing your ignorance.
>
And, the problem is that a given DD *CAN* be decided about halting, just not by HHH, so "can not be decided" is not a correct answer.

>
A single universal decider can correctly determine whether
or not an input could possibly be denial-of-service-attack.
0=yes does not halt or pathological self-reference
1=no  halts

>
Conventionally the value 0 is used for "no" (for example, no errors)
and value 1 for "yes". If there are different "yes" results other

 A Conventional halt decider is 1 for halts and 0 for does not halt.
0 also means input has pathological relationship to decider.
In other words 1 means good input and 0 means bad input.

Except that there is nothing "bad" about the input, just that the decider it uses will get the wrong wnswer.
Also, that criteria isn't a valid criteria, as it is subjective, having a different answer when the same input is given to different decideres.
So, all you are doing is admitting that you have not been doing the problem you claime to have been doing, and thus have been a LIAR for years, and don't even know what a valid decision problem is.

 

numbers in addition to 1 can be used. For example, for the question
"is there anu errors?" the number may identify the error. For a
partial halt decider the best values are
-1 = does not halt
0 = not determined
1 = halts.
>
In C the value 0 is interpreted as false and every other number,
positive or negative, is interpreted as true in every context
where a boolean value is expected.
>

 I have known that since K&R was the standard.
I met Bjarne Stroustrup we he went around the country
promoting his new C++ language at the local universities.
He was a tee shirt and blue jeans kind of guy.
 

So, why do you not know that when DDD calls HHH, that the code in HHH is part of the code in the program created by DDD?
That has ALWAYS been true.