Sujet : Re: I call it a halting decidability decider, and thus isn't actually a computability decider.
De : richard (at) *nospam* damon-family.org (Richard Damon)
Groupes : comp.theoryDate : 06. Aug 2024, 02:32:08
Autres entêtes
Organisation : i2pn2 (i2pn.org)
Message-ID : <e7ddae8f874a17ffc6f7c961f674fd3fd014ca11@i2pn2.org>
References : 1 2 3 4 5 6 7
User-Agent : Mozilla Thunderbird
On 8/5/24 8:55 PM, olcott wrote:
On 8/5/2024 5:59 PM, Richard Damon wrote:
On 8/5/24 9:46 AM, olcott wrote:
On 8/5/2024 8:44 AM, Python wrote:
Le 05/08/2024 à 13:50, olcott a écrit :
On 8/5/2024 3:08 AM, Mikko wrote:
On 2024-08-04 14:46:02 +0000, olcott said:
>
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.
>
That is called a "partial halt decider". The set of requirements is
a subset of the requirements for "halt decider" but still require
that the answer is not "halts" if the input does not halt and that
the answer is not "does not halt" if the input halts. The difference
is that a "halt decider" is required to give one of these answers
for every input but a "partial halt decider" is not.
>
For every computation there is a partial halt decider that answers it.
>
>
I call it a halting decidability decider.
1=input halts
0=input does not halt or has pathological relationship with its decider
>
So it is NOT an halt decider. Case closed. You've lost your time
for years, and made a lot of people lose their time too.
>
>
>
>
It refutes Rice
>
>
Nope, since the criteria is not a avalid criteria, as it is a subjective criteria, and NOT a property of JUST the input.
A freaking actual execution trace is not freaking subjective.
If the trace depends on who does it, it is.
But then, part of your problem is that HHH doesn't actual do a correct emulation, so you can't use that as your grounds.
Do you not agree that giving the DDD/HHH pair to different deciders can result in different answers?
When we give it to HHH, it should say 0, but if we give it to HHH1, it should say 1.
Thus, the question is BY DEFINITION, subjective.
And, if you try to claim that we pair DDD with whatever decider we give it to, then it isn't a Program, as it doesn't have its own complete instrucctions, and doesn't always behave the same, so you are just caught lying that it is a proper input.
Sorry, you are just proving your stupidity.
Date | Sujet | # | | Auteur |
4 Aug 24 | Defining a correct halt decider | 67 | | olcott |
4 Aug 24 | Re: Defining a correct halt decider | 45 | | Richard Damon |
4 Aug 24 | Re: Defining a correct halting decidability decider | 44 | | olcott |
4 Aug 24 | Re: Defining a correct halting decidability decider | 43 | | Richard Damon |
4 Aug 24 | Re: Defining a correct halting decidability decider | 42 | | olcott |
4 Aug 24 | Re: Defining a correct halting decidability decider | 20 | | Richard Damon |
4 Aug 24 | Re: Defining a correct halting decidability decider | 19 | | olcott |
4 Aug 24 | Re: Defining a correct halting decidability decider | 18 | | Richard Damon |
4 Aug 24 | Re: Defining a correct halting decidability decider | 17 | | olcott |
5 Aug 24 | Re: Defining a correct halting decidability decider | 16 | | Richard Damon |
5 Aug 24 | Re: Defining a correct halting decidability decider | 15 | | olcott |
5 Aug 24 | Re: Defining a correct halting decidability decider | 14 | | Richard Damon |
5 Aug 24 | Re: Defining a correct halting decidability decider | 13 | | olcott |
5 Aug 24 | Re: Defining a correct halting decidability decider | 12 | | Richard Damon |
5 Aug 24 | Re: Defining a correct halting decidability decider | 11 | | olcott |
5 Aug 24 | Re: Defining a correct halting decidability decider | 10 | | Richard Damon |
5 Aug 24 | You still seem too dishonest to admit that DDD correctly emulated by any HHH cannot possibly reach its own ,"return" instruction | 9 | | olcott |
5 Aug 24 | Re: You still seem too dishonest to admit that DDD correctly emulated by any HHH cannot possibly reach its own ,"return" instruction | 8 | | Richard Damon |
5 Aug 24 | Re: You still seem too dishonest to admit that DDD correctly emulated by any HHH cannot possibly reach its own ,"return" instruction | 7 | | olcott |
5 Aug 24 | Re: You still seem too dishonest to admit that DDD correctly emulated by any HHH cannot possibly reach its own ,"return" instruction | 6 | | Richard Damon |
5 Aug 24 | Re: You still seem too dishonest to admit that DDD correctly emulated by any HHH cannot possibly reach its own ,"return" instruction | 5 | | olcott |
5 Aug 24 | Re: You still seem too dishonest to admit that DDD correctly emulated by any HHH cannot possibly reach its own ,"return" instruction | 4 | | Richard Damon |
5 Aug 24 | Re: You still seem too dishonest to admit that DDD correctly emulated by any HHH cannot possibly reach its own ,"return" instruction | 3 | | wij |
5 Aug 24 | Re: You still seem too dishonest to admit that DDD correctly emulated by any HHH cannot possibly reach its own ,"return" instruction | 2 | | olcott |
6 Aug 24 | Re: Olcott still seems too dishonest to admit that his HHH doesn't correctly emulate DDD | 1 | | Richard Damon |
7 Aug 24 | Re: Defining a correct halting decidability decider | 21 | | Mikko |
7 Aug 24 | Re: Defining a correct halting decidability decider | 20 | | olcott |
8 Aug 24 | Re: Defining a correct halting decidability decider (Which isn't a valid criteria for a decider) | 1 | | Richard Damon |
8 Aug 24 | Re: Defining a correct halting decidability decider | 18 | | Mikko |
8 Aug 24 | Re: Defining a correct halting decidability decider | 17 | | olcott |
8 Aug 24 | Re: Defining a correct halting decidability decider | 4 | | Python |
8 Aug 24 | Re: Defining a correct halting decidability decider | 3 | | olcott |
9 Aug 24 | Re: Defining a correct halting decidability decider | 1 | | Richard Damon |
9 Aug 24 | Re: Defining a correct halting decidability decider | 1 | | Python |
9 Aug 24 | Re: Defining a correct halting decidability decider | 1 | | Richard Damon |
9 Aug 24 | Re: Defining a correct halting decidability decider | 11 | | Mikko |
9 Aug 24 | Re: Defining a correct halting decidability decider | 10 | | olcott |
10 Aug 24 | Re: Defining a correct halting decidability decider | 1 | | Richard Damon |
10 Aug 24 | Re: Defining a correct halting decidability decider | 8 | | Mikko |
10 Aug 24 | Re: Defining a correct halting decidability decider | 7 | | olcott |
10 Aug 24 | Re: Defining a correct halting decidability decider | 3 | | Richard Damon |
10 Aug 24 | Re: Defining a correct halting decidability decider | 2 | | olcott |
10 Aug 24 | Re: Defining a correct halting decidability decider | 1 | | Richard Damon |
11 Aug 24 | Re: Defining a correct halting decidability decider | 3 | | Mikko |
11 Aug 24 | Re: Defining a correct halting decidability decider | 2 | | olcott |
11 Aug 24 | Re: Defining a correct halting decidability decider | 1 | | Richard Damon |
5 Aug 24 | Re: Defining a correct halt decider | 21 | | Mikko |
5 Aug 24 | I call it a halting decidability decider | 20 | | olcott |
5 Aug 24 | Re: I call it a halting decidability decider | 14 | | Python |
5 Aug 24 | Re: I call it a halting decidability decider | 13 | | olcott |
6 Aug 24 | Re: I call it a halting decidability decider, and thus isn't actually a computability decider. | 5 | | Richard Damon |
6 Aug 24 | Re: I call it a halting decidability decider, and thus isn't actually a computability decider. | 4 | | olcott |
6 Aug 24 | Re: I call it a halting decidability decider, and thus isn't actually a computability decider. | 3 | | Richard Damon |
6 Aug 24 | Re: I call it a halting decidability decider, and thus isn't actually a computability decider. | 2 | | olcott |
6 Aug 24 | Re: I call it a halting decidability decider, and thus isn't actually a computability decider. | 1 | | Richard Damon |
7 Aug 24 | Re: I call it a halting decidability decider | 7 | | Mikko |
7 Aug 24 | HHH decides a non-trivial semantic property of its input | 6 | | olcott |
8 Aug 24 | Re: HHH decides a trivial semantic non-property of its input | 1 | | Richard Damon |
8 Aug 24 | Re: HHH decides a non-trivial semantic property of its input | 3 | | Mikko |
8 Aug 24 | Re: HHH decides a non-trivial semantic property of its input | 2 | | olcott |
9 Aug 24 | Re: HHH decides a non-trivial semantic property of its input | 1 | | Richard Damon |
8 Aug 24 | Re: HHH decides a trivial non-semantic non-property of its input | 1 | | Richard Damon |
6 Aug 24 | Re: I call it a halting decidability decider, and thus doesn't say anything about the halting problem | 1 | | Richard Damon |
7 Aug 24 | Re: I call it a halting decidability decider | 4 | | Mikko |
7 Aug 24 | Re: I call it a halting decidability decider | 3 | | olcott |
8 Aug 24 | Re: I call it a halting decidability decider | 1 | | Richard Damon |
8 Aug 24 | Re: I call it a halting decidability decider | 1 | | Mikko |