Sujet : Re: Olcott still seems too dishonest to admit that his HHH doesn't correctly emulate DDD
De : richard (at) *nospam* damon-family.org (Richard Damon)
Groupes : comp.theoryDate : 05. Aug 2024, 23:59:12
Autres entêtes
Organisation : i2pn2 (i2pn.org)
Message-ID : <22d4fbed2cbc9a969dbb7abf7d48619d6038e1c1@i2pn2.org>
References : 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23
User-Agent : Mozilla Thunderbird
On 8/5/24 8:41 AM, olcott wrote:
On 8/5/2024 6:53 AM, wij wrote:
On Mon, 2024-08-05 at 07:40 -0400, Richard Damon wrote:
On 8/4/24 11:58 PM, olcott wrote:
On 8/4/2024 10:07 PM, Richard Damon wrote:
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.
>
>
No it does not and every C expert knows that it does not.
>
>
Really> You have a source for that?
>
Or is this just another of your "Digonalization" logic claims that you
retracted.
>
Claims that "every x knows" are just a fallacy, and you should know it,
but are, of course, just to dumb to understand.
>
Here the problem is you just lie about what "Correctly Emulated" means
for determining the behavior of a program.
>
Sorry, you are just proving you are a stupid pathetic ignorant
pathological lying idiot with a reckless disregrad for the truth because
you beleive your own lies to the point that you don't even look at the
facts.
>
Don't know why I am glad to see someone finally to find out olcott is a
"pathological liar and idiot".
>
Save all your time. olcott don't understand the basic "if" logic, that says
everything to me. He don't know anything logic.
>
typedef void (*ptr)();
int HHH(ptr P);
void DDD()
{
HHH(DDD);
return;
}
int main()
{
HHH(DDD);
}
Every expert in the C programming language knows that
DDD correctly simulated by any HHH cannot possibly reach
its own "return" instruction halt state.
Nope, only those that think they are experts but don't actually know what they are talking about.
If HHH(DDD) return 0, it returns 0 to the PROGRAM DDD that it is emulating a copy of, and thus that DDD will halt.
The PARTIAL emulaition of DDD that HHH does is NOT a "correct emulation" and thus your premise is just inocrrect.
Note, if *THE* HHH (and there can only be one at a time in a given problem) NEVER aborts, (and thus doesn't answer, and thus is not a decider) then the DDD built on it will not reach the return instruction, but that has clearly not be the only and only HHH that you are talking about, and thus your claim is just a LIE.
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 |