Path: ...!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail
From: olcott <polcott333@gmail.com>
Newsgroups: comp.theory
Subject: Re: Hypothetical possibilities --- Complete Proof -- more details
Date: Fri, 2 Aug 2024 22:30:40 -0500
Organization: A noiseless patient Spider
Lines: 99
Message-ID: <v8k890$38685$2@dont-email.me>
References: <v7gl30$3j9fi$1@dont-email.me> <v8306v$3c7$1@news.muc.de>
 <v83161$3dftr$11@dont-email.me> <v84udt$3rp4t$1@dont-email.me>
 <v8bc6j$159av$1@dont-email.me>
 <ea673a5b4ed43fbddf938c69bd013b0cf2ca325d@i2pn2.org>
 <v8c6kb$1de3l$1@dont-email.me>
 <9f3112e056ad6eebf35f940c34b802b46addcad4@i2pn2.org>
 <v8cde0$1ecgo$1@dont-email.me> <v8ctgt$1gbu7$4@dont-email.me>
 <v8dkc3$1kii7$3@dont-email.me> <v8e55v$1nrnh$1@dont-email.me>
 <v8e9vu$1oqd7$1@dont-email.me> <v8fftq$22ege$3@dont-email.me>
 <v8fuj5$24rl1$10@dont-email.me> <v8g1j7$24u77$6@dont-email.me>
 <v8g2jl$26d7d$1@dont-email.me> <v8ibf5$2p7ho$1@dont-email.me>
 <s3CdnbweXt8ohDD7nZ2dnZfqn_ednZ2d@brightview.co.uk>
 <a287d1fc2c1fc90d4381e46eae05287b96e801b9@i2pn2.org>
 <-Vednah5VvbtwTD7nZ2dnZfqnPSdnZ2d@brightview.co.uk>
 <87frrmczso.fsf@bsb.me.uk>
 <AZSdncJX-q4WGDD7nZ2dnZfqn_ednZ2d@brightview.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Injection-Date: Sat, 03 Aug 2024 05:30:40 +0200 (CEST)
Injection-Info: dont-email.me; posting-host="6697133516c971b81fd53169bb6a94ea";
	logging-data="3414277"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX1+PLDAaVC82ADaBimZt6NgQ"
User-Agent: Mozilla Thunderbird
Cancel-Lock: sha1:1WkqLuaMruyMRDwh4CIPE6XL2VQ=
Content-Language: en-US
In-Reply-To: <AZSdncJX-q4WGDD7nZ2dnZfqn_ednZ2d@brightview.co.uk>
Bytes: 6176

On 8/2/2024 8:19 PM, Mike Terry wrote:
> On 02/08/2024 23:42, Ben Bacarisse wrote:
>> Mike Terry <news.dead.person.stones@darjeeling.plus.com> writes:
>>
>>> Of course these traces don't support PO's overall case he is claiming,
>>> because the (various) logs show that DDD halts, and that HHH(DDD) 
>>> reports
>>> DDD as non-halting, exactly as Linz/Sipser argue. Er, that's about it!
>>
>> PO certainly used to claim that false (non-halting) is the correct
>> result "even though DDD halts" (I've edited the quote to reflect a name
>> change).  Unless he's changed this position, the traces do support his
>> claim that what everyone else calls the wrong answer is actually the
>> right one.
>>
> 
> So, in your opinion, what do you believe is PO's criterion for "correct 
> result", exactly?  It would be handy if you can give a proper 
> mathematical definition so nobody will have any doubt what it is. Hey, I 
> know you're more than capable of getting a definition right, so let's 
> have that definition!
> 
> Definition:  A TM P given input I is said to "halt" iff ?????
>               or whatever...
> 
> It's easy enough to say "PO has his own criterion for halting, which is 
> materially different from the HP condition, and so we all agree PO is 
> correct by his own criterion, but that does not say anything about the 
> HP theorem because it is different from the HP definition".
> 
> But is that /really/ something PO agrees with?  I don't think so 
> somehow, because I'm pretty sure PO believes his claim "refutes" the HP 
> result.  He wouldn't say that if he freely acknowleded that he had 
> invented a completely different definition for halting.  Also, for what 
> you're saying to be the right way of looking at things, PO would have to 
> admit that the HP proof with its standard definition of halting is 
> valid, and that there is nothing wrong with the Linz proof, other than 
> it not applying to his own favourite PO-halting definition.
> 
> I.e. I think your way of looking at it is a bit "too easy" - but I'd be 
> happy to be convinced! Personally I suspect PO has no such "new and 
> different definition" and that anything along those lines PO is thinking 
> of will be quite incoherent.  No doubt you could make some definition 
> that is at least coherent but we have to ask ourselves - is that 
> definition /really/ what PO is thinking???
> 
> Nowadays, I think PO's position is more that:
> -  yes, DDD() halts when run directly
> -  but DDD() when it runs inside HHH simulator /really/ does not halt, 
> in some kind of
>     sense that it /really/ has infinite recursion which would never end
>     however far it was simulated (because it "exhibits" infinite 
> recursion in some way)
> -  and yes, DDD() /does/ halt when simulated within UTM(DDD),
> -  but the behaviour of DDD depends on who is simulating it.  It 
> terminates when
>     UTM simulates it, but doesn't terminate when HHH simulates it, due 
> to some
>     kind of pathelogical relationship specifically with HHH.  This 
> difference in
>     simulation is /more/ than one simulator aborting earlier than the 
> other...
> 
> 
> Mike.
> 

There are zero flaws in my logic that DDD correctly emulated
by HHH cannot possibly reach its own return instruction,
thus never halts.

void DDD()
{
   HHH(DDD);
   return;
}

Deciders only operate on finite string inputs and never
have operated on executing Turing Machines. This is the
key mistake that everyone including Linz has made.

This means that the behavior of DDD emulated by HHH
according to the x86 semantics of DDD and HHH <is> the
deciding factor and the behavior of the directly executed
DDD() has always been moot.

Everyone that disagreed that the simulation is correct is
disagreeing with the semantics of the x86 language and
that is not allowed.

It is easy to assume that the behavior of the correctly
emulated input must be the same as the direct execution
because this <is> that way that it has worked with every
other computation. This <is> proven to be a false assumption.


-- 
Copyright 2024 Olcott "Talent hits a target no one else can hit; Genius
hits a target no one else can see." Arthur Schopenhauer