Re: You still seem too dishonest to admit that DDD correctly emulated by any HHH cannot possibly reach its own ,"return" instruction

Liste des GroupesRevenir à theory 
Sujet : Re: You still seem too dishonest to admit that DDD correctly emulated by any HHH cannot possibly reach its own ,"return" instruction
De : richard (at) *nospam* damon-family.org (Richard Damon)
Groupes : comp.theory
Date : 05. Aug 2024, 04:18:42
Autres entêtes
Organisation : i2pn2 (i2pn.org)
Message-ID : <ff44c6626923661554540bf75cb50a4921a50381@i2pn2.org>
References : 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17
User-Agent : Mozilla Thunderbird
On 8/4/24 9:07 PM, olcott wrote:
On 8/4/2024 7:05 PM, Richard Damon wrote:
On 8/4/24 7:34 PM, olcott wrote:
On 8/4/2024 6:25 PM, Richard Damon wrote:
On 8/4/24 6:57 PM, olcott wrote:
On 8/4/2024 5:31 PM, Richard Damon wrote:
On 8/4/24 6:15 PM, olcott wrote:
On 8/4/2024 5:02 PM, Richard Damon wrote:
On 8/4/24 5:58 PM, olcott wrote:
On 8/4/2024 4:43 PM, Richard Damon wrote:
On 8/4/24 5:05 PM, olcott wrote:
On 8/4/2024 3:14 PM, Richard Damon wrote:
On 8/4/24 3:33 PM, olcott wrote:
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
>
>
>
Which isn't halt deciding, so you are just admitting you have been lying about working on the Halting Problem.
>
>
It does seem to refute Rice.
>
>
Nope, because your criteria in not a semantic property of the INPUT (or it is trivial, as 0 is always a correct answer).
>
>
It is only allowed to answer 0 when when
(a) The input does not halt
(b) The input has a pathological relationship with the decider.
>
>
>
Which means it is not a property of the INPUT, but the input and the decider.
>
>
It is a property of the input.
(a) The input does
(b) The input has
>
>
But not of JUST the input.
>
>
It is a semantic property of the input.
I don't care if you lie about it.
>
>
Nope, because it depends on the decider.
>
>
(b) Cannot possibly exist unless it is a property
of the input.
>
>
>
Then it can not exist, becuase it depends on more than the input.
>
 void DDD()
{
   HHH(DDD);
   return;
}
 You still seem too dishonest to admit that DDD correctly
emulated by any HHH cannot possibly reach its own "return"
instruction.
No, I admit that *IF* HHH does correctly (and thus completely without aborting) emulated its input, then THAT DDD and ONLY that DDD will be non-halting.
This means that EVERY OTHER HHH is just wrong, as the DDD that it is given DOES halt when run, but HHH does emulate long enough to see that because in INCORRECTLY aborts its emulation, confusing the input it was actually given with the input given to the non-aborting HHH, because it thinks that it is that non-aborting HHH itself, but that it can still abort.
What seems to be your problem is that you don't understand what a program is, and that only actual programs have programtic behavior.
You also don't seem to understand that you can't assume that the impossible happens, that just proves your own insanity.

 Maybe EE and a masters in EE just doesn't teach
hardly anything about actual programming.
I learned a lot, but it seems you don't understand the basic definition that DDD without HHH provided IS NOT A PROGRAM.
That your logic is based on the lie that DDD doesn't include HHH, just proves your utter stupidity.

 I would hate to call you dishonest when it is just
ordinary ignorance. It can't really be just ordinary
ignorance when it feigns expertise.
 
Nope, it is your PATHOLOGICAL IGNORANCE that causes the problem, your trying to blame others for your own stupidity just proves your state as a pathetic ignorant pathologically lying idiot with a reckless disregard for the truth, who even ADMITS that he doesn't have a basis for his claims.
Sorry, you have just killed your reputation and earned your place in HELL.

Date Sujet#  Auteur
4 Aug 24 * Defining a correct halt decider67olcott
4 Aug 24 +* Re: Defining a correct halt decider45Richard Damon
4 Aug 24 i`* Re: Defining a correct halting decidability decider44olcott
4 Aug 24 i `* Re: Defining a correct halting decidability decider43Richard Damon
4 Aug 24 i  `* Re: Defining a correct halting decidability decider42olcott
4 Aug 24 i   +* Re: Defining a correct halting decidability decider20Richard Damon
4 Aug 24 i   i`* Re: Defining a correct halting decidability decider19olcott
4 Aug 24 i   i `* Re: Defining a correct halting decidability decider18Richard Damon
4 Aug 24 i   i  `* Re: Defining a correct halting decidability decider17olcott
5 Aug 24 i   i   `* Re: Defining a correct halting decidability decider16Richard Damon
5 Aug 24 i   i    `* Re: Defining a correct halting decidability decider15olcott
5 Aug 24 i   i     `* Re: Defining a correct halting decidability decider14Richard Damon
5 Aug 24 i   i      `* Re: Defining a correct halting decidability decider13olcott
5 Aug 24 i   i       `* Re: Defining a correct halting decidability decider12Richard Damon
5 Aug 24 i   i        `* Re: Defining a correct halting decidability decider11olcott
5 Aug 24 i   i         `* Re: Defining a correct halting decidability decider10Richard Damon
5 Aug 24 i   i          `* You still seem too dishonest to admit that DDD correctly emulated by any HHH cannot possibly reach its own ,"return" instruction9olcott
5 Aug 24 i   i           `* Re: You still seem too dishonest to admit that DDD correctly emulated by any HHH cannot possibly reach its own ,"return" instruction8Richard Damon
5 Aug 24 i   i            `* Re: You still seem too dishonest to admit that DDD correctly emulated by any HHH cannot possibly reach its own ,"return" instruction7olcott
5 Aug 24 i   i             `* Re: You still seem too dishonest to admit that DDD correctly emulated by any HHH cannot possibly reach its own ,"return" instruction6Richard Damon
5 Aug 24 i   i              `* Re: You still seem too dishonest to admit that DDD correctly emulated by any HHH cannot possibly reach its own ,"return" instruction5olcott
5 Aug 24 i   i               `* Re: You still seem too dishonest to admit that DDD correctly emulated by any HHH cannot possibly reach its own ,"return" instruction4Richard Damon
5 Aug 24 i   i                `* Re: You still seem too dishonest to admit that DDD correctly emulated by any HHH cannot possibly reach its own ,"return" instruction3wij
5 Aug 24 i   i                 `* Re: You still seem too dishonest to admit that DDD correctly emulated by any HHH cannot possibly reach its own ,"return" instruction2olcott
6 Aug 24 i   i                  `- Re: Olcott still seems too dishonest to admit that his HHH doesn't correctly emulate DDD1Richard Damon
7 Aug 24 i   `* Re: Defining a correct halting decidability decider21Mikko
7 Aug 24 i    `* Re: Defining a correct halting decidability decider20olcott
8 Aug 24 i     +- Re: Defining a correct halting decidability decider (Which isn't a valid criteria for a decider)1Richard Damon
8 Aug 24 i     `* Re: Defining a correct halting decidability decider18Mikko
8 Aug 24 i      `* Re: Defining a correct halting decidability decider17olcott
8 Aug 24 i       +* Re: Defining a correct halting decidability decider4Python
8 Aug 24 i       i`* Re: Defining a correct halting decidability decider3olcott
9 Aug 24 i       i +- Re: Defining a correct halting decidability decider1Richard Damon
9 Aug 24 i       i `- Re: Defining a correct halting decidability decider1Python
9 Aug 24 i       +- Re: Defining a correct halting decidability decider1Richard Damon
9 Aug 24 i       `* Re: Defining a correct halting decidability decider11Mikko
9 Aug 24 i        `* Re: Defining a correct halting decidability decider10olcott
10 Aug 24 i         +- Re: Defining a correct halting decidability decider1Richard Damon
10 Aug 24 i         `* Re: Defining a correct halting decidability decider8Mikko
10 Aug 24 i          `* Re: Defining a correct halting decidability decider7olcott
10 Aug 24 i           +* Re: Defining a correct halting decidability decider3Richard Damon
10 Aug 24 i           i`* Re: Defining a correct halting decidability decider2olcott
10 Aug 24 i           i `- Re: Defining a correct halting decidability decider1Richard Damon
11 Aug 24 i           `* Re: Defining a correct halting decidability decider3Mikko
11 Aug 24 i            `* Re: Defining a correct halting decidability decider2olcott
11 Aug 24 i             `- Re: Defining a correct halting decidability decider1Richard Damon
5 Aug 24 `* Re: Defining a correct halt decider21Mikko
5 Aug 24  `* I call it a halting decidability decider20olcott
5 Aug 24   +* Re: I call it a halting decidability decider14Python
5 Aug 24   i`* Re: I call it a halting decidability decider13olcott
6 Aug 24   i +* Re: I call it a halting decidability decider, and thus isn't actually a computability decider.5Richard Damon
6 Aug 24   i i`* Re: I call it a halting decidability decider, and thus isn't actually a computability decider.4olcott
6 Aug 24   i i `* Re: I call it a halting decidability decider, and thus isn't actually a computability decider.3Richard Damon
6 Aug 24   i i  `* Re: I call it a halting decidability decider, and thus isn't actually a computability decider.2olcott
6 Aug 24   i i   `- Re: I call it a halting decidability decider, and thus isn't actually a computability decider.1Richard Damon
7 Aug 24   i `* Re: I call it a halting decidability decider7Mikko
7 Aug 24   i  `* HHH decides a non-trivial semantic property of its input6olcott
8 Aug 24   i   +- Re: HHH decides a trivial semantic non-property of its input1Richard Damon
8 Aug 24   i   +* Re: HHH decides a non-trivial semantic property of its input3Mikko
8 Aug 24   i   i`* Re: HHH decides a non-trivial semantic property of its input2olcott
9 Aug 24   i   i `- Re: HHH decides a non-trivial semantic property of its input1Richard Damon
8 Aug 24   i   `- Re: HHH decides a trivial non-semantic non-property of its input1Richard Damon
6 Aug 24   +- Re: I call it a halting decidability decider, and thus doesn't say anything about the halting problem1Richard Damon
7 Aug 24   `* Re: I call it a halting decidability decider4Mikko
7 Aug 24    `* Re: I call it a halting decidability decider3olcott
8 Aug 24     +- Re: I call it a halting decidability decider1Richard Damon
8 Aug 24     `- Re: I call it a halting decidability decider1Mikko

Haut de la page

Les messages affichés proviennent d'usenet.

NewsPortal