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, 05:07:56
Autres entêtes
Organisation : i2pn2 (i2pn.org)
Message-ID : <569060964dc985138884a3bdff8d0157a52af40e@i2pn2.org>
References : 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19
User-Agent : Mozilla Thunderbird
On 8/4/24 10:49 PM, olcott wrote:
On 8/4/2024 9:18 PM, Richard Damon wrote:
On 8/4/24 9:07 PM, olcott wrote:>>
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.
>
 See there?
 DDD correctly emulated by any HHH that can possibly exist
cannot possibly reach its "return" instruction and every
C expert knows this.
But that only apply to the PROGRAM DDD built from an HHH that never aborts.
It doesn't apply to any other PROGRAM DDD built from any other HHH that doesn't do that, in particular, any HHH that aborts its emulation and returns creates a PROGRAM DDD that does reach that final state.
Sinmce you just admitted below that your DDD isn't a program, it doesn't apply, as non-programs can't actually be correct emualted.

 
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.
>
 Of course it is not a program.
It is also true that 56 is not an English word.
Then you admit it isn't a valid input to a Halt Decider.
I guess you can pack up you work, as you have just admitted it is based on a lie.
The Halting problem is about making decisions on the PROGRAM described to the decider.
If you input isn't based on a program, than it can't be a valid input to a halt decider. PERIOD.
YOu just admitted that all your work is just WORTHLESS.
Sorry you are that stupid.

 That seems to clinch it. You are feigning competence with C.
That is much better than sadistic pleasure in denying easily
verified facts. That might get you sent to Hell.
How? Even C defines a PROGRAM as containing all the code of all the functions that it calls.
Every statement I have made is true, based on the actual meaning of the words used. It also presumes that you were using the words at least close to correct, and thus we are treating the "input DDD" as something representing an actual program built from DDD.
So, what "lie" are you claiming I have made?
Calling your non-program not a program?
It seems you call other people liars to try to hid your own lies.
It seems that your LIFE has been based on lies, and that is exactly the thing that Revelation was talking about. You have punched your one-way ticket to the lake of fire. Unless you confess your sins are repent of them, that is where you are going to end up by every sign you have shown.

 
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.
 *Feigning competence with C probably would not get you sent to Hell*
 
I know more about C then you even have.
You are just proving yourself to be a MORON.

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