Rocksolid Light

Welcome to novaBBS (click a section below)

mail  files  register  newsreader  groups  login

Message-ID:  

If Bill Gates is the Devil then Linus Torvalds must be the Messiah. -- Unknown source


devel / comp.theory / Re: Infinitely Recursive input on HP Proofs

SubjectAuthor
* Infinitely Recursive input on HP Proofsolcott
+- Infinitely Recursive input on HP ProofsJeff Barnett
+- Infinitely Recursive input on HP ProofsRichard Damon
`* Infinitely Recursive input on HP ProofsBen Bacarisse
 `* Infinitely Recursive input on HP Proofsolcott
  +* Infinitely Recursive input on HP ProofsRichard Damon
  |`* Infinitely Recursive input on HP Proofsolcott
  | `* Infinitely Recursive input on HP ProofsRichard Damon
  |  `* Infinitely Recursive input on HP Proofsolcott
  |   +* Infinitely Recursive input on HP ProofsRichard Damon
  |   |`* Infinitely Recursive input on HP Proofsolcott
  |   | `* Infinitely Recursive input on HP ProofsRichard Damon
  |   |  `* Infinitely Recursive input on HP Proofsolcott
  |   |   +- Infinitely Recursive input on HP ProofsRichard Damon
  |   |   `* Infinitely Recursive input on HP ProofsRichard Damon
  |   |    `* Infinitely Recursive input on HP ProofsMalcolm McLean
  |   |     +* Infinitely Recursive input on HP Proofsolcott
  |   |     |`- Infinitely Recursive input on HP ProofsRichard Damon
  |   |     `* Infinitely Recursive input on HP ProofsBen Bacarisse
  |   |      `* Infinitely Recursive input on HP Proofsolcott
  |   |       +* Infinitely Recursive input on HP ProofsBen Bacarisse
  |   |       |`* Infinitely Recursive input on HP Proofsolcott
  |   |       | +- Infinitely Recursive input on HP ProofsRichard Damon
  |   |       | `- Infinitely Recursive input on HP ProofsBen Bacarisse
  |   |       `- Infinitely Recursive input on HP ProofsRichard Damon
  |   `* Infinitely Recursive input on HP ProofsAndré G. Isaak
  |    `* Infinitely Recursive input on HP Proofsolcott
  |     `- Infinitely Recursive input on HP ProofsRichard Damon
  `* Infinitely Recursive input on HP ProofsBen Bacarisse
   `* Infinitely Recursive input on HP Proofs (Full Linz text)olcott
    `* Infinitely Recursive input on HP Proofs (Full Linz text)Ben Bacarisse
     `- Infinitely Recursive input on HP Proofs (eternally on this point)olcott

Pages:12
Re: Infinitely Recursive input on HP Proofs

<a4ydnWkMIKhS8Dz9nZ2dnUU7-L3NnZ2d@giganews.com>

  copy mid

https://www.novabbs.com/devel/article-flat.php?id=15579&group=comp.theory#15579

  copy link   Newsgroups: comp.theory
Path: i2pn2.org!i2pn.org!weretis.net!feeder6.news.weretis.net!news.snarked.org!border2.nntp.dca1.giganews.com!nntp.giganews.com!buffer2.nntp.dca1.giganews.com!news.giganews.com.POSTED!not-for-mail
NNTP-Posting-Date: Sun, 16 May 2021 14:09:03 -0500
Subject: Re: Infinitely Recursive input on HP Proofs
Newsgroups: comp.theory
References: <918df253-d4f0-4370-8f73-88e6690380a1@googlegroups.com>
From: NoO...@NoWhere.com (olcott)
Date: Sun, 16 May 2021 14:09:59 -0500
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101
Thunderbird/78.10.1
MIME-Version: 1.0
In-Reply-To: <918df253-d4f0-4370-8f73-88e6690380a1@googlegroups.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Message-ID: <a4ydnWkMIKhS8Dz9nZ2dnUU7-L3NnZ2d@giganews.com>
Lines: 48
X-Usenet-Provider: http://www.giganews.com
X-Trace: sv3-uRX4IriegNLTD1mwuctfTwhC/QRfldkXaigpu111ODBs0MM+ktk/p9lj2+re+XtBzNd2s2zt1pc5O12!Ces/BTEdEKQtXLPSKECoP40F7/1h4gsgdpttYbccuo4PXYmm/d7JUepFa6Dfop1x+dn/jxhNFp+l!4g==
X-Complaints-To: abuse@giganews.com
X-DMCA-Notifications: http://www.giganews.com/info/dmca.html
X-Abuse-and-DMCA-Info: Please be sure to forward a copy of ALL headers
X-Abuse-and-DMCA-Info: Otherwise we will be unable to process your complaint properly
X-Postfilter: 1.3.40
X-Original-Bytes: 2977
 by: olcott - Sun, 16 May 2021 19:09 UTC

On 3/11/2017 3:13 PM, peteolcott wrote:
> http://LiarParadox.org/HP_Infinite_Recursion.pdf
>
> As this page 319 of An Introduction to Formal Languages and Automata
> by Peter Linz 1990 indicates
>
> From H' we construct another Turing machine H-Hat. This new machine takes as input Wm, copies it then behaves exactly like H'.
>
> q0 Wm |-* H-Hat q0 Wm Wm...
>
> Page 320 indicates that we apply H-Hat to itself as input.
>
> The problem is that every H-Hat needs a pair of inputs.
>
> H-Hat takes an H-Hat as input and copies it so that it
> can analyze how its input H-hat would analyze the copy
> of H-Hat that it just made.
>
> The input H-Hat would have to copy its own input H-Hat
> so that it can analyze what its own input H-Hat would
> do on its own input, on and on forever...
>
> Copyright 2016 and 2017 Pete Olcott.
>

Any genius knowing the theory of computation quite well can easily
confirm that Ĥ(Ĥ) specifies the non halting behavior pattern of
[infinitely_nested_simulation] to every simulating halt decider.
This equally applies to all of the halting problem instances.

Ĥ(Ĥ) is short-hand for:
Now Ĥ is a Turing machine, so that it will have some description in Σ*,
say ŵ. This string, in addition to being the description of Ĥ can also
be used
as input string. We can therefore legitimately ask what would happen if Ĥ is
applied to ŵ. (Linz:1990:320)

Linz, Peter 1990. An Introduction to Formal Languages and Automata.
Lexington/Toronto: D. C. Heath and Company. (315-320)

http://www.liarparadox.org/Peter_Linz_HP(Pages_315-320).pdf

--
Copyright 2021 Pete Olcott

"Great spirits have always encountered violent opposition from mediocre
minds." Einstein

Re: Infinitely Recursive input on HP Proofs

<s7rsqh$8rg$1@dont-email.me>

  copy mid

https://www.novabbs.com/devel/article-flat.php?id=15584&group=comp.theory#15584

  copy link   Newsgroups: comp.theory
Path: i2pn2.org!i2pn.org!eternal-september.org!reader02.eternal-september.org!.POSTED!not-for-mail
From: jbb...@notatt.com (Jeff Barnett)
Newsgroups: comp.theory
Subject: Re: Infinitely Recursive input on HP Proofs
Date: Sun, 16 May 2021 13:46:19 -0600
Organization: A noiseless patient Spider
Lines: 24
Message-ID: <s7rsqh$8rg$1@dont-email.me>
References: <918df253-d4f0-4370-8f73-88e6690380a1@googlegroups.com>
<a4ydnWkMIKhS8Dz9nZ2dnUU7-L3NnZ2d@giganews.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Injection-Date: Sun, 16 May 2021 19:46:26 -0000 (UTC)
Injection-Info: reader02.eternal-september.org; posting-host="f826f7f720cbb7986a92dffc0710d5bf";
logging-data="9072"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1/YWPUIlsMBbVedPwvpjJOm/PaflqTWvQw="
User-Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:78.0) Gecko/20100101
Thunderbird/78.10.1
Cancel-Lock: sha1:h764oS6KW/rDDHFfRmnouVzmpjQ=
In-Reply-To: <a4ydnWkMIKhS8Dz9nZ2dnUU7-L3NnZ2d@giganews.com>
Content-Language: en-US
 by: Jeff Barnett - Sun, 16 May 2021 19:46 UTC

On 5/16/2021 1:09 PM, olcott wrote:
> On 3/11/2017 3:13 PM, peteolcott wrote:

> Any genius knowing the theory of computation

Ah, we are at the heart of the matter!!!!

1) You are not a genius, not even close. Just a lonesome troll feeding
on newsgroup interactions for the human interactions in her/his life.

2) You have shown no knowledge of theory of computation or, its
engineering kin, software engineer.

I think your life would be much more fulfilling if you wrote a
foundational paper "Cut and Pasting, Theory and Practice" and then a
minor epic such as "Emphasis from the Cap Key and Repetition". Together
they would revolutionize keyboard designs and give you a firm place in
the history of the field. Trolling, at last, would be put on a firm
scientific and engineering foundation and could join other modern
occupations that are well prepared for the future.

BTW, don't forget to patent and copyright your papers.
--
Jeff Barnett

Re: Infinitely Recursive input on HP Proofs

<tNeoI.197819$sd3.1379@fx02.iad>

  copy mid

https://www.novabbs.com/devel/article-flat.php?id=15585&group=comp.theory#15585

  copy link   Newsgroups: comp.theory
Path: i2pn2.org!i2pn.org!paganini.bofh.team!news.dns-netz.com!news.freedyn.net!newsfeed.xs4all.nl!newsfeed7.news.xs4all.nl!news-out.netnews.com!newsin.alt.net!fdcspool1.netnews.com!news-out.netnews.com!news.alt.net!fdc3.netnews.com!peer03.ams1!peer.ams1.xlned.com!news.xlned.com!peer03.iad!feed-me.highwinds-media.com!news.highwinds-media.com!fx02.iad.POSTED!not-for-mail
Subject: Re: Infinitely Recursive input on HP Proofs
Newsgroups: comp.theory
References: <918df253-d4f0-4370-8f73-88e6690380a1@googlegroups.com>
<a4ydnWkMIKhS8Dz9nZ2dnUU7-L3NnZ2d@giganews.com>
From: Rich...@Damon-Family.org (Richard Damon)
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:78.0)
Gecko/20100101 Thunderbird/78.10.1
MIME-Version: 1.0
In-Reply-To: <a4ydnWkMIKhS8Dz9nZ2dnUU7-L3NnZ2d@giganews.com>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Lines: 70
Message-ID: <tNeoI.197819$sd3.1379@fx02.iad>
X-Complaints-To: abuse@easynews.com
Organization: Forte - www.forteinc.com
X-Complaints-Info: Please be sure to forward a copy of ALL headers otherwise we will be unable to process your complaint properly.
Date: Sun, 16 May 2021 15:56:09 -0400
X-Received-Bytes: 3733
 by: Richard Damon - Sun, 16 May 2021 19:56 UTC

On 5/16/21 3:09 PM, olcott wrote:
> On 3/11/2017 3:13 PM, peteolcott wrote:
>> http://LiarParadox.org/HP_Infinite_Recursion.pdf
>>
>> As this page 319 of An Introduction to Formal Languages and Automata
>> by Peter Linz 1990 indicates
>>
>>  From H' we construct another Turing machine H-Hat. This new machine
>> takes as input Wm, copies it then behaves exactly like H'.
>>   q0 Wm |-* H-Hat q0 Wm Wm...
>>
>> Page 320 indicates that we apply H-Hat to itself as input.
>>
>> The problem is that every H-Hat needs a pair of inputs.
>>
>> H-Hat takes an H-Hat as input and copies it so that it
>> can analyze how its input H-hat would analyze the copy
>> of H-Hat that it just made.
>>
>> The input H-Hat would have to copy its own input H-Hat
>> so that it can analyze what its own input H-Hat would
>> do on its own input, on and on forever...
>>
>> Copyright 2016 and 2017 Pete Olcott.
>>
>
> Any genius knowing the theory of computation quite well can easily
> confirm that Ĥ(Ĥ) specifies the non halting behavior pattern of
> [infinitely_nested_simulation] to every simulating halt decider.
> This equally applies to all of the halting problem instances.

Only if said genius is blind, and doesn't look at the actual behavior of
H^(H^) which even YOU admit halts.

That a simulation Halt Decider can't decide it doesn't make it
non-halting, just that simulation can't handle that type of machine,
which is the fault of the design of the desider.

H^(H^) CAN'T be infinitely recursive, as H(P, I) is required to be
halting for ALL possible inputs P and I, so must be for H^, H^.

>
> Ĥ(Ĥ) is short-hand for:
> Now Ĥ is a Turing machine, so that it will have some description in Σ*,
> say ŵ. This string, in addition to being the description of Ĥ can also
> be used
> as input string. We can therefore legitimately ask what would happen if
> Ĥ is
> applied to ŵ. (Linz:1990:320)
>
> Linz, Peter 1990. An Introduction to Formal Languages and Automata.
> Lexington/Toronto: D. C. Heath and Company. (315-320)
>
> http://www.liarparadox.org/Peter_Linz_HP(Pages_315-320).pdf
>
>

Yes, and since H is defined to be finite in execution for all inputs, H^
can not get locked into an infinite recursion.

H^ CAN have infinite execution, but only if H says H(H^,H^) is a halting
computation.

The other possibility is if H fails to meet the requirement of being
non-Halting, but in that case, H failed to qualify for the proof, so it
doesn't need to be refuted.

So, the only way you can say that H^(H^) has infinite recursion is to
admit that H(H^, H^) also has infinite recursion and thus fails to
qualify as a decider in the first place.

Re: Infinitely Recursive input on HP Proofs

<87im3i5t12.fsf@bsb.me.uk>

  copy mid

https://www.novabbs.com/devel/article-flat.php?id=15590&group=comp.theory#15590

  copy link   Newsgroups: comp.theory
Path: i2pn2.org!i2pn.org!eternal-september.org!reader02.eternal-september.org!.POSTED!not-for-mail
From: ben.use...@bsb.me.uk (Ben Bacarisse)
Newsgroups: comp.theory
Subject: Re: Infinitely Recursive input on HP Proofs
Date: Sun, 16 May 2021 21:21:29 +0100
Organization: A noiseless patient Spider
Lines: 29
Message-ID: <87im3i5t12.fsf@bsb.me.uk>
References: <918df253-d4f0-4370-8f73-88e6690380a1@googlegroups.com>
<a4ydnWkMIKhS8Dz9nZ2dnUU7-L3NnZ2d@giganews.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
Injection-Info: reader02.eternal-september.org; posting-host="4a1d6728404b495b2ff33612faae7f55";
logging-data="4229"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX18XWuFKFY4rhN5wei3NGhrMAt7QUAQv+0Y="
Cancel-Lock: sha1:7zJHvt2cNxa5uRi2ycxHqFexGvY=
sha1:jVAirs3wQFklhDqnwZtcplqWaJM=
X-BSB-Auth: 1.31c66298d93e74bbf86a.20210516212129BST.87im3i5t12.fsf@bsb.me.uk
 by: Ben Bacarisse - Sun, 16 May 2021 20:21 UTC

olcott <NoOne@NoWhere.com> writes:

> Any genius knowing the theory of computation quite well can easily
> confirm that Ĥ(Ĥ) specifies the non halting behavior pattern of
> [infinitely_nested_simulation] to every simulating halt decider.
> This equally applies to all of the halting problem instances.
>
> Ĥ(Ĥ) is short-hand for:
> Now Ĥ is a Turing machine, so that it will have some description in Σ*,
> say ŵ. This string, in addition to being the description of Ĥ can also be used
> as input string. We can therefore legitimately ask what would happen if Ĥ is
> applied to ŵ. (Linz:1990:320)
>
> Linz, Peter 1990. An Introduction to Formal Languages and
> Automata. Lexington/Toronto: D. C. Heath and Company. (315-320)

Nonsense. H is the name given in Linz to a non-existent Turing
machine. H^, derived from it, also does not exit. Anyone who has read
that book should know that H^([H^]) specifies no behaviour at all.

You have constructed a poor-man's partial decider that gets the "hat"
case wrong, but you can't justify the wrong answer by appeal Linz.

Your "infinitely nested simulation" explanation for your decider giving
the wrong answer can be put on a more formal basis, but you can't do by
re-using the names of nonexistent TM's from Linz.

--
Ben.

Re: Infinitely Recursive input on HP Proofs

<0sCdnWsgz4JPGjz9nZ2dnUU7-RvNnZ2d@giganews.com>

  copy mid

https://www.novabbs.com/devel/article-flat.php?id=15594&group=comp.theory#15594

  copy link   Newsgroups: comp.theory comp.ai.philosophy sci.math sci.math.symbolic
Followup: comp.theory
Path: i2pn2.org!i2pn.org!weretis.net!feeder6.news.weretis.net!4.us.feeder.erje.net!2.eu.feeder.erje.net!feeder.erje.net!newsfeed.xs4all.nl!newsfeed9.news.xs4all.nl!tr1.eu1.usenetexpress.com!feeder.usenetexpress.com!tr3.iad1.usenetexpress.com!border1.nntp.dca1.giganews.com!nntp.giganews.com!buffer1.nntp.dca1.giganews.com!buffer2.nntp.dca1.giganews.com!news.giganews.com.POSTED!not-for-mail
NNTP-Posting-Date: Sun, 16 May 2021 16:00:02 -0500
Subject: Re: Infinitely Recursive input on HP Proofs
Newsgroups: comp.theory,comp.ai.philosophy,sci.math,sci.math.symbolic
References: <918df253-d4f0-4370-8f73-88e6690380a1@googlegroups.com> <a4ydnWkMIKhS8Dz9nZ2dnUU7-L3NnZ2d@giganews.com> <87im3i5t12.fsf@bsb.me.uk>
From: NoO...@NoWhere.com (olcott)
Followup-To: comp.theory
Date: Sun, 16 May 2021 16:00:57 -0500
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.10.1
MIME-Version: 1.0
In-Reply-To: <87im3i5t12.fsf@bsb.me.uk>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Message-ID: <0sCdnWsgz4JPGjz9nZ2dnUU7-RvNnZ2d@giganews.com>
Lines: 80
X-Usenet-Provider: http://www.giganews.com
X-Trace: sv3-ve01StAg39Wioaiy8BhIK9l3NEtrBk1JwRvr9voD9iOUYFO3ckKTgJ3WddIbNSWbGt8EYJnBTxnPR7U!U4fhsaBDYeVYfV2RC4CQpsfDe+LIi65Y9YIpKeE2C4qXPSSiEHNZ63/3QXLGOIC5ovzLcMgNwCyt!oA==
X-Complaints-To: abuse@giganews.com
X-DMCA-Notifications: http://www.giganews.com/info/dmca.html
X-Abuse-and-DMCA-Info: Please be sure to forward a copy of ALL headers
X-Abuse-and-DMCA-Info: Otherwise we will be unable to process your complaint properly
X-Postfilter: 1.3.40
X-Original-Bytes: 4823
 by: olcott - Sun, 16 May 2021 21:00 UTC

On 5/16/2021 3:21 PM, Ben Bacarisse wrote:
> olcott <NoOne@NoWhere.com> writes:
>
>> Any genius knowing the theory of computation quite well can easily
>> confirm that Ĥ(Ĥ) specifies the non halting behavior pattern of
>> [infinitely_nested_simulation] to every simulating halt decider.
>> This equally applies to all of the halting problem instances.
>>
>> Ĥ(Ĥ) is short-hand for:
>> Now Ĥ is a Turing machine, so that it will have some description in Σ*,
>> say ŵ. This string, in addition to being the description of Ĥ can also be used
>> as input string. We can therefore legitimately ask what would happen if Ĥ is
>> applied to ŵ. (Linz:1990:320)
>>
>> Linz, Peter 1990. An Introduction to Formal Languages and
>> Automata. Lexington/Toronto: D. C. Heath and Company. (315-320)
>
> Nonsense. H is the name given in Linz to a non-existent Turing
> machine. H^, derived from it, also does not exit. Anyone who has read
> that book should know that H^([H^]) specifies no behaviour at all.
>
> You have constructed a poor-man's partial decider that gets the "hat"
> case wrong, but you can't justify the wrong answer by appeal Linz.
>
> Your "infinitely nested simulation" explanation for your decider giving
> the wrong answer can be put on a more formal basis, but you can't do by
> re-using the names of nonexistent TM's from Linz.
>

Well I won't say that you are not a genius or that you don't know the
theory of computation very well.

The actual Ĥ(<Ĥ>) does specify [infinitely_nested_simulation] to every
simulating halt decider. This [infinitely_nested_simulation] is more
complex than the one that Halts recognizes.

Ĥ.q0 wM ⊢* Ĥ.qx wM wM ⊢* Ĥ.qy ∞
Ĥ.q0 wM ⊢* Ĥ.qx wM wM ⊢* Ĥ.qn

The above is adapted from (Linz:1990:319).
It shows that Turing machine Ĥ copies its input at (q0) and begins
executing an embedded copy of the original halt decider with this input
at (qx).

The (qy) state indicates that the halt decider decides that its input
would halt. The ((qn)) state indicates the input would not halt. The
appended (qa) and (qb) states cause Ĥ to infinitely loop if the halt
decider decides that its input would halt.

It can be understood from the above specification that when the embedded
halt decider @Ĥ.qx bases its halting decision on simulating its input,
and it has (Ĥ, Ĥ) as its input that:
Ĥ.q0 would copy its input and then Ĥ.qx would simulate its input with
this copy then
Ĥ.q0 would copy its input and then Ĥ.qx would simulate its input with
this copy then
Ĥ.q0 would copy its input and then Ĥ.qx would simulate its input with
this copy...
unless and until the halt decider @Ĥ.qx stops simulating its input.

Linz, Peter 1990. An Introduction to Formal Languages and Automata.
Lexington/Toronto: D. C. Heath and Company.

So it seems to be the same as it was more than four years ago you are so
biased against either me or my position (or both) that you simply won't
pay enough attention to see that I am right.

The key evidence that I am right and you just don't see it is the lack
of any correct rebuttal.

That the actual Ĥ(<Ĥ>) does specify [infinitely_nested_simulation] to
every simulating halt decider can't be refuted simply because <it is>
the case.

--
Copyright 2021 Pete Olcott

"Great spirits have always encountered violent opposition from mediocre
minds." Einstein

Re: Infinitely Recursive input on HP Proofs

<R%foI.542844$nn2.335922@fx48.iad>

  copy mid

https://www.novabbs.com/devel/article-flat.php?id=15597&group=comp.theory#15597

  copy link   Newsgroups: comp.theory
Path: i2pn2.org!i2pn.org!weretis.net!feeder8.news.weretis.net!news.mixmin.net!fdcspool5.netnews.com!news-out.netnews.com!news.alt.net!fdc2.netnews.com!peer02.ams1!peer.ams1.xlned.com!news.xlned.com!peer02.iad!feed-me.highwinds-media.com!news.highwinds-media.com!fx48.iad.POSTED!not-for-mail
Subject: Re: Infinitely Recursive input on HP Proofs
Newsgroups: comp.theory
References: <918df253-d4f0-4370-8f73-88e6690380a1@googlegroups.com>
<a4ydnWkMIKhS8Dz9nZ2dnUU7-L3NnZ2d@giganews.com> <87im3i5t12.fsf@bsb.me.uk>
<0sCdnWsgz4JPGjz9nZ2dnUU7-RvNnZ2d@giganews.com>
From: Rich...@Damon-Family.org (Richard Damon)
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:78.0)
Gecko/20100101 Thunderbird/78.10.1
MIME-Version: 1.0
In-Reply-To: <0sCdnWsgz4JPGjz9nZ2dnUU7-RvNnZ2d@giganews.com>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Lines: 98
Message-ID: <R%foI.542844$nn2.335922@fx48.iad>
X-Complaints-To: abuse@easynews.com
Organization: Forte - www.forteinc.com
X-Complaints-Info: Please be sure to forward a copy of ALL headers otherwise we will be unable to process your complaint properly.
Date: Sun, 16 May 2021 17:19:45 -0400
X-Received-Bytes: 5349
 by: Richard Damon - Sun, 16 May 2021 21:19 UTC

On 5/16/21 5:00 PM, olcott wrote:
> On 5/16/2021 3:21 PM, Ben Bacarisse wrote:
>> olcott <NoOne@NoWhere.com> writes:
>>
>>> Any genius knowing the theory of computation quite well can easily
>>> confirm that Ĥ(Ĥ) specifies the non halting behavior pattern of
>>> [infinitely_nested_simulation] to every simulating halt decider.
>>> This equally applies to all of the halting problem instances.
>>>
>>> Ĥ(Ĥ) is short-hand for:
>>> Now Ĥ is a Turing machine, so that it will have some description in Σ*,
>>> say ŵ. This string, in addition to being the description of Ĥ can
>>> also be used
>>> as input string. We can therefore legitimately ask what would happen
>>> if Ĥ is
>>> applied to ŵ. (Linz:1990:320)
>>>
>>> Linz, Peter 1990. An Introduction to Formal Languages and
>>> Automata. Lexington/Toronto: D. C. Heath and Company. (315-320)
>>
>> Nonsense.  H is the name given in Linz to a non-existent Turing
>> machine.  H^, derived from it, also does not exit.  Anyone who has read
>> that book should know that H^([H^]) specifies no behaviour at all.
>>
>> You have constructed a poor-man's partial decider that gets the "hat"
>> case wrong, but you can't justify the wrong answer by appeal Linz.
>>
>> Your "infinitely nested simulation" explanation for your decider giving
>> the wrong answer can be put on a more formal basis, but you can't do by
>> re-using the names of nonexistent TM's from Linz.
>>
>
> Well I won't say that you are not a genius or that you don't know the
> theory of computation very well.
>
> The actual Ĥ(<Ĥ>) does specify [infinitely_nested_simulation] to every
> simulating halt decider. This [infinitely_nested_simulation] is more
> complex than the one that Halts recognizes.
>
> Ĥ.q0  wM  ⊢*  Ĥ.qx  wM  wM  ⊢*  Ĥ.qy  ∞
> Ĥ.q0  wM  ⊢*  Ĥ.qx  wM  wM  ⊢*  Ĥ.qn
>
> The above is adapted from (Linz:1990:319).
> It shows that Turing machine Ĥ copies its input at (q0) and begins
> executing an embedded copy of the original halt decider with this input
> at (qx).
>
> The (qy) state indicates that the halt decider decides that its input
> would halt. The ((qn)) state indicates the input would not halt. The
> appended (qa) and (qb) states cause Ĥ to infinitely loop if the halt
> decider decides that its input would halt.
>
> It can be understood from the above specification that when the embedded
> halt decider @Ĥ.qx bases its halting decision on simulating its input,
> and it has (Ĥ,  Ĥ) as its input that:
> Ĥ.q0 would copy its input and then Ĥ.qx would simulate its input with
> this copy then
> Ĥ.q0 would copy its input and then Ĥ.qx would simulate its input with
> this copy then
> Ĥ.q0 would copy its input and then Ĥ.qx would simulate its input with
> this copy...
> unless and until the halt decider @Ĥ.qx stops simulating its input.

BUT, since H is required to be finite in execution, the copy of H within
H^ must have some alteration from a simple simulator to break the loop.

If it does, then it WILL break the loop, and be finite in execution.

If it doesn't then H(H^,H^) won't break the loop, and thus will not
answer in finite time and thus fail to give an answer and not be a decider.

The ONLY way you can get one without the other is for H to NOT be a
computation, and thus it can't be a Turing Machine, so your argument
about working with true Turing Equivalents is false.

PERIOD.

You had to move out of Turing Machine because you can't do it as Turing
Machines, which means that something you have claimed to be a 'Turing
Equivalent' isn't.

>
> Linz, Peter 1990. An Introduction to Formal Languages and Automata.
> Lexington/Toronto: D. C. Heath and Company.
>
> So it seems to be the same as it was more than four years ago you are so
> biased against either me or my position (or both) that you simply won't
> pay enough attention to see that I am right.
>
> The key evidence that I am right and you just don't see it is the lack
> of any correct rebuttal.
>
> That the actual Ĥ(<Ĥ>) does specify [infinitely_nested_simulation] to
> every simulating halt decider can't be refuted simply because <it is>
> the case.
>
>

Re: Infinitely Recursive input on HP Proofs

<-rednavQTY_BDTz9nZ2dnUU7-SXNnZ2d@giganews.com>

  copy mid

https://www.novabbs.com/devel/article-flat.php?id=15600&group=comp.theory#15600

  copy link   Newsgroups: comp.theory
Path: i2pn2.org!i2pn.org!weretis.net!feeder6.news.weretis.net!news.snarked.org!border2.nntp.dca1.giganews.com!nntp.giganews.com!buffer2.nntp.dca1.giganews.com!news.giganews.com.POSTED!not-for-mail
NNTP-Posting-Date: Sun, 16 May 2021 16:36:28 -0500
Subject: Re: Infinitely Recursive input on HP Proofs
Newsgroups: comp.theory
References: <918df253-d4f0-4370-8f73-88e6690380a1@googlegroups.com>
<a4ydnWkMIKhS8Dz9nZ2dnUU7-L3NnZ2d@giganews.com> <87im3i5t12.fsf@bsb.me.uk>
<0sCdnWsgz4JPGjz9nZ2dnUU7-RvNnZ2d@giganews.com>
<R%foI.542844$nn2.335922@fx48.iad>
From: NoO...@NoWhere.com (olcott)
Date: Sun, 16 May 2021 16:37:24 -0500
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101
Thunderbird/78.10.1
MIME-Version: 1.0
In-Reply-To: <R%foI.542844$nn2.335922@fx48.iad>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Message-ID: <-rednavQTY_BDTz9nZ2dnUU7-SXNnZ2d@giganews.com>
Lines: 99
X-Usenet-Provider: http://www.giganews.com
X-Trace: sv3-6Vqz50/ACnsNkl/LTBzujRcxBsfptGy0mFLWpeEa0VG3667Qg+LEM1Au+LbgLGCTjvdn7Br+Nmv7o54!Uw7o1H0/MifOliSiVqW2IFJvReAWFIirUrULYRmp+5cFxcCgGxZQJrLz9w9SJ8JPx++Z37hlmVTb!Gg==
X-Complaints-To: abuse@giganews.com
X-DMCA-Notifications: http://www.giganews.com/info/dmca.html
X-Abuse-and-DMCA-Info: Please be sure to forward a copy of ALL headers
X-Abuse-and-DMCA-Info: Otherwise we will be unable to process your complaint properly
X-Postfilter: 1.3.40
X-Original-Bytes: 5708
 by: olcott - Sun, 16 May 2021 21:37 UTC

On 5/16/2021 4:19 PM, Richard Damon wrote:
> On 5/16/21 5:00 PM, olcott wrote:
>> On 5/16/2021 3:21 PM, Ben Bacarisse wrote:
>>> olcott <NoOne@NoWhere.com> writes:
>>>
>>>> Any genius knowing the theory of computation quite well can easily
>>>> confirm that Ĥ(Ĥ) specifies the non halting behavior pattern of
>>>> [infinitely_nested_simulation] to every simulating halt decider.
>>>> This equally applies to all of the halting problem instances.
>>>>
>>>> Ĥ(Ĥ) is short-hand for:
>>>> Now Ĥ is a Turing machine, so that it will have some description in Σ*,
>>>> say ŵ. This string, in addition to being the description of Ĥ can
>>>> also be used
>>>> as input string. We can therefore legitimately ask what would happen
>>>> if Ĥ is
>>>> applied to ŵ. (Linz:1990:320)
>>>>
>>>> Linz, Peter 1990. An Introduction to Formal Languages and
>>>> Automata. Lexington/Toronto: D. C. Heath and Company. (315-320)
>>>
>>> Nonsense.  H is the name given in Linz to a non-existent Turing
>>> machine.  H^, derived from it, also does not exit.  Anyone who has read
>>> that book should know that H^([H^]) specifies no behaviour at all.
>>>
>>> You have constructed a poor-man's partial decider that gets the "hat"
>>> case wrong, but you can't justify the wrong answer by appeal Linz.
>>>
>>> Your "infinitely nested simulation" explanation for your decider giving
>>> the wrong answer can be put on a more formal basis, but you can't do by
>>> re-using the names of nonexistent TM's from Linz.
>>>
>>
>> Well I won't say that you are not a genius or that you don't know the
>> theory of computation very well.
>>
>> The actual Ĥ(<Ĥ>) does specify [infinitely_nested_simulation] to every
>> simulating halt decider. This [infinitely_nested_simulation] is more
>> complex than the one that Halts recognizes.
>>
>> Ĥ.q0  wM  ⊢*  Ĥ.qx  wM  wM  ⊢*  Ĥ.qy  ∞
>> Ĥ.q0  wM  ⊢*  Ĥ.qx  wM  wM  ⊢*  Ĥ.qn
>>
>> The above is adapted from (Linz:1990:319).
>> It shows that Turing machine Ĥ copies its input at (q0) and begins
>> executing an embedded copy of the original halt decider with this input
>> at (qx).
>>
>> The (qy) state indicates that the halt decider decides that its input
>> would halt. The ((qn)) state indicates the input would not halt. The
>> appended (qa) and (qb) states cause Ĥ to infinitely loop if the halt
>> decider decides that its input would halt.
>>
>> It can be understood from the above specification that when the embedded
>> halt decider @Ĥ.qx bases its halting decision on simulating its input,
>> and it has (Ĥ,  Ĥ) as its input that:
>> Ĥ.q0 would copy its input and then Ĥ.qx would simulate its input with
>> this copy then
>> Ĥ.q0 would copy its input and then Ĥ.qx would simulate its input with
>> this copy then
>> Ĥ.q0 would copy its input and then Ĥ.qx would simulate its input with
>> this copy...
>> unless and until the halt decider @Ĥ.qx stops simulating its input.
>
> BUT, since H is required to be finite in execution, the copy of H within
> H^ must have some alteration from a simple simulator to break the loop.
>
> If it does, then it WILL break the loop, and be finite in execution.
>
> If it doesn't then H(H^,H^) won't break the loop, and thus will not
> answer in finite time and thus fail to give an answer and not be a decider.
>

That is why we need this truism to dislodge the pathological
self-reference:

On 5/11/2021 11:10 AM, Ben Bacarisse wrote:
> olcott <NoOne@NoWhere.com> writes:
>
>> Truism:
>> Every simulation that would never stop unless Halts() stops
>> it at some point specifies infinite execution.
>
> Any algorithm that implements this truism is, of course, a halting
> decider.

Whether a computation is finite is more nuanced than it simply stops
running otherwise an infinite loop that had its simulation aborted
because its behavior matched the [infinite_loop] non-halting behavior
pattern would have to be classified as a halting computation.

Unless the simulating halt decider stops simulating Ĥ(Ĥ) at some point
its simulation would be infinite ∴ meets the non-halting truism.

--
Copyright 2021 Pete Olcott

"Great spirits have always encountered violent opposition from mediocre
minds." Einstein

Re: Infinitely Recursive input on HP Proofs

<_yhoI.542847$nn2.449398@fx48.iad>

  copy mid

https://www.novabbs.com/devel/article-flat.php?id=15605&group=comp.theory#15605

  copy link   Newsgroups: comp.theory
Path: i2pn2.org!i2pn.org!paganini.bofh.team!news.dns-netz.com!news.freedyn.net!newsfeed.xs4all.nl!newsfeed7.news.xs4all.nl!fdcspool5.netnews.com!news-out.netnews.com!news.alt.net!fdc2.netnews.com!feeder1.feed.usenet.farm!feed.usenet.farm!peer02.ams4!peer.am4.highwinds-media.com!peer03.iad!feed-me.highwinds-media.com!news.highwinds-media.com!fx48.iad.POSTED!not-for-mail
Subject: Re: Infinitely Recursive input on HP Proofs
Newsgroups: comp.theory
References: <918df253-d4f0-4370-8f73-88e6690380a1@googlegroups.com>
<a4ydnWkMIKhS8Dz9nZ2dnUU7-L3NnZ2d@giganews.com> <87im3i5t12.fsf@bsb.me.uk>
<0sCdnWsgz4JPGjz9nZ2dnUU7-RvNnZ2d@giganews.com>
<R%foI.542844$nn2.335922@fx48.iad>
<-rednavQTY_BDTz9nZ2dnUU7-SXNnZ2d@giganews.com>
From: Rich...@Damon-Family.org (Richard Damon)
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:78.0)
Gecko/20100101 Thunderbird/78.10.1
MIME-Version: 1.0
In-Reply-To: <-rednavQTY_BDTz9nZ2dnUU7-SXNnZ2d@giganews.com>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Lines: 105
Message-ID: <_yhoI.542847$nn2.449398@fx48.iad>
X-Complaints-To: abuse@easynews.com
Organization: Forte - www.forteinc.com
X-Complaints-Info: Please be sure to forward a copy of ALL headers otherwise we will be unable to process your complaint properly.
Date: Sun, 16 May 2021 19:05:29 -0400
X-Received-Bytes: 5883
 by: Richard Damon - Sun, 16 May 2021 23:05 UTC

On 5/16/21 5:37 PM, olcott wrote:
> On 5/16/2021 4:19 PM, Richard Damon wrote:
>> On 5/16/21 5:00 PM, olcott wrote:
>>> On 5/16/2021 3:21 PM, Ben Bacarisse wrote:
>>>> olcott <NoOne@NoWhere.com> writes:
>>>>
>>>>> Any genius knowing the theory of computation quite well can easily
>>>>> confirm that Ĥ(Ĥ) specifies the non halting behavior pattern of
>>>>> [infinitely_nested_simulation] to every simulating halt decider.
>>>>> This equally applies to all of the halting problem instances.
>>>>>
>>>>> Ĥ(Ĥ) is short-hand for:
>>>>> Now Ĥ is a Turing machine, so that it will have some description in
>>>>> Σ*,
>>>>> say ŵ. This string, in addition to being the description of Ĥ can
>>>>> also be used
>>>>> as input string. We can therefore legitimately ask what would happen
>>>>> if Ĥ is
>>>>> applied to ŵ. (Linz:1990:320)
>>>>>
>>>>> Linz, Peter 1990. An Introduction to Formal Languages and
>>>>> Automata. Lexington/Toronto: D. C. Heath and Company. (315-320)
>>>>
>>>> Nonsense.  H is the name given in Linz to a non-existent Turing
>>>> machine.  H^, derived from it, also does not exit.  Anyone who has read
>>>> that book should know that H^([H^]) specifies no behaviour at all.
>>>>
>>>> You have constructed a poor-man's partial decider that gets the "hat"
>>>> case wrong, but you can't justify the wrong answer by appeal Linz.
>>>>
>>>> Your "infinitely nested simulation" explanation for your decider giving
>>>> the wrong answer can be put on a more formal basis, but you can't do by
>>>> re-using the names of nonexistent TM's from Linz.
>>>>
>>>
>>> Well I won't say that you are not a genius or that you don't know the
>>> theory of computation very well.
>>>
>>> The actual Ĥ(<Ĥ>) does specify [infinitely_nested_simulation] to every
>>> simulating halt decider. This [infinitely_nested_simulation] is more
>>> complex than the one that Halts recognizes.
>>>
>>> Ĥ.q0  wM  ⊢*  Ĥ.qx  wM  wM  ⊢*  Ĥ.qy  ∞
>>> Ĥ.q0  wM  ⊢*  Ĥ.qx  wM  wM  ⊢*  Ĥ.qn
>>>
>>> The above is adapted from (Linz:1990:319).
>>> It shows that Turing machine Ĥ copies its input at (q0) and begins
>>> executing an embedded copy of the original halt decider with this input
>>> at (qx).
>>>
>>> The (qy) state indicates that the halt decider decides that its input
>>> would halt. The ((qn)) state indicates the input would not halt. The
>>> appended (qa) and (qb) states cause Ĥ to infinitely loop if the halt
>>> decider decides that its input would halt.
>>>
>>> It can be understood from the above specification that when the embedded
>>> halt decider @Ĥ.qx bases its halting decision on simulating its input,
>>> and it has (Ĥ,  Ĥ) as its input that:
>>> Ĥ.q0 would copy its input and then Ĥ.qx would simulate its input with
>>> this copy then
>>> Ĥ.q0 would copy its input and then Ĥ.qx would simulate its input with
>>> this copy then
>>> Ĥ.q0 would copy its input and then Ĥ.qx would simulate its input with
>>> this copy...
>>> unless and until the halt decider @Ĥ.qx stops simulating its input.
>>
>> BUT, since H is required to be finite in execution, the copy of H within
>> H^ must have some alteration from a simple simulator to break the loop.
>>
>> If it does, then it WILL break the loop, and be finite in execution.
>>
>> If it doesn't then H(H^,H^) won't break the loop, and thus will not
>> answer in finite time and thus fail to give an answer and not be a
>> decider.
>>
>
> That is why we need this truism to dislodge the pathological
> self-reference:
>
> On 5/11/2021 11:10 AM, Ben Bacarisse wrote:
>> olcott <NoOne@NoWhere.com> writes:
>>
>>> Truism:
>>> Every simulation that would never stop unless Halts() stops
>>> it at some point specifies infinite execution.
>>
>> Any algorithm that implements this truism is, of course, a halting
>> decider.
>
> Whether a computation is finite is more nuanced than it simply stops
> running otherwise an infinite loop that had its simulation aborted
> because its behavior matched the [infinite_loop] non-halting behavior
> pattern would have to be classified as a halting computation.
>
> Unless the simulating halt decider stops simulating Ĥ(Ĥ) at some point
> its simulation would be infinite ∴ meets the non-halting truism.
>

But you can't use a 'Falsism' to change the facts about the definition.

And, as I have said, there IS no pathological self-reference in the problem.

YOU create the self-reference by not implementing the required copy
operation. In actuality the Linz proof has no real self-reference, just
two copies of what just happens to be the same thing.

Re: Infinitely Recursive input on HP Proofs

<EsCdnduL051HNTz9nZ2dnUU7-d_NnZ2d@giganews.com>

  copy mid

https://www.novabbs.com/devel/article-flat.php?id=15606&group=comp.theory#15606

  copy link   Newsgroups: comp.theory
Path: i2pn2.org!i2pn.org!paganini.bofh.team!news.dns-netz.com!news.freedyn.net!newsfeed.xs4all.nl!newsfeed8.news.xs4all.nl!tr1.eu1.usenetexpress.com!feeder.usenetexpress.com!tr3.iad1.usenetexpress.com!border1.nntp.dca1.giganews.com!nntp.giganews.com!buffer1.nntp.dca1.giganews.com!news.giganews.com.POSTED!not-for-mail
NNTP-Posting-Date: Sun, 16 May 2021 18:20:58 -0500
Subject: Re: Infinitely Recursive input on HP Proofs
Newsgroups: comp.theory
References: <918df253-d4f0-4370-8f73-88e6690380a1@googlegroups.com> <a4ydnWkMIKhS8Dz9nZ2dnUU7-L3NnZ2d@giganews.com> <87im3i5t12.fsf@bsb.me.uk> <0sCdnWsgz4JPGjz9nZ2dnUU7-RvNnZ2d@giganews.com> <R%foI.542844$nn2.335922@fx48.iad> <-rednavQTY_BDTz9nZ2dnUU7-SXNnZ2d@giganews.com> <_yhoI.542847$nn2.449398@fx48.iad>
From: NoO...@NoWhere.com (olcott)
Date: Sun, 16 May 2021 18:21:53 -0500
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.10.1
MIME-Version: 1.0
In-Reply-To: <_yhoI.542847$nn2.449398@fx48.iad>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Message-ID: <EsCdnduL051HNTz9nZ2dnUU7-d_NnZ2d@giganews.com>
Lines: 144
X-Usenet-Provider: http://www.giganews.com
X-Trace: sv3-LeMeQgwxbiRLChypbsn5LqbUGUR1Z8t+pKzlp4k6SHAlxN3kUpv0NUvpdg1NALEl7kBZUbK6v82W4yr!oA9ZCuY0ymS+qJCIZ1oT+qwK9g1fhWYZBlWMNJzDLxv9TYi8UTLkN3eX8dpnyIN/7ADkmQNBacAq!BQ==
X-Complaints-To: abuse@giganews.com
X-DMCA-Notifications: http://www.giganews.com/info/dmca.html
X-Abuse-and-DMCA-Info: Please be sure to forward a copy of ALL headers
X-Abuse-and-DMCA-Info: Otherwise we will be unable to process your complaint properly
X-Postfilter: 1.3.40
X-Original-Bytes: 7734
 by: olcott - Sun, 16 May 2021 23:21 UTC

On 5/16/2021 6:05 PM, Richard Damon wrote:
> On 5/16/21 5:37 PM, olcott wrote:
>> On 5/16/2021 4:19 PM, Richard Damon wrote:
>>> On 5/16/21 5:00 PM, olcott wrote:
>>>> On 5/16/2021 3:21 PM, Ben Bacarisse wrote:
>>>>> olcott <NoOne@NoWhere.com> writes:
>>>>>
>>>>>> Any genius knowing the theory of computation quite well can easily
>>>>>> confirm that Ĥ(Ĥ) specifies the non halting behavior pattern of
>>>>>> [infinitely_nested_simulation] to every simulating halt decider.
>>>>>> This equally applies to all of the halting problem instances.
>>>>>>
>>>>>> Ĥ(Ĥ) is short-hand for:
>>>>>> Now Ĥ is a Turing machine, so that it will have some description in
>>>>>> Σ*,
>>>>>> say ŵ. This string, in addition to being the description of Ĥ can
>>>>>> also be used
>>>>>> as input string. We can therefore legitimately ask what would happen
>>>>>> if Ĥ is
>>>>>> applied to ŵ. (Linz:1990:320)
>>>>>>
>>>>>> Linz, Peter 1990. An Introduction to Formal Languages and
>>>>>> Automata. Lexington/Toronto: D. C. Heath and Company. (315-320)
>>>>>
>>>>> Nonsense.  H is the name given in Linz to a non-existent Turing
>>>>> machine.  H^, derived from it, also does not exit.  Anyone who has read
>>>>> that book should know that H^([H^]) specifies no behaviour at all.
>>>>>
>>>>> You have constructed a poor-man's partial decider that gets the "hat"
>>>>> case wrong, but you can't justify the wrong answer by appeal Linz.
>>>>>
>>>>> Your "infinitely nested simulation" explanation for your decider giving
>>>>> the wrong answer can be put on a more formal basis, but you can't do by
>>>>> re-using the names of nonexistent TM's from Linz.
>>>>>
>>>>
>>>> Well I won't say that you are not a genius or that you don't know the
>>>> theory of computation very well.
>>>>
>>>> The actual Ĥ(<Ĥ>) does specify [infinitely_nested_simulation] to every
>>>> simulating halt decider. This [infinitely_nested_simulation] is more
>>>> complex than the one that Halts recognizes.
>>>>
>>>> Ĥ.q0  wM  ⊢*  Ĥ.qx  wM  wM  ⊢*  Ĥ.qy  ∞
>>>> Ĥ.q0  wM  ⊢*  Ĥ.qx  wM  wM  ⊢*  Ĥ.qn
>>>>
>>>> The above is adapted from (Linz:1990:319).
>>>> It shows that Turing machine Ĥ copies its input at (q0) and begins
>>>> executing an embedded copy of the original halt decider with this input
>>>> at (qx).
>>>>
>>>> The (qy) state indicates that the halt decider decides that its input
>>>> would halt. The ((qn)) state indicates the input would not halt. The
>>>> appended (qa) and (qb) states cause Ĥ to infinitely loop if the halt
>>>> decider decides that its input would halt.
>>>>
>>>> It can be understood from the above specification that when the embedded
>>>> halt decider @Ĥ.qx bases its halting decision on simulating its input,
>>>> and it has (Ĥ,  Ĥ) as its input that:
>>>> Ĥ.q0 would copy its input and then Ĥ.qx would simulate its input with
>>>> this copy then
>>>> Ĥ.q0 would copy its input and then Ĥ.qx would simulate its input with
>>>> this copy then
>>>> Ĥ.q0 would copy its input and then Ĥ.qx would simulate its input with
>>>> this copy...
>>>> unless and until the halt decider @Ĥ.qx stops simulating its input.
>>>
>>> BUT, since H is required to be finite in execution, the copy of H within
>>> H^ must have some alteration from a simple simulator to break the loop.
>>>
>>> If it does, then it WILL break the loop, and be finite in execution.
>>>
>>> If it doesn't then H(H^,H^) won't break the loop, and thus will not
>>> answer in finite time and thus fail to give an answer and not be a
>>> decider.
>>>
>>
>> That is why we need this truism to dislodge the pathological
>> self-reference:
>>
>> On 5/11/2021 11:10 AM, Ben Bacarisse wrote:
>>> olcott <NoOne@NoWhere.com> writes:
>>>
>>>> Truism:
>>>> Every simulation that would never stop unless Halts() stops
>>>> it at some point specifies infinite execution.
>>>
>>> Any algorithm that implements this truism is, of course, a halting
>>> decider.
>>
>> Whether a computation is finite is more nuanced than it simply stops
>> running otherwise an infinite loop that had its simulation aborted
>> because its behavior matched the [infinite_loop] non-halting behavior
>> pattern would have to be classified as a halting computation.
>>
>> Unless the simulating halt decider stops simulating Ĥ(Ĥ) at some point
>> its simulation would be infinite ∴ meets the non-halting truism.
>>
>
> But you can't use a 'Falsism' to change the facts about the definition.
>
> And, as I have said, there IS no pathological self-reference in the problem.
>
> YOU create the self-reference by not implementing the required copy
> operation. In actuality the Linz proof has no real self-reference, just
> two copies of what just happens to be the same thing.
>

I am referring to the complete Peter Linz version where a copy <is> made.

Ĥ.q0 wM ⊢* Ĥ.qx wM wM ⊢* Ĥ.qy ∞
Ĥ.q0 wM ⊢* Ĥ.qx wM wM ⊢* Ĥ.qn

The above is adapted from (Linz:1990:319).
It shows that Turing machine Ĥ copies its input at (q0) and begins
executing an embedded copy of the original halt decider with this input
at (qx).

The (qy) state indicates that the halt decider decides that its input
would halt. The ((qn)) state indicates the input would not halt. The
appended (qa) and (qb) states cause Ĥ to infinitely loop if the halt
decider decides that its input would halt.

It can be understood from the above specification that when the embedded
halt decider @Ĥ.qx bases its halting decision on simulating its input,
and it has (Ĥ, Ĥ) as its input that:
Ĥ.q0 would copy its input and then Ĥ.qx would simulate its input with
this copy then
Ĥ.q0 would copy its input and then Ĥ.qx would simulate its input with
this copy then
Ĥ.q0 would copy its input and then Ĥ.qx would simulate its input with
this copy...
unless and until the halt decider @Ĥ.qx stops simulating its input.

Linz, Peter 1990. An Introduction to Formal Languages and Automata.
Lexington/Toronto: D. C. Heath and Company.

--
Copyright 2021 Pete Olcott

"Great spirits have always encountered violent opposition from mediocre
minds." Einstein

Re: Infinitely Recursive input on HP Proofs

<HojoI.604824$%W6.542760@fx44.iad>

  copy mid

https://www.novabbs.com/devel/article-flat.php?id=15611&group=comp.theory#15611

  copy link   Newsgroups: comp.theory
Path: i2pn2.org!i2pn.org!aioe.org!news.uzoreto.com!fdcspool6.netnews.com!news-out.netnews.com!news.alt.net!fdc3.netnews.com!peer03.ams1!peer.ams1.xlned.com!news.xlned.com!peer01.iad!feed-me.highwinds-media.com!news.highwinds-media.com!fx44.iad.POSTED!not-for-mail
Subject: Re: Infinitely Recursive input on HP Proofs
Newsgroups: comp.theory
References: <918df253-d4f0-4370-8f73-88e6690380a1@googlegroups.com>
<a4ydnWkMIKhS8Dz9nZ2dnUU7-L3NnZ2d@giganews.com> <87im3i5t12.fsf@bsb.me.uk>
<0sCdnWsgz4JPGjz9nZ2dnUU7-RvNnZ2d@giganews.com>
<R%foI.542844$nn2.335922@fx48.iad>
<-rednavQTY_BDTz9nZ2dnUU7-SXNnZ2d@giganews.com>
<_yhoI.542847$nn2.449398@fx48.iad>
<EsCdnduL051HNTz9nZ2dnUU7-d_NnZ2d@giganews.com>
From: Rich...@Damon-Family.org (Richard Damon)
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:78.0)
Gecko/20100101 Thunderbird/78.10.1
MIME-Version: 1.0
In-Reply-To: <EsCdnduL051HNTz9nZ2dnUU7-d_NnZ2d@giganews.com>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Lines: 61
Message-ID: <HojoI.604824$%W6.542760@fx44.iad>
X-Complaints-To: abuse@easynews.com
Organization: Forte - www.forteinc.com
X-Complaints-Info: Please be sure to forward a copy of ALL headers otherwise we will be unable to process your complaint properly.
Date: Sun, 16 May 2021 21:11:03 -0400
X-Received-Bytes: 3763
 by: Richard Damon - Mon, 17 May 2021 01:11 UTC

On 5/16/21 7:21 PM, olcott wrote:
> On 5/16/2021 6:05 PM, Richard Damon wrote:

>>
>> But you can't use a 'Falsism' to change the facts about the definition.
>>
>> And, as I have said, there IS no pathological self-reference in the
>> problem.
>>
>> YOU create the self-reference by not implementing the required copy
>> operation. In actuality the Linz proof has no real self-reference, just
>> two copies of what just happens to be the same thing.
>>
>
> I am referring to the complete Peter Linz version where a copy <is> made.
>
> Ĥ.q0  wM  ⊢*  Ĥ.qx  wM  wM  ⊢*  Ĥ.qy  ∞
> Ĥ.q0  wM  ⊢*  Ĥ.qx  wM  wM  ⊢*  Ĥ.qn
>
> The above is adapted from (Linz:1990:319).
> It shows that Turing machine Ĥ copies its input at (q0) and begins
> executing an embedded copy of the original halt decider with this input
> at (qx).
>
> The (qy) state indicates that the halt decider decides that its input
> would halt. The ((qn)) state indicates the input would not halt. The
> appended (qa) and (qb) states cause Ĥ to infinitely loop if the halt
> decider decides that its input would halt.
>
> It can be understood from the above specification that when the embedded
> halt decider @Ĥ.qx bases its halting decision on simulating its input,
> and it has (Ĥ,  Ĥ) as its input that:
> Ĥ.q0 would copy its input and then Ĥ.qx would simulate its input with
> this copy then
> Ĥ.q0 would copy its input and then Ĥ.qx would simulate its input with
> this copy then
> Ĥ.q0 would copy its input and then Ĥ.qx would simulate its input with
> this copy...
> unless and until the halt decider @Ĥ.qx stops simulating its input.
>
> Linz, Peter 1990. An Introduction to Formal Languages and Automata.
> Lexington/Toronto: D. C. Heath and Company.
>
>
>
Key point to notice is that Linz's description doesn't have ANY
self-reference, or even things done via a 'reference'

EVERYTHING is done with a copy, and there is no references to be self.

H^ has its own copy of the algorithm of H in it, it doesn't 'reference'
H, so this is NOT a self-reference.

The input to H^ doesn't 'reference' H^, it is built on the description of H^

With no references, you can't have self-reference.

The only self-references in your 'proof' are the one YOU create by not
making the 'required' copies. This also makes it so things are likely
not actually the Equivalents of the required Turing Machines. Another
flaw in your proof.

Re: Infinitely Recursive input on HP Proofs

<s7sg34$94t$1@dont-email.me>

  copy mid

https://www.novabbs.com/devel/article-flat.php?id=15612&group=comp.theory#15612

  copy link   Newsgroups: comp.theory
Path: i2pn2.org!i2pn.org!eternal-september.org!reader02.eternal-september.org!.POSTED!not-for-mail
From: agis...@gm.invalid (André G. Isaak)
Newsgroups: comp.theory
Subject: Re: Infinitely Recursive input on HP Proofs
Date: Sun, 16 May 2021 19:15:16 -0600
Organization: Christians and Atheists United Against Creeping Agnosticism
Lines: 147
Message-ID: <s7sg34$94t$1@dont-email.me>
References: <918df253-d4f0-4370-8f73-88e6690380a1@googlegroups.com>
<a4ydnWkMIKhS8Dz9nZ2dnUU7-L3NnZ2d@giganews.com> <87im3i5t12.fsf@bsb.me.uk>
<0sCdnWsgz4JPGjz9nZ2dnUU7-RvNnZ2d@giganews.com>
<R%foI.542844$nn2.335922@fx48.iad>
<-rednavQTY_BDTz9nZ2dnUU7-SXNnZ2d@giganews.com>
<_yhoI.542847$nn2.449398@fx48.iad>
<EsCdnduL051HNTz9nZ2dnUU7-d_NnZ2d@giganews.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Injection-Date: Mon, 17 May 2021 01:15:17 -0000 (UTC)
Injection-Info: reader02.eternal-september.org; posting-host="ec8282cd21476f1c933a3f9612da5f05";
logging-data="9373"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1/d6ECzgtRljbJ4LPdY8beg"
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:68.0)
Gecko/20100101 Thunderbird/68.12.1
Cancel-Lock: sha1:we4ZWwKbPe8bPfBLEBApQQkx7oM=
In-Reply-To: <EsCdnduL051HNTz9nZ2dnUU7-d_NnZ2d@giganews.com>
Content-Language: en-US
 by: André G. Isaak - Mon, 17 May 2021 01:15 UTC

On 2021-05-16 17:21, olcott wrote:
> On 5/16/2021 6:05 PM, Richard Damon wrote:
>> On 5/16/21 5:37 PM, olcott wrote:
>>> On 5/16/2021 4:19 PM, Richard Damon wrote:
>>>> On 5/16/21 5:00 PM, olcott wrote:
>>>>> On 5/16/2021 3:21 PM, Ben Bacarisse wrote:
>>>>>> olcott <NoOne@NoWhere.com> writes:
>>>>>>
>>>>>>> Any genius knowing the theory of computation quite well can easily
>>>>>>> confirm that Ĥ(Ĥ) specifies the non halting behavior pattern of
>>>>>>> [infinitely_nested_simulation] to every simulating halt decider.
>>>>>>> This equally applies to all of the halting problem instances.
>>>>>>>
>>>>>>> Ĥ(Ĥ) is short-hand for:
>>>>>>> Now Ĥ is a Turing machine, so that it will have some description in
>>>>>>> Σ*,
>>>>>>> say ŵ. This string, in addition to being the description of Ĥ can
>>>>>>> also be used
>>>>>>> as input string. We can therefore legitimately ask what would happen
>>>>>>> if Ĥ is
>>>>>>> applied to ŵ. (Linz:1990:320)
>>>>>>>
>>>>>>> Linz, Peter 1990. An Introduction to Formal Languages and
>>>>>>> Automata. Lexington/Toronto: D. C. Heath and Company. (315-320)
>>>>>>
>>>>>> Nonsense.  H is the name given in Linz to a non-existent Turing
>>>>>> machine.  H^, derived from it, also does not exit.  Anyone who has
>>>>>> read
>>>>>> that book should know that H^([H^]) specifies no behaviour at all.
>>>>>>
>>>>>> You have constructed a poor-man's partial decider that gets the "hat"
>>>>>> case wrong, but you can't justify the wrong answer by appeal Linz.
>>>>>>
>>>>>> Your "infinitely nested simulation" explanation for your decider
>>>>>> giving
>>>>>> the wrong answer can be put on a more formal basis, but you can't
>>>>>> do by
>>>>>> re-using the names of nonexistent TM's from Linz.
>>>>>>
>>>>>
>>>>> Well I won't say that you are not a genius or that you don't know the
>>>>> theory of computation very well.
>>>>>
>>>>> The actual Ĥ(<Ĥ>) does specify [infinitely_nested_simulation] to every
>>>>> simulating halt decider. This [infinitely_nested_simulation] is more
>>>>> complex than the one that Halts recognizes.
>>>>>
>>>>> Ĥ.q0  wM  ⊢*  Ĥ.qx  wM  wM  ⊢*  Ĥ.qy  ∞
>>>>> Ĥ.q0  wM  ⊢*  Ĥ.qx  wM  wM  ⊢*  Ĥ.qn
>>>>>
>>>>> The above is adapted from (Linz:1990:319).
>>>>> It shows that Turing machine Ĥ copies its input at (q0) and begins
>>>>> executing an embedded copy of the original halt decider with this
>>>>> input
>>>>> at (qx).
>>>>>
>>>>> The (qy) state indicates that the halt decider decides that its input
>>>>> would halt. The ((qn)) state indicates the input would not halt. The
>>>>> appended (qa) and (qb) states cause Ĥ to infinitely loop if the halt
>>>>> decider decides that its input would halt.
>>>>>
>>>>> It can be understood from the above specification that when the
>>>>> embedded
>>>>> halt decider @Ĥ.qx bases its halting decision on simulating its input,
>>>>> and it has (Ĥ,  Ĥ) as its input that:
>>>>> Ĥ.q0 would copy its input and then Ĥ.qx would simulate its input with
>>>>> this copy then
>>>>> Ĥ.q0 would copy its input and then Ĥ.qx would simulate its input with
>>>>> this copy then
>>>>> Ĥ.q0 would copy its input and then Ĥ.qx would simulate its input with
>>>>> this copy...
>>>>> unless and until the halt decider @Ĥ.qx stops simulating its input.
>>>>
>>>> BUT, since H is required to be finite in execution, the copy of H
>>>> within
>>>> H^ must have some alteration from a simple simulator to break the loop.
>>>>
>>>> If it does, then it WILL break the loop, and be finite in execution.
>>>>
>>>> If it doesn't then H(H^,H^) won't break the loop, and thus will not
>>>> answer in finite time and thus fail to give an answer and not be a
>>>> decider.
>>>>
>>>
>>> That is why we need this truism to dislodge the pathological
>>> self-reference:
>>>
>>> On 5/11/2021 11:10 AM, Ben Bacarisse wrote:
>>>> olcott <NoOne@NoWhere.com> writes:
>>>>
>>>>> Truism:
>>>>> Every simulation that would never stop unless Halts() stops
>>>>> it at some point specifies infinite execution.
>>>>
>>>> Any algorithm that implements this truism is, of course, a halting
>>>> decider.
>>>
>>> Whether a computation is finite is more nuanced than it simply stops
>>> running otherwise an infinite loop that had its simulation aborted
>>> because its behavior matched the [infinite_loop] non-halting behavior
>>> pattern would have to be classified as a halting computation.
>>>
>>> Unless the simulating halt decider stops simulating Ĥ(Ĥ) at some point
>>> its simulation would be infinite ∴ meets the non-halting truism.
>>>
>>
>> But you can't use a 'Falsism' to change the facts about the definition.
>>
>> And, as I have said, there IS no pathological self-reference in the
>> problem.
>>
>> YOU create the self-reference by not implementing the required copy
>> operation. In actuality the Linz proof has no real self-reference, just
>> two copies of what just happens to be the same thing.
>>
>
> I am referring to the complete Peter Linz version where a copy <is> made.
>
> Ĥ.q0  wM  ⊢*  Ĥ.qx  wM  wM  ⊢*  Ĥ.qy  ∞
> Ĥ.q0  wM  ⊢*  Ĥ.qx  wM  wM  ⊢*  Ĥ.qn
>
> The above is adapted from (Linz:1990:319).
> It shows that Turing machine Ĥ copies its input at (q0) and begins
> executing an embedded copy of the original halt decider with this input
> at (qx).
>
> The (qy) state indicates that the halt decider decides that its input
> would halt. The ((qn)) state indicates the input would not halt. The
> appended (qa) and (qb) states cause Ĥ to infinitely loop if the halt
> decider decides that its input would halt.
>
> It can be understood from the above specification that when the embedded
> halt decider @Ĥ.qx bases its halting decision on simulating its input,
> and it has (Ĥ,  Ĥ) as its input that:

But Linz's specification doesn't make any mention of simulating the
input, so there isn't anything intrinsincally recursive about Linz's
specification. It's only *your* decision to employ simulation which
leads to potentially infinite recursion.

The actual specification involves no self-reference or recursion.

André

--
To email remove 'invalid' & replace 'gm' with well known Google mail
service.

Re: Infinitely Recursive input on HP Proofs

<87bl9a40nr.fsf@bsb.me.uk>

  copy mid

https://www.novabbs.com/devel/article-flat.php?id=15614&group=comp.theory#15614

  copy link   Newsgroups: comp.theory
Path: i2pn2.org!i2pn.org!eternal-september.org!reader02.eternal-september.org!.POSTED!not-for-mail
From: ben.use...@bsb.me.uk (Ben Bacarisse)
Newsgroups: comp.theory
Subject: Re: Infinitely Recursive input on HP Proofs
Date: Mon, 17 May 2021 02:19:35 +0100
Organization: A noiseless patient Spider
Lines: 106
Message-ID: <87bl9a40nr.fsf@bsb.me.uk>
References: <918df253-d4f0-4370-8f73-88e6690380a1@googlegroups.com>
<a4ydnWkMIKhS8Dz9nZ2dnUU7-L3NnZ2d@giganews.com>
<87im3i5t12.fsf@bsb.me.uk>
<0sCdnWsgz4JPGjz9nZ2dnUU7-RvNnZ2d@giganews.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
Injection-Info: reader02.eternal-september.org; posting-host="342c78f756b73b7a65cfaf9b40e676c4";
logging-data="20508"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX19q4ELrinUZP44ckmjSqFXATQgJYuMW7ls="
Cancel-Lock: sha1:uwpf+ADEtYHReotcOmtBZWyh300=
sha1:c8XFEtsrg9rZ9LcPgnbLvYOy6yM=
X-BSB-Auth: 1.4e9e10e81d4a555b611b.20210517021936BST.87bl9a40nr.fsf@bsb.me.uk
 by: Ben Bacarisse - Mon, 17 May 2021 01:19 UTC

olcott <NoOne@NoWhere.com> writes:

> On 5/16/2021 3:21 PM, Ben Bacarisse wrote:
>> olcott <NoOne@NoWhere.com> writes:
>>
>>> Any genius knowing the theory of computation quite well can easily
>>> confirm that Ĥ(Ĥ) specifies the non halting behavior pattern of
>>> [infinitely_nested_simulation] to every simulating halt decider.
>>> This equally applies to all of the halting problem instances.
>>>
>>> Ĥ(Ĥ) is short-hand for:
>>> Now Ĥ is a Turing machine, so that it will have some description in Σ*,
>>> say ŵ. This string, in addition to being the description of Ĥ can also be used
>>> as input string. We can therefore legitimately ask what would happen if Ĥ is
>>> applied to ŵ. (Linz:1990:320)
>>>
>>> Linz, Peter 1990. An Introduction to Formal Languages and
>>> Automata. Lexington/Toronto: D. C. Heath and Company. (315-320)
>>
>> Nonsense. H is the name given in Linz to a non-existent Turing
>> machine. H^, derived from it, also does not exit. Anyone who has read
>> that book should know that H^([H^]) specifies no behaviour at all.
>>
>> You have constructed a poor-man's partial decider that gets the "hat"
>> case wrong, but you can't justify the wrong answer by appeal Linz.
>>
>> Your "infinitely nested simulation" explanation for your decider giving
>> the wrong answer can be put on a more formal basis, but you can't do by
>> re-using the names of nonexistent TM's from Linz.
>>
>
> Well I won't say that you are not a genius or that you don't know the
> theory of computation very well.
>
> The actual Ĥ(<Ĥ>) does specify [infinitely_nested_simulation] to every
> simulating halt decider. This [infinitely_nested_simulation] is more
> complex than the one that Halts recognizes.

No. H and H^ specify no behaviour. These lines:

> Ĥ.q0 wM ⊢* Ĥ.qx wM wM ⊢* Ĥ.qy ∞
> Ĥ.q0 wM ⊢* Ĥ.qx wM wM ⊢* Ĥ.qn

(with the text below) specify the behaviour of no Turing machine.

> The above is adapted from (Linz:1990:319).
> It shows that Turing machine Ĥ copies its input at (q0) and begins
> executing an embedded copy of the original halt decider with this
> input at (qx).
>
> The (qy) state indicates that the halt decider decides that its input
> would halt. The ((qn)) state indicates the input would not halt. The
> appended (qa) and (qb) states cause Ĥ to infinitely loop if the halt
> decider decides that its input would halt.

The above is Linz (except for the altered specification). But this is
all yours:

> It can be understood from the above specification that when the embedded halt decider @Ĥ.qx bases its halting decision on simulating its input, and it has (Ĥ, Ĥ) as its input that:
> Ĥ.q0 would copy its input and then Ĥ.qx would simulate its input with this copy then
> Ĥ.q0 would copy its input and then Ĥ.qx would simulate its input with this copy then
> Ĥ.q0 would copy its input and then Ĥ.qx would simulate its input with this copy...
> unless and until the halt decider @Ĥ.qx stops simulating its input.
>
> Linz, Peter 1990. An Introduction to Formal Languages and
> Automata. Lexington/Toronto: D. C. Heath and Company.

You should not attribute your junk to Linz. Linz of course does not
limit how a decider might be written because he wants to make general
claims, not specific ones.

And you want to pretend that the finite nested simulations you show can
be called infinitely nested simulation and no one will notice! Sorry, I
noticed the last time, and I'm pointing it out again.

> So it seems to be the same as it was more than four years ago you are
> so biased against either me or my position (or both) that you simply
> won't pay enough attention to see that I am right.
>
> The key evidence that I am right and you just don't see it is the lack
> of any correct rebuttal.

Talk junk and I'll correct it -- stop talking junk and I won't have
anything to correct. Stop saying that a nonexistent TM specifies any
behaviour at all. Stop saying that Linz's H shows nested simulation
when it's your badly conceived decider uses simulation. Stop saying
that explicitly finite nested simulation is infinite nested simulation.
Stop saying that whether a computation is finite is more nuanced than it
simply stops running. Stop saying that the fact that a computation
halts does not entail that it is a halting computation. Stop pretending
that your silly-not-halting problem is the halting problem. We are up
to our necks in garbage now.

> That the actual Ĥ(<Ĥ>) does specify [infinitely_nested_simulation] to
> every simulating halt decider can't be refuted simply because <it is>
> the case.

The nonexistent H^ based on the nonexistent H that does not necessarily
simulate anything but which you show performing explicitly finite nested
simulation? That's the "actual" H^(H^) you claim specifies infinite
nested simulation?

You have lost touch with reality.

--
Ben.

Re: Infinitely Recursive input on HP Proofs

<it-dnVe8wa5OWjz9nZ2dnUU7-emdnZ2d@giganews.com>

  copy mid

https://www.novabbs.com/devel/article-flat.php?id=15617&group=comp.theory#15617

  copy link   Newsgroups: comp.theory
Path: i2pn2.org!i2pn.org!aioe.org!feeder1.feed.usenet.farm!feed.usenet.farm!tr1.eu1.usenetexpress.com!feeder.usenetexpress.com!tr3.iad1.usenetexpress.com!border1.nntp.dca1.giganews.com!nntp.giganews.com!buffer1.nntp.dca1.giganews.com!news.giganews.com.POSTED!not-for-mail
NNTP-Posting-Date: Sun, 16 May 2021 20:33:07 -0500
Subject: Re: Infinitely Recursive input on HP Proofs
Newsgroups: comp.theory
References: <918df253-d4f0-4370-8f73-88e6690380a1@googlegroups.com> <a4ydnWkMIKhS8Dz9nZ2dnUU7-L3NnZ2d@giganews.com> <87im3i5t12.fsf@bsb.me.uk> <0sCdnWsgz4JPGjz9nZ2dnUU7-RvNnZ2d@giganews.com> <R%foI.542844$nn2.335922@fx48.iad> <-rednavQTY_BDTz9nZ2dnUU7-SXNnZ2d@giganews.com> <_yhoI.542847$nn2.449398@fx48.iad> <EsCdnduL051HNTz9nZ2dnUU7-d_NnZ2d@giganews.com> <s7sg34$94t$1@dont-email.me>
From: NoO...@NoWhere.com (olcott)
Date: Sun, 16 May 2021 20:34:03 -0500
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.10.1
MIME-Version: 1.0
In-Reply-To: <s7sg34$94t$1@dont-email.me>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Message-ID: <it-dnVe8wa5OWjz9nZ2dnUU7-emdnZ2d@giganews.com>
Lines: 170
X-Usenet-Provider: http://www.giganews.com
X-Trace: sv3-nRhW/wARYHntznCpqQsE4xB9/IZ31+teblYnSigz3CQN5tk34SLCHqlLPZWLgsKqwqxc5IQr4/yM00+!tAEggL4dsQ4GFSzdhfz7yoMIkTg0j33yHdCiga6NXOF2RoMgf4fOz7dUx9Rjc856uCcL4W/CPwQk!fg==
X-Complaints-To: abuse@giganews.com
X-DMCA-Notifications: http://www.giganews.com/info/dmca.html
X-Abuse-and-DMCA-Info: Please be sure to forward a copy of ALL headers
X-Abuse-and-DMCA-Info: Otherwise we will be unable to process your complaint properly
X-Postfilter: 1.3.40
X-Original-Bytes: 8597
 by: olcott - Mon, 17 May 2021 01:34 UTC

On 5/16/2021 8:15 PM, André G. Isaak wrote:
> On 2021-05-16 17:21, olcott wrote:
>> On 5/16/2021 6:05 PM, Richard Damon wrote:
>>> On 5/16/21 5:37 PM, olcott wrote:
>>>> On 5/16/2021 4:19 PM, Richard Damon wrote:
>>>>> On 5/16/21 5:00 PM, olcott wrote:
>>>>>> On 5/16/2021 3:21 PM, Ben Bacarisse wrote:
>>>>>>> olcott <NoOne@NoWhere.com> writes:
>>>>>>>
>>>>>>>> Any genius knowing the theory of computation quite well can easily
>>>>>>>> confirm that Ĥ(Ĥ) specifies the non halting behavior pattern of
>>>>>>>> [infinitely_nested_simulation] to every simulating halt decider.
>>>>>>>> This equally applies to all of the halting problem instances.
>>>>>>>>
>>>>>>>> Ĥ(Ĥ) is short-hand for:
>>>>>>>> Now Ĥ is a Turing machine, so that it will have some description in
>>>>>>>> Σ*,
>>>>>>>> say ŵ. This string, in addition to being the description of Ĥ can
>>>>>>>> also be used
>>>>>>>> as input string. We can therefore legitimately ask what would
>>>>>>>> happen
>>>>>>>> if Ĥ is
>>>>>>>> applied to ŵ. (Linz:1990:320)
>>>>>>>>
>>>>>>>> Linz, Peter 1990. An Introduction to Formal Languages and
>>>>>>>> Automata. Lexington/Toronto: D. C. Heath and Company. (315-320)
>>>>>>>
>>>>>>> Nonsense.  H is the name given in Linz to a non-existent Turing
>>>>>>> machine.  H^, derived from it, also does not exit.  Anyone who
>>>>>>> has read
>>>>>>> that book should know that H^([H^]) specifies no behaviour at all.
>>>>>>>
>>>>>>> You have constructed a poor-man's partial decider that gets the
>>>>>>> "hat"
>>>>>>> case wrong, but you can't justify the wrong answer by appeal Linz.
>>>>>>>
>>>>>>> Your "infinitely nested simulation" explanation for your decider
>>>>>>> giving
>>>>>>> the wrong answer can be put on a more formal basis, but you can't
>>>>>>> do by
>>>>>>> re-using the names of nonexistent TM's from Linz.
>>>>>>>
>>>>>>
>>>>>> Well I won't say that you are not a genius or that you don't know the
>>>>>> theory of computation very well.
>>>>>>
>>>>>> The actual Ĥ(<Ĥ>) does specify [infinitely_nested_simulation] to
>>>>>> every
>>>>>> simulating halt decider. This [infinitely_nested_simulation] is more
>>>>>> complex than the one that Halts recognizes.
>>>>>>
>>>>>> Ĥ.q0  wM  ⊢*  Ĥ.qx  wM  wM  ⊢*  Ĥ.qy  ∞
>>>>>> Ĥ.q0  wM  ⊢*  Ĥ.qx  wM  wM  ⊢*  Ĥ.qn
>>>>>>
>>>>>> The above is adapted from (Linz:1990:319).
>>>>>> It shows that Turing machine Ĥ copies its input at (q0) and begins
>>>>>> executing an embedded copy of the original halt decider with this
>>>>>> input
>>>>>> at (qx).
>>>>>>
>>>>>> The (qy) state indicates that the halt decider decides that its input
>>>>>> would halt. The ((qn)) state indicates the input would not halt. The
>>>>>> appended (qa) and (qb) states cause Ĥ to infinitely loop if the halt
>>>>>> decider decides that its input would halt.
>>>>>>
>>>>>> It can be understood from the above specification that when the
>>>>>> embedded
>>>>>> halt decider @Ĥ.qx bases its halting decision on simulating its
>>>>>> input,
>>>>>> and it has (Ĥ,  Ĥ) as its input that:
>>>>>> Ĥ.q0 would copy its input and then Ĥ.qx would simulate its input with
>>>>>> this copy then
>>>>>> Ĥ.q0 would copy its input and then Ĥ.qx would simulate its input with
>>>>>> this copy then
>>>>>> Ĥ.q0 would copy its input and then Ĥ.qx would simulate its input with
>>>>>> this copy...
>>>>>> unless and until the halt decider @Ĥ.qx stops simulating its input.
>>>>>
>>>>> BUT, since H is required to be finite in execution, the copy of H
>>>>> within
>>>>> H^ must have some alteration from a simple simulator to break the
>>>>> loop.
>>>>>
>>>>> If it does, then it WILL break the loop, and be finite in execution.
>>>>>
>>>>> If it doesn't then H(H^,H^) won't break the loop, and thus will not
>>>>> answer in finite time and thus fail to give an answer and not be a
>>>>> decider.
>>>>>
>>>>
>>>> That is why we need this truism to dislodge the pathological
>>>> self-reference:
>>>>
>>>> On 5/11/2021 11:10 AM, Ben Bacarisse wrote:
>>>>> olcott <NoOne@NoWhere.com> writes:
>>>>>
>>>>>> Truism:
>>>>>> Every simulation that would never stop unless Halts() stops
>>>>>> it at some point specifies infinite execution.
>>>>>
>>>>> Any algorithm that implements this truism is, of course, a halting
>>>>> decider.
>>>>
>>>> Whether a computation is finite is more nuanced than it simply stops
>>>> running otherwise an infinite loop that had its simulation aborted
>>>> because its behavior matched the [infinite_loop] non-halting behavior
>>>> pattern would have to be classified as a halting computation.
>>>>
>>>> Unless the simulating halt decider stops simulating Ĥ(Ĥ) at some point
>>>> its simulation would be infinite ∴ meets the non-halting truism.
>>>>
>>>
>>> But you can't use a 'Falsism' to change the facts about the definition.
>>>
>>> And, as I have said, there IS no pathological self-reference in the
>>> problem.
>>>
>>> YOU create the self-reference by not implementing the required copy
>>> operation. In actuality the Linz proof has no real self-reference, just
>>> two copies of what just happens to be the same thing.
>>>
>>
>> I am referring to the complete Peter Linz version where a copy <is> made.
>>
>> Ĥ.q0  wM  ⊢*  Ĥ.qx  wM  wM  ⊢*  Ĥ.qy  ∞
>> Ĥ.q0  wM  ⊢*  Ĥ.qx  wM  wM  ⊢*  Ĥ.qn
>>
>> The above is adapted from (Linz:1990:319).
>> It shows that Turing machine Ĥ copies its input at (q0) and begins
>> executing an embedded copy of the original halt decider with this
>> input at (qx).
>>
>> The (qy) state indicates that the halt decider decides that its input
>> would halt. The ((qn)) state indicates the input would not halt. The
>> appended (qa) and (qb) states cause Ĥ to infinitely loop if the halt
>> decider decides that its input would halt.
>>
>> It can be understood from the above specification that when the
>> embedded halt decider @Ĥ.qx bases its halting decision on simulating
>> its input, and it has (Ĥ,  Ĥ) as its input that:
>
> But Linz's specification doesn't make any mention of simulating the
> input, so there isn't anything intrinsincally recursive about Linz's
> specification. It's only *your* decision to employ simulation which
> leads to potentially infinite recursion.
>
> The actual specification involves no self-reference or recursion.
>
> André
>

Simulating halt decider H correctly decides non-halting on its input
(Ĥ,Ĥ) on the basis of this truism:

On 5/11/2021 11:10 AM, Ben Bacarisse wrote:
> olcott <NoOne@NoWhere.com> writes:
>
>> Truism:
>> Every simulation that would never stop unless Halts() stops
>> it at some point specifies infinite execution.
>
> Any algorithm that implements this truism is, of course, a halting
> decider.

--
Copyright 2021 Pete Olcott

"Great spirits have always encountered violent opposition from mediocre
minds." Einstein


Click here to read the complete article
Re: Infinitely Recursive input on HP Proofs (Full Linz text)

<KKidnYZUNMQlUTz9nZ2dnUU7-f_NnZ2d@giganews.com>

  copy mid

https://www.novabbs.com/devel/article-flat.php?id=15618&group=comp.theory#15618

  copy link   Newsgroups: comp.theory
Path: i2pn2.org!i2pn.org!weretis.net!feeder6.news.weretis.net!news.snarked.org!border2.nntp.dca1.giganews.com!nntp.giganews.com!buffer2.nntp.dca1.giganews.com!buffer1.nntp.dca1.giganews.com!news.giganews.com.POSTED!not-for-mail
NNTP-Posting-Date: Sun, 16 May 2021 20:54:00 -0500
Subject: Re: Infinitely Recursive input on HP Proofs (Full Linz text)
Newsgroups: comp.theory
References: <918df253-d4f0-4370-8f73-88e6690380a1@googlegroups.com>
<a4ydnWkMIKhS8Dz9nZ2dnUU7-L3NnZ2d@giganews.com> <87im3i5t12.fsf@bsb.me.uk>
<0sCdnWsgz4JPGjz9nZ2dnUU7-RvNnZ2d@giganews.com> <87bl9a40nr.fsf@bsb.me.uk>
From: NoO...@NoWhere.com (olcott)
Date: Sun, 16 May 2021 20:54:55 -0500
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101
Thunderbird/78.10.1
MIME-Version: 1.0
In-Reply-To: <87bl9a40nr.fsf@bsb.me.uk>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Message-ID: <KKidnYZUNMQlUTz9nZ2dnUU7-f_NnZ2d@giganews.com>
Lines: 112
X-Usenet-Provider: http://www.giganews.com
X-Trace: sv3-a7X72mU1JyBO3YZXYC99UwOQCF0IJAeEQshj3ulejicouSVm1Z8Z26PXhBFE90j5g2kTZ33Ls5gyErz!TfOYB1tmOgjA5ak2dCOxuohSjRvErJYay2cgqBOCqAtwFAdpwInWRLmR9kJWo8JOi47a60G6fVCI!SA==
X-Complaints-To: abuse@giganews.com
X-DMCA-Notifications: http://www.giganews.com/info/dmca.html
X-Abuse-and-DMCA-Info: Please be sure to forward a copy of ALL headers
X-Abuse-and-DMCA-Info: Otherwise we will be unable to process your complaint properly
X-Postfilter: 1.3.40
X-Original-Bytes: 6520
 by: olcott - Mon, 17 May 2021 01:54 UTC

On 5/16/2021 8:19 PM, Ben Bacarisse wrote:
> olcott <NoOne@NoWhere.com> writes:
>
>> On 5/16/2021 3:21 PM, Ben Bacarisse wrote:
>>> olcott <NoOne@NoWhere.com> writes:
>>>
>>>> Any genius knowing the theory of computation quite well can easily
>>>> confirm that Ĥ(Ĥ) specifies the non halting behavior pattern of
>>>> [infinitely_nested_simulation] to every simulating halt decider.
>>>> This equally applies to all of the halting problem instances.
>>>>
>>>> Ĥ(Ĥ) is short-hand for:
>>>> Now Ĥ is a Turing machine, so that it will have some description in Σ*,
>>>> say ŵ. This string, in addition to being the description of Ĥ can also be used
>>>> as input string. We can therefore legitimately ask what would happen if Ĥ is
>>>> applied to ŵ. (Linz:1990:320)
>>>>
>>>> Linz, Peter 1990. An Introduction to Formal Languages and
>>>> Automata. Lexington/Toronto: D. C. Heath and Company. (315-320)
>>>
>>> Nonsense. H is the name given in Linz to a non-existent Turing
>>> machine. H^, derived from it, also does not exit. Anyone who has read
>>> that book should know that H^([H^]) specifies no behaviour at all.
>>>
>>> You have constructed a poor-man's partial decider that gets the "hat"
>>> case wrong, but you can't justify the wrong answer by appeal Linz.
>>>
>>> Your "infinitely nested simulation" explanation for your decider giving
>>> the wrong answer can be put on a more formal basis, but you can't do by
>>> re-using the names of nonexistent TM's from Linz.
>>>
>>
>> Well I won't say that you are not a genius or that you don't know the
>> theory of computation very well.
>>
>> The actual Ĥ(<Ĥ>) does specify [infinitely_nested_simulation] to every
>> simulating halt decider. This [infinitely_nested_simulation] is more
>> complex than the one that Halts recognizes.
>
> No. H and H^ specify no behaviour. These lines:
>
>> Ĥ.q0 wM ⊢* Ĥ.qx wM wM ⊢* Ĥ.qy ∞
>> Ĥ.q0 wM ⊢* Ĥ.qx wM wM ⊢* Ĥ.qn
>
> (with the text below) specify the behaviour of no Turing machine.
>
>> The above is adapted from (Linz:1990:319).
>> It shows that Turing machine Ĥ copies its input at (q0) and begins
>> executing an embedded copy of the original halt decider with this
>> input at (qx).
>>
>> The (qy) state indicates that the halt decider decides that its input
>> would halt. The ((qn)) state indicates the input would not halt. The
>> appended (qa) and (qb) states cause Ĥ to infinitely loop if the halt
>> decider decides that its input would halt.
>
> The above is Linz (except for the altered specification). But this is
> all yours:
>
>> It can be understood from the above specification that when the embedded halt decider @Ĥ.qx bases its halting decision on simulating its input, and it has (Ĥ, Ĥ) as its input that:
>> Ĥ.q0 would copy its input and then Ĥ.qx would simulate its input with this copy then
>> Ĥ.q0 would copy its input and then Ĥ.qx would simulate its input with this copy then
>> Ĥ.q0 would copy its input and then Ĥ.qx would simulate its input with this copy...
>> unless and until the halt decider @Ĥ.qx stops simulating its input.

In other words you are saying that the following Linz text would not
specify the above behavior to a simulating halt decider H?

Proof: We assume the contrary, namely that there exists an algorithm,
and consequently some Turing machine H, that solves the halting problem.
The input to H will be the description (encoded in some form) of M, say
wM, as well as the input w. The requirement is then that, given any (wM, w),
the Turing machine H will halt with either a yes or no answer. We achieve
this by asking that H halt in one of two corresponding final states,
say, qy or
qn. The situation can be visualized by a block diagram like Figure 12.1. The
intent of this diagram is to indicate that, if M is started in state q0
with input
(wM, w), it will eventually halt in state qy or qn. As required by
Definition
12.1, we want H to operate according to the following rules:

H.qx wM wM ⊢* H.qy
if M applied to w halts, and

H.qx wM wM ⊢* H.qn
if M applied to w does not halt

Next, we modify H to produce a Turing machine H' with the structure
shown in Figure 12.2. With the added states in Figure 12.2 we want to
convey that the transitions between state qy and the new states qa and
qb are
to be made, regardless of the tape symbol, in such a way that the tape
remains unchanged. The way this is done is straightforward. Comparing H
and H' we see that, in situations where H reaches qy and halts, the modified
machine H' will enter an infinite loop.

From H' we construct another Turing machine Ĥ. This new machine
takes as input wM, copies it, and then behaves exactly like H'. Then the
action of Ĥ is such that

Ĥ.q0 wM ⊢* Ĥ.qx wM wM ⊢* Ĥ.qy ∞
if M applied to wM halts, and

Ĥ.q0 wM ⊢* Ĥ.qx wM wM ⊢* Ĥ.qn
if M applied to wM does not halt

--
Copyright 2021 Pete Olcott

"Great spirits have always encountered violent opposition from mediocre
minds." Einstein

Re: Infinitely Recursive input on HP Proofs

<52koI.84709$qy1.16481@fx26.iad>

  copy mid

https://www.novabbs.com/devel/article-flat.php?id=15619&group=comp.theory#15619

  copy link   Newsgroups: comp.theory
Path: i2pn2.org!i2pn.org!aioe.org!feeder5.feed.usenet.farm!feeder1.feed.usenet.farm!feed.usenet.farm!peer02.ams4!peer.am4.highwinds-media.com!peer01.iad!feed-me.highwinds-media.com!news.highwinds-media.com!fx26.iad.POSTED!not-for-mail
Subject: Re: Infinitely Recursive input on HP Proofs
Newsgroups: comp.theory
References: <918df253-d4f0-4370-8f73-88e6690380a1@googlegroups.com>
<a4ydnWkMIKhS8Dz9nZ2dnUU7-L3NnZ2d@giganews.com> <87im3i5t12.fsf@bsb.me.uk>
<0sCdnWsgz4JPGjz9nZ2dnUU7-RvNnZ2d@giganews.com>
<R%foI.542844$nn2.335922@fx48.iad>
<-rednavQTY_BDTz9nZ2dnUU7-SXNnZ2d@giganews.com>
<_yhoI.542847$nn2.449398@fx48.iad>
<EsCdnduL051HNTz9nZ2dnUU7-d_NnZ2d@giganews.com> <s7sg34$94t$1@dont-email.me>
<it-dnVe8wa5OWjz9nZ2dnUU7-emdnZ2d@giganews.com>
From: Rich...@Damon-Family.org (Richard Damon)
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:78.0)
Gecko/20100101 Thunderbird/78.10.1
MIME-Version: 1.0
In-Reply-To: <it-dnVe8wa5OWjz9nZ2dnUU7-emdnZ2d@giganews.com>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Lines: 176
Message-ID: <52koI.84709$qy1.16481@fx26.iad>
X-Complaints-To: abuse@easynews.com
Organization: Forte - www.forteinc.com
X-Complaints-Info: Please be sure to forward a copy of ALL headers otherwise we will be unable to process your complaint properly.
Date: Sun, 16 May 2021 21:55:13 -0400
X-Received-Bytes: 8616
 by: Richard Damon - Mon, 17 May 2021 01:55 UTC

On 5/16/21 9:34 PM, olcott wrote:
> On 5/16/2021 8:15 PM, André G. Isaak wrote:
>> On 2021-05-16 17:21, olcott wrote:
>>> On 5/16/2021 6:05 PM, Richard Damon wrote:
>>>> On 5/16/21 5:37 PM, olcott wrote:
>>>>> On 5/16/2021 4:19 PM, Richard Damon wrote:
>>>>>> On 5/16/21 5:00 PM, olcott wrote:
>>>>>>> On 5/16/2021 3:21 PM, Ben Bacarisse wrote:
>>>>>>>> olcott <NoOne@NoWhere.com> writes:
>>>>>>>>
>>>>>>>>> Any genius knowing the theory of computation quite well can easily
>>>>>>>>> confirm that Ĥ(Ĥ) specifies the non halting behavior pattern of
>>>>>>>>> [infinitely_nested_simulation] to every simulating halt decider.
>>>>>>>>> This equally applies to all of the halting problem instances.
>>>>>>>>>
>>>>>>>>> Ĥ(Ĥ) is short-hand for:
>>>>>>>>> Now Ĥ is a Turing machine, so that it will have some
>>>>>>>>> description in
>>>>>>>>> Σ*,
>>>>>>>>> say ŵ. This string, in addition to being the description of Ĥ can
>>>>>>>>> also be used
>>>>>>>>> as input string. We can therefore legitimately ask what would
>>>>>>>>> happen
>>>>>>>>> if Ĥ is
>>>>>>>>> applied to ŵ. (Linz:1990:320)
>>>>>>>>>
>>>>>>>>> Linz, Peter 1990. An Introduction to Formal Languages and
>>>>>>>>> Automata. Lexington/Toronto: D. C. Heath and Company. (315-320)
>>>>>>>>
>>>>>>>> Nonsense.  H is the name given in Linz to a non-existent Turing
>>>>>>>> machine.  H^, derived from it, also does not exit.  Anyone who
>>>>>>>> has read
>>>>>>>> that book should know that H^([H^]) specifies no behaviour at all.
>>>>>>>>
>>>>>>>> You have constructed a poor-man's partial decider that gets the
>>>>>>>> "hat"
>>>>>>>> case wrong, but you can't justify the wrong answer by appeal Linz.
>>>>>>>>
>>>>>>>> Your "infinitely nested simulation" explanation for your decider
>>>>>>>> giving
>>>>>>>> the wrong answer can be put on a more formal basis, but you
>>>>>>>> can't do by
>>>>>>>> re-using the names of nonexistent TM's from Linz.
>>>>>>>>
>>>>>>>
>>>>>>> Well I won't say that you are not a genius or that you don't know
>>>>>>> the
>>>>>>> theory of computation very well.
>>>>>>>
>>>>>>> The actual Ĥ(<Ĥ>) does specify [infinitely_nested_simulation] to
>>>>>>> every
>>>>>>> simulating halt decider. This [infinitely_nested_simulation] is more
>>>>>>> complex than the one that Halts recognizes.
>>>>>>>
>>>>>>> Ĥ.q0  wM  ⊢*  Ĥ.qx  wM  wM  ⊢*  Ĥ.qy  ∞
>>>>>>> Ĥ.q0  wM  ⊢*  Ĥ.qx  wM  wM  ⊢*  Ĥ.qn
>>>>>>>
>>>>>>> The above is adapted from (Linz:1990:319).
>>>>>>> It shows that Turing machine Ĥ copies its input at (q0) and begins
>>>>>>> executing an embedded copy of the original halt decider with this
>>>>>>> input
>>>>>>> at (qx).
>>>>>>>
>>>>>>> The (qy) state indicates that the halt decider decides that its
>>>>>>> input
>>>>>>> would halt. The ((qn)) state indicates the input would not halt. The
>>>>>>> appended (qa) and (qb) states cause Ĥ to infinitely loop if the halt
>>>>>>> decider decides that its input would halt.
>>>>>>>
>>>>>>> It can be understood from the above specification that when the
>>>>>>> embedded
>>>>>>> halt decider @Ĥ.qx bases its halting decision on simulating its
>>>>>>> input,
>>>>>>> and it has (Ĥ,  Ĥ) as its input that:
>>>>>>> Ĥ.q0 would copy its input and then Ĥ.qx would simulate its input
>>>>>>> with
>>>>>>> this copy then
>>>>>>> Ĥ.q0 would copy its input and then Ĥ.qx would simulate its input
>>>>>>> with
>>>>>>> this copy then
>>>>>>> Ĥ.q0 would copy its input and then Ĥ.qx would simulate its input
>>>>>>> with
>>>>>>> this copy...
>>>>>>> unless and until the halt decider @Ĥ.qx stops simulating its input.
>>>>>>
>>>>>> BUT, since H is required to be finite in execution, the copy of H
>>>>>> within
>>>>>> H^ must have some alteration from a simple simulator to break the
>>>>>> loop.
>>>>>>
>>>>>> If it does, then it WILL break the loop, and be finite in execution.
>>>>>>
>>>>>> If it doesn't then H(H^,H^) won't break the loop, and thus will not
>>>>>> answer in finite time and thus fail to give an answer and not be a
>>>>>> decider.
>>>>>>
>>>>>
>>>>> That is why we need this truism to dislodge the pathological
>>>>> self-reference:
>>>>>
>>>>> On 5/11/2021 11:10 AM, Ben Bacarisse wrote:
>>>>>> olcott <NoOne@NoWhere.com> writes:
>>>>>>
>>>>>>> Truism:
>>>>>>> Every simulation that would never stop unless Halts() stops
>>>>>>> it at some point specifies infinite execution.
>>>>>>
>>>>>> Any algorithm that implements this truism is, of course, a halting
>>>>>> decider.
>>>>>
>>>>> Whether a computation is finite is more nuanced than it simply stops
>>>>> running otherwise an infinite loop that had its simulation aborted
>>>>> because its behavior matched the [infinite_loop] non-halting behavior
>>>>> pattern would have to be classified as a halting computation.
>>>>>
>>>>> Unless the simulating halt decider stops simulating Ĥ(Ĥ) at some point
>>>>> its simulation would be infinite ∴ meets the non-halting truism.
>>>>>
>>>>
>>>> But you can't use a 'Falsism' to change the facts about the definition.
>>>>
>>>> And, as I have said, there IS no pathological self-reference in the
>>>> problem.
>>>>
>>>> YOU create the self-reference by not implementing the required copy
>>>> operation. In actuality the Linz proof has no real self-reference, just
>>>> two copies of what just happens to be the same thing.
>>>>
>>>
>>> I am referring to the complete Peter Linz version where a copy <is>
>>> made.
>>>
>>> Ĥ.q0  wM  ⊢*  Ĥ.qx  wM  wM  ⊢*  Ĥ.qy  ∞
>>> Ĥ.q0  wM  ⊢*  Ĥ.qx  wM  wM  ⊢*  Ĥ.qn
>>>
>>> The above is adapted from (Linz:1990:319).
>>> It shows that Turing machine Ĥ copies its input at (q0) and begins
>>> executing an embedded copy of the original halt decider with this
>>> input at (qx).
>>>
>>> The (qy) state indicates that the halt decider decides that its input
>>> would halt. The ((qn)) state indicates the input would not halt. The
>>> appended (qa) and (qb) states cause Ĥ to infinitely loop if the halt
>>> decider decides that its input would halt.
>>>
>>> It can be understood from the above specification that when the
>>> embedded halt decider @Ĥ.qx bases its halting decision on simulating
>>> its input, and it has (Ĥ,  Ĥ) as its input that:
>>
>> But Linz's specification doesn't make any mention of simulating the
>> input, so there isn't anything intrinsincally recursive about Linz's
>> specification. It's only *your* decision to employ simulation which
>> leads to potentially infinite recursion.
>>
>> The actual specification involves no self-reference or recursion.
>>
>> André
>>
>
> Simulating halt decider H correctly decides non-halting on its input
> (Ĥ,Ĥ) on the basis of this truism:
>
> On 5/11/2021 11:10 AM, Ben Bacarisse wrote:
>> olcott <NoOne@NoWhere.com> writes:
>>
>>> Truism:
>>> Every simulation that would never stop unless Halts() stops
>>> it at some point specifies infinite execution.
>>
>> Any algorithm that implements this truism is, of course, a halting
>> decider.
>
>


Click here to read the complete article
Re: Infinitely Recursive input on HP Proofs

<daudnYwj2vzXUzz9nZ2dnUU7-XPNnZ2d@giganews.com>

  copy mid

https://www.novabbs.com/devel/article-flat.php?id=15621&group=comp.theory#15621

  copy link   Newsgroups: comp.theory
Path: i2pn2.org!i2pn.org!aioe.org!feeder5.feed.usenet.farm!feeder1.feed.usenet.farm!feed.usenet.farm!tr3.eu1.usenetexpress.com!feeder.usenetexpress.com!tr2.iad1.usenetexpress.com!border1.nntp.dca1.giganews.com!nntp.giganews.com!buffer1.nntp.dca1.giganews.com!news.giganews.com.POSTED!not-for-mail
NNTP-Posting-Date: Sun, 16 May 2021 21:00:42 -0500
Subject: Re: Infinitely Recursive input on HP Proofs
Newsgroups: comp.theory
References: <918df253-d4f0-4370-8f73-88e6690380a1@googlegroups.com> <a4ydnWkMIKhS8Dz9nZ2dnUU7-L3NnZ2d@giganews.com> <87im3i5t12.fsf@bsb.me.uk> <0sCdnWsgz4JPGjz9nZ2dnUU7-RvNnZ2d@giganews.com> <R%foI.542844$nn2.335922@fx48.iad> <-rednavQTY_BDTz9nZ2dnUU7-SXNnZ2d@giganews.com> <_yhoI.542847$nn2.449398@fx48.iad> <EsCdnduL051HNTz9nZ2dnUU7-d_NnZ2d@giganews.com> <HojoI.604824$%W6.542760@fx44.iad>
From: NoO...@NoWhere.com (olcott)
Date: Sun, 16 May 2021 21:01:37 -0500
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.10.1
MIME-Version: 1.0
In-Reply-To: <HojoI.604824$%W6.542760@fx44.iad>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Message-ID: <daudnYwj2vzXUzz9nZ2dnUU7-XPNnZ2d@giganews.com>
Lines: 74
X-Usenet-Provider: http://www.giganews.com
X-Trace: sv3-UUrqHRj98ppmXdT+Bn5PYD64+6vSLWrjkww5PwATkXeR32eFDHQr5G2qTm+RRRkHmfL5ew0mAYaRhYj!DbLDliCO6BB3dypKeP7Fr417pfJUhxoh7QjWs5rFstXNgLw3gDfXCaxrgPlUxl8oebZOuivjHYf4!XQ==
X-Complaints-To: abuse@giganews.com
X-DMCA-Notifications: http://www.giganews.com/info/dmca.html
X-Abuse-and-DMCA-Info: Please be sure to forward a copy of ALL headers
X-Abuse-and-DMCA-Info: Otherwise we will be unable to process your complaint properly
X-Postfilter: 1.3.40
X-Original-Bytes: 4445
 by: olcott - Mon, 17 May 2021 02:01 UTC

On 5/16/2021 8:11 PM, Richard Damon wrote:
> On 5/16/21 7:21 PM, olcott wrote:
>> On 5/16/2021 6:05 PM, Richard Damon wrote:
>
>>>
>>> But you can't use a 'Falsism' to change the facts about the definition.
>>>
>>> And, as I have said, there IS no pathological self-reference in the
>>> problem.
>>>
>>> YOU create the self-reference by not implementing the required copy
>>> operation. In actuality the Linz proof has no real self-reference, just
>>> two copies of what just happens to be the same thing.
>>>
>>
>> I am referring to the complete Peter Linz version where a copy <is> made.
>>
>> Ĥ.q0  wM  ⊢*  Ĥ.qx  wM  wM  ⊢*  Ĥ.qy  ∞
>> Ĥ.q0  wM  ⊢*  Ĥ.qx  wM  wM  ⊢*  Ĥ.qn
>>
>> The above is adapted from (Linz:1990:319).
>> It shows that Turing machine Ĥ copies its input at (q0) and begins
>> executing an embedded copy of the original halt decider with this input
>> at (qx).
>>
>> The (qy) state indicates that the halt decider decides that its input
>> would halt. The ((qn)) state indicates the input would not halt. The
>> appended (qa) and (qb) states cause Ĥ to infinitely loop if the halt
>> decider decides that its input would halt.
>>
>> It can be understood from the above specification that when the embedded
>> halt decider @Ĥ.qx bases its halting decision on simulating its input,
>> and it has (Ĥ,  Ĥ) as its input that:
>> Ĥ.q0 would copy its input and then Ĥ.qx would simulate its input with
>> this copy then
>> Ĥ.q0 would copy its input and then Ĥ.qx would simulate its input with
>> this copy then
>> Ĥ.q0 would copy its input and then Ĥ.qx would simulate its input with
>> this copy...
>> unless and until the halt decider @Ĥ.qx stops simulating its input.
>>
>> Linz, Peter 1990. An Introduction to Formal Languages and Automata.
>> Lexington/Toronto: D. C. Heath and Company.
>>
>>
>>
> Key point to notice is that Linz's description doesn't have ANY
> self-reference, or even things done via a 'reference'
>
> EVERYTHING is done with a copy, and there is no references to be self.

The computation Ĥ(<Ĥ>) has no self-reference in the exactly same way
that all entirely black cats are only rainbow colored and not black at all.

>
> H^ has its own copy of the algorithm of H in it, it doesn't 'reference'
> H, so this is NOT a self-reference.
>
> The input to H^ doesn't 'reference' H^, it is built on the description of H^
>
> With no references, you can't have self-reference.
>
> The only self-references in your 'proof' are the one YOU create by not
> making the 'required' copies. This also makes it so things are likely
> not actually the Equivalents of the required Turing Machines. Another
> flaw in your proof.
>

--
Copyright 2021 Pete Olcott

"Great spirits have always encountered violent opposition from mediocre
minds." Einstein

Re: Infinitely Recursive input on HP Proofs

<ngloI.149087$gq3.16218@fx04.iad>

  copy mid

https://www.novabbs.com/devel/article-flat.php?id=15624&group=comp.theory#15624

  copy link   Newsgroups: comp.theory
Path: i2pn2.org!i2pn.org!aioe.org!news.uzoreto.com!news-out.netnews.com!news.alt.net!fdc3.netnews.com!peer01.ams1!peer.ams1.xlned.com!news.xlned.com!peer03.iad!feed-me.highwinds-media.com!news.highwinds-media.com!fx04.iad.POSTED!not-for-mail
Subject: Re: Infinitely Recursive input on HP Proofs
Newsgroups: comp.theory
References: <918df253-d4f0-4370-8f73-88e6690380a1@googlegroups.com>
<a4ydnWkMIKhS8Dz9nZ2dnUU7-L3NnZ2d@giganews.com> <87im3i5t12.fsf@bsb.me.uk>
<0sCdnWsgz4JPGjz9nZ2dnUU7-RvNnZ2d@giganews.com>
<R%foI.542844$nn2.335922@fx48.iad>
<-rednavQTY_BDTz9nZ2dnUU7-SXNnZ2d@giganews.com>
<_yhoI.542847$nn2.449398@fx48.iad>
<EsCdnduL051HNTz9nZ2dnUU7-d_NnZ2d@giganews.com>
<HojoI.604824$%W6.542760@fx44.iad>
<daudnYwj2vzXUzz9nZ2dnUU7-XPNnZ2d@giganews.com>
From: Rich...@Damon-Family.org (Richard Damon)
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:78.0)
Gecko/20100101 Thunderbird/78.10.1
MIME-Version: 1.0
In-Reply-To: <daudnYwj2vzXUzz9nZ2dnUU7-XPNnZ2d@giganews.com>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Lines: 70
Message-ID: <ngloI.149087$gq3.16218@fx04.iad>
X-Complaints-To: abuse@easynews.com
Organization: Forte - www.forteinc.com
X-Complaints-Info: Please be sure to forward a copy of ALL headers otherwise we will be unable to process your complaint properly.
Date: Sun, 16 May 2021 23:18:42 -0400
X-Received-Bytes: 4149
 by: Richard Damon - Mon, 17 May 2021 03:18 UTC

On 5/16/21 10:01 PM, olcott wrote:
> On 5/16/2021 8:11 PM, Richard Damon wrote:
>> On 5/16/21 7:21 PM, olcott wrote:
>>> On 5/16/2021 6:05 PM, Richard Damon wrote:
>>
>>>>
>>>> But you can't use a 'Falsism' to change the facts about the definition.
>>>>
>>>> And, as I have said, there IS no pathological self-reference in the
>>>> problem.
>>>>
>>>> YOU create the self-reference by not implementing the required copy
>>>> operation. In actuality the Linz proof has no real self-reference, just
>>>> two copies of what just happens to be the same thing.
>>>>
>>>
>>> I am referring to the complete Peter Linz version where a copy <is>
>>> made.
>>>
>>> Ĥ.q0  wM  ⊢*  Ĥ.qx  wM  wM  ⊢*  Ĥ.qy  ∞
>>> Ĥ.q0  wM  ⊢*  Ĥ.qx  wM  wM  ⊢*  Ĥ.qn
>>>
>>> The above is adapted from (Linz:1990:319).
>>> It shows that Turing machine Ĥ copies its input at (q0) and begins
>>> executing an embedded copy of the original halt decider with this input
>>> at (qx).
>>>
>>> The (qy) state indicates that the halt decider decides that its input
>>> would halt. The ((qn)) state indicates the input would not halt. The
>>> appended (qa) and (qb) states cause Ĥ to infinitely loop if the halt
>>> decider decides that its input would halt.
>>>
>>> It can be understood from the above specification that when the embedded
>>> halt decider @Ĥ.qx bases its halting decision on simulating its input,
>>> and it has (Ĥ,  Ĥ) as its input that:
>>> Ĥ.q0 would copy its input and then Ĥ.qx would simulate its input with
>>> this copy then
>>> Ĥ.q0 would copy its input and then Ĥ.qx would simulate its input with
>>> this copy then
>>> Ĥ.q0 would copy its input and then Ĥ.qx would simulate its input with
>>> this copy...
>>> unless and until the halt decider @Ĥ.qx stops simulating its input.
>>>
>>> Linz, Peter 1990. An Introduction to Formal Languages and Automata.
>>> Lexington/Toronto: D. C. Heath and Company.
>>>
>>>
>>>
>> Key point to notice is that Linz's description doesn't have ANY
>> self-reference, or even things done via a 'reference'
>>
>> EVERYTHING is done with a copy, and there is no references to be self.
>
> The computation Ĥ(<Ĥ>) has no self-reference in the exactly same way
> that all entirely black cats are only rainbow colored and not black at all.

Please show where in a proper encoding of H^(H^) you ever have something
generate an actual reference to something. PLEASE.

H^ has a COPY OF (not a reference to) H within it.

It is given a DESCRIPTION OF (not a reference to) H^

No reference in sight!

YOU fail to copy Halts, and make H_Hat use a reference to it, but that
is actually in violation to the structure described in Linz.

Turing Machines do not DO 'references'.

Re: Infinitely Recursive input on HP Proofs

<lO2dncjmT5ftfDz9nZ2dnUU7-IWdnZ2d@giganews.com>

  copy mid

https://www.novabbs.com/devel/article-flat.php?id=15625&group=comp.theory#15625

  copy link   Newsgroups: comp.theory
Path: i2pn2.org!i2pn.org!weretis.net!feeder6.news.weretis.net!news.snarked.org!border2.nntp.dca1.giganews.com!nntp.giganews.com!buffer2.nntp.dca1.giganews.com!buffer1.nntp.dca1.giganews.com!news.giganews.com.POSTED!not-for-mail
NNTP-Posting-Date: Sun, 16 May 2021 22:22:24 -0500
Subject: Re: Infinitely Recursive input on HP Proofs
Newsgroups: comp.theory
References: <918df253-d4f0-4370-8f73-88e6690380a1@googlegroups.com>
<a4ydnWkMIKhS8Dz9nZ2dnUU7-L3NnZ2d@giganews.com> <87im3i5t12.fsf@bsb.me.uk>
<0sCdnWsgz4JPGjz9nZ2dnUU7-RvNnZ2d@giganews.com>
<R%foI.542844$nn2.335922@fx48.iad>
<-rednavQTY_BDTz9nZ2dnUU7-SXNnZ2d@giganews.com>
<_yhoI.542847$nn2.449398@fx48.iad>
<EsCdnduL051HNTz9nZ2dnUU7-d_NnZ2d@giganews.com>
<HojoI.604824$%W6.542760@fx44.iad>
<daudnYwj2vzXUzz9nZ2dnUU7-XPNnZ2d@giganews.com>
<ngloI.149087$gq3.16218@fx04.iad>
From: NoO...@NoWhere.com (olcott)
Date: Sun, 16 May 2021 22:23:19 -0500
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101
Thunderbird/78.10.1
MIME-Version: 1.0
In-Reply-To: <ngloI.149087$gq3.16218@fx04.iad>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Message-ID: <lO2dncjmT5ftfDz9nZ2dnUU7-IWdnZ2d@giganews.com>
Lines: 87
X-Usenet-Provider: http://www.giganews.com
X-Trace: sv3-JlW9eZ+rbcffw5ONdGWedl4Y5y3rUokfuErT7B4S7Nh3JwR9OZNS11AILdAt7f3ZwTlYnbUz01/eN4q!c7FAmXkoKLwNleKvbUPN3LopT17yDz/glX0RuLIOBSPMxdCr2N/bRab2M65/vKbSYm4jOGXtPK0F!8g==
X-Complaints-To: abuse@giganews.com
X-DMCA-Notifications: http://www.giganews.com/info/dmca.html
X-Abuse-and-DMCA-Info: Please be sure to forward a copy of ALL headers
X-Abuse-and-DMCA-Info: Otherwise we will be unable to process your complaint properly
X-Postfilter: 1.3.40
X-Original-Bytes: 4951
 by: olcott - Mon, 17 May 2021 03:23 UTC

On 5/16/2021 10:18 PM, Richard Damon wrote:
> On 5/16/21 10:01 PM, olcott wrote:
>> On 5/16/2021 8:11 PM, Richard Damon wrote:
>>> On 5/16/21 7:21 PM, olcott wrote:
>>>> On 5/16/2021 6:05 PM, Richard Damon wrote:
>>>
>>>>>
>>>>> But you can't use a 'Falsism' to change the facts about the definition.
>>>>>
>>>>> And, as I have said, there IS no pathological self-reference in the
>>>>> problem.
>>>>>
>>>>> YOU create the self-reference by not implementing the required copy
>>>>> operation. In actuality the Linz proof has no real self-reference, just
>>>>> two copies of what just happens to be the same thing.
>>>>>
>>>>
>>>> I am referring to the complete Peter Linz version where a copy <is>
>>>> made.
>>>>
>>>> Ĥ.q0  wM  ⊢*  Ĥ.qx  wM  wM  ⊢*  Ĥ.qy  ∞
>>>> Ĥ.q0  wM  ⊢*  Ĥ.qx  wM  wM  ⊢*  Ĥ.qn
>>>>
>>>> The above is adapted from (Linz:1990:319).
>>>> It shows that Turing machine Ĥ copies its input at (q0) and begins
>>>> executing an embedded copy of the original halt decider with this input
>>>> at (qx).
>>>>
>>>> The (qy) state indicates that the halt decider decides that its input
>>>> would halt. The ((qn)) state indicates the input would not halt. The
>>>> appended (qa) and (qb) states cause Ĥ to infinitely loop if the halt
>>>> decider decides that its input would halt.
>>>>
>>>> It can be understood from the above specification that when the embedded
>>>> halt decider @Ĥ.qx bases its halting decision on simulating its input,
>>>> and it has (Ĥ,  Ĥ) as its input that:
>>>> Ĥ.q0 would copy its input and then Ĥ.qx would simulate its input with
>>>> this copy then
>>>> Ĥ.q0 would copy its input and then Ĥ.qx would simulate its input with
>>>> this copy then
>>>> Ĥ.q0 would copy its input and then Ĥ.qx would simulate its input with
>>>> this copy...
>>>> unless and until the halt decider @Ĥ.qx stops simulating its input.
>>>>
>>>> Linz, Peter 1990. An Introduction to Formal Languages and Automata.
>>>> Lexington/Toronto: D. C. Heath and Company.
>>>>
>>>>
>>>>
>>> Key point to notice is that Linz's description doesn't have ANY
>>> self-reference, or even things done via a 'reference'
>>>
>>> EVERYTHING is done with a copy, and there is no references to be self.
>>
>> The computation Ĥ(<Ĥ>) has no self-reference in the exactly same way
>> that all entirely black cats are only rainbow colored and not black at all.
>
> Please show where in a proper encoding of H^(H^) you ever have something
> generate an actual reference to something. PLEASE.
>

http://www.liarparadox.org/Peter_Linz_HP(Pages_315-320).pdf

> H^ has a COPY OF (not a reference to) H within it.
>
> It is given a DESCRIPTION OF (not a reference to) H^
>
> No reference in sight!
>

I have provided the full reference at least 50 times now.

> YOU fail to copy Halts, and make H_Hat use a reference to it, but that
> is actually in violation to the structure described in Linz.
>
> Turing Machines do not DO 'references'.
>

I changed the subject from the x86utm H_Hat C/x86 computation to the
actual Linz: Ĥ(Ĥ) a few messages ago and you didn't notice.

--
Copyright 2021 Pete Olcott

"Great spirits have always encountered violent opposition from mediocre
minds." Einstein

Re: Infinitely Recursive input on HP Proofs

<BbsoI.227125$N_4.174401@fx36.iad>

  copy mid

https://www.novabbs.com/devel/article-flat.php?id=15640&group=comp.theory#15640

  copy link   Newsgroups: comp.theory
Path: i2pn2.org!i2pn.org!aioe.org!feeder1.feed.usenet.farm!feed.usenet.farm!news-out.netnews.com!news.alt.net!fdc3.netnews.com!peer03.ams1!peer.ams1.xlned.com!news.xlned.com!peer01.iad!feed-me.highwinds-media.com!news.highwinds-media.com!fx36.iad.POSTED!not-for-mail
Subject: Re: Infinitely Recursive input on HP Proofs
Newsgroups: comp.theory
References: <918df253-d4f0-4370-8f73-88e6690380a1@googlegroups.com>
<a4ydnWkMIKhS8Dz9nZ2dnUU7-L3NnZ2d@giganews.com> <87im3i5t12.fsf@bsb.me.uk>
<0sCdnWsgz4JPGjz9nZ2dnUU7-RvNnZ2d@giganews.com>
<R%foI.542844$nn2.335922@fx48.iad>
<-rednavQTY_BDTz9nZ2dnUU7-SXNnZ2d@giganews.com>
<_yhoI.542847$nn2.449398@fx48.iad>
<EsCdnduL051HNTz9nZ2dnUU7-d_NnZ2d@giganews.com>
<HojoI.604824$%W6.542760@fx44.iad>
<daudnYwj2vzXUzz9nZ2dnUU7-XPNnZ2d@giganews.com>
<ngloI.149087$gq3.16218@fx04.iad>
<lO2dncjmT5ftfDz9nZ2dnUU7-IWdnZ2d@giganews.com>
From: Rich...@Damon-Family.org (Richard Damon)
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:78.0)
Gecko/20100101 Thunderbird/78.10.1
MIME-Version: 1.0
In-Reply-To: <lO2dncjmT5ftfDz9nZ2dnUU7-IWdnZ2d@giganews.com>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Lines: 89
Message-ID: <BbsoI.227125$N_4.174401@fx36.iad>
X-Complaints-To: abuse@easynews.com
Organization: Forte - www.forteinc.com
X-Complaints-Info: Please be sure to forward a copy of ALL headers otherwise we will be unable to process your complaint properly.
Date: Mon, 17 May 2021 07:11:30 -0400
X-Received-Bytes: 4792
 by: Richard Damon - Mon, 17 May 2021 11:11 UTC

On 5/16/21 11:23 PM, olcott wrote:
> On 5/16/2021 10:18 PM, Richard Damon wrote:
>> On 5/16/21 10:01 PM, olcott wrote:
>>> On 5/16/2021 8:11 PM, Richard Damon wrote:
>>>> On 5/16/21 7:21 PM, olcott wrote:
>>>>> On 5/16/2021 6:05 PM, Richard Damon wrote:
>>>>
>>>>>>
>>>>>> But you can't use a 'Falsism' to change the facts about the
>>>>>> definition.
>>>>>>
>>>>>> And, as I have said, there IS no pathological self-reference in the
>>>>>> problem.
>>>>>>
>>>>>> YOU create the self-reference by not implementing the required copy
>>>>>> operation. In actuality the Linz proof has no real self-reference,
>>>>>> just
>>>>>> two copies of what just happens to be the same thing.
>>>>>>
>>>>>
>>>>> I am referring to the complete Peter Linz version where a copy <is>
>>>>> made.
>>>>>
>>>>> Ĥ.q0  wM  ⊢*  Ĥ.qx  wM  wM  ⊢*  Ĥ.qy  ∞
>>>>> Ĥ.q0  wM  ⊢*  Ĥ.qx  wM  wM  ⊢*  Ĥ.qn
>>>>>
>>>>> The above is adapted from (Linz:1990:319).
>>>>> It shows that Turing machine Ĥ copies its input at (q0) and begins
>>>>> executing an embedded copy of the original halt decider with this
>>>>> input
>>>>> at (qx).
>>>>>
>>>>> The (qy) state indicates that the halt decider decides that its input
>>>>> would halt. The ((qn)) state indicates the input would not halt. The
>>>>> appended (qa) and (qb) states cause Ĥ to infinitely loop if the halt
>>>>> decider decides that its input would halt.
>>>>>
>>>>> It can be understood from the above specification that when the
>>>>> embedded
>>>>> halt decider @Ĥ.qx bases its halting decision on simulating its input,
>>>>> and it has (Ĥ,  Ĥ) as its input that:
>>>>> Ĥ.q0 would copy its input and then Ĥ.qx would simulate its input with
>>>>> this copy then
>>>>> Ĥ.q0 would copy its input and then Ĥ.qx would simulate its input with
>>>>> this copy then
>>>>> Ĥ.q0 would copy its input and then Ĥ.qx would simulate its input with
>>>>> this copy...
>>>>> unless and until the halt decider @Ĥ.qx stops simulating its input.
>>>>>
>>>>> Linz, Peter 1990. An Introduction to Formal Languages and Automata.
>>>>> Lexington/Toronto: D. C. Heath and Company.
>>>>>
>>>>>
>>>>>
>>>> Key point to notice is that Linz's description doesn't have ANY
>>>> self-reference, or even things done via a 'reference'
>>>>
>>>> EVERYTHING is done with a copy, and there is no references to be self.
>>>
>>> The computation Ĥ(<Ĥ>) has no self-reference in the exactly same way
>>> that all entirely black cats are only rainbow colored and not black
>>> at all.
>>
>> Please show where in a proper encoding of H^(H^) you ever have something
>> generate an actual reference to something. PLEASE.
>>
>
> http://www.liarparadox.org/Peter_Linz_HP(Pages_315-320).pdf
>
>> H^ has a COPY OF (not a reference to) H within it.
>>
>> It is given a DESCRIPTION OF (not a reference to) H^
>>
>> No reference in sight!
>>
>
> I have provided the full reference at least 50 times now.
>
>> YOU fail to copy Halts, and make H_Hat use a reference to it, but that
>> is actually in violation to the structure described in Linz.
>>
>> Turing Machines do not DO 'references'.
>>
>
> I changed the subject from the x86utm H_Hat C/x86 computation to the
> actual Linz: Ĥ(Ĥ) a few messages ago and you didn't notice.
>
>

Re: Infinitely Recursive input on HP Proofs

<GpsoI.240833$PE7.20906@fx39.iad>

  copy mid

https://www.novabbs.com/devel/article-flat.php?id=15641&group=comp.theory#15641

  copy link   Newsgroups: comp.theory
Path: i2pn2.org!i2pn.org!aioe.org!news.uzoreto.com!news-out.netnews.com!news.alt.net!fdc3.netnews.com!peer03.ams1!peer.ams1.xlned.com!news.xlned.com!peer01.iad!feed-me.highwinds-media.com!news.highwinds-media.com!fx39.iad.POSTED!not-for-mail
Subject: Re: Infinitely Recursive input on HP Proofs
Newsgroups: comp.theory
References: <918df253-d4f0-4370-8f73-88e6690380a1@googlegroups.com>
<a4ydnWkMIKhS8Dz9nZ2dnUU7-L3NnZ2d@giganews.com> <87im3i5t12.fsf@bsb.me.uk>
<0sCdnWsgz4JPGjz9nZ2dnUU7-RvNnZ2d@giganews.com>
<R%foI.542844$nn2.335922@fx48.iad>
<-rednavQTY_BDTz9nZ2dnUU7-SXNnZ2d@giganews.com>
<_yhoI.542847$nn2.449398@fx48.iad>
<EsCdnduL051HNTz9nZ2dnUU7-d_NnZ2d@giganews.com>
<HojoI.604824$%W6.542760@fx44.iad>
<daudnYwj2vzXUzz9nZ2dnUU7-XPNnZ2d@giganews.com>
<ngloI.149087$gq3.16218@fx04.iad>
<lO2dncjmT5ftfDz9nZ2dnUU7-IWdnZ2d@giganews.com>
From: Rich...@Damon-Family.org (Richard Damon)
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:78.0)
Gecko/20100101 Thunderbird/78.10.1
MIME-Version: 1.0
In-Reply-To: <lO2dncjmT5ftfDz9nZ2dnUU7-IWdnZ2d@giganews.com>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Lines: 140
Message-ID: <GpsoI.240833$PE7.20906@fx39.iad>
X-Complaints-To: abuse@easynews.com
Organization: Forte - www.forteinc.com
X-Complaints-Info: Please be sure to forward a copy of ALL headers otherwise we will be unable to process your complaint properly.
Date: Mon, 17 May 2021 07:26:31 -0400
X-Received-Bytes: 6992
 by: Richard Damon - Mon, 17 May 2021 11:26 UTC

On 5/16/21 11:23 PM, olcott wrote:
> On 5/16/2021 10:18 PM, Richard Damon wrote:
>> On 5/16/21 10:01 PM, olcott wrote:
>>> On 5/16/2021 8:11 PM, Richard Damon wrote:
>>>> On 5/16/21 7:21 PM, olcott wrote:
>>>>> On 5/16/2021 6:05 PM, Richard Damon wrote:
>>>>
>>>>>>
>>>>>> But you can't use a 'Falsism' to change the facts about the
>>>>>> definition.
>>>>>>
>>>>>> And, as I have said, there IS no pathological self-reference in the
>>>>>> problem.
>>>>>>
>>>>>> YOU create the self-reference by not implementing the required copy
>>>>>> operation. In actuality the Linz proof has no real self-reference,
>>>>>> just
>>>>>> two copies of what just happens to be the same thing.
>>>>>>
>>>>>
>>>>> I am referring to the complete Peter Linz version where a copy <is>
>>>>> made.
>>>>>
>>>>> Ĥ.q0  wM  ⊢*  Ĥ.qx  wM  wM  ⊢*  Ĥ.qy  ∞
>>>>> Ĥ.q0  wM  ⊢*  Ĥ.qx  wM  wM  ⊢*  Ĥ.qn
>>>>>
>>>>> The above is adapted from (Linz:1990:319).
>>>>> It shows that Turing machine Ĥ copies its input at (q0) and begins
>>>>> executing an embedded copy of the original halt decider with this
>>>>> input
>>>>> at (qx).
>>>>>
>>>>> The (qy) state indicates that the halt decider decides that its input
>>>>> would halt. The ((qn)) state indicates the input would not halt. The
>>>>> appended (qa) and (qb) states cause Ĥ to infinitely loop if the halt
>>>>> decider decides that its input would halt.
>>>>>
>>>>> It can be understood from the above specification that when the
>>>>> embedded
>>>>> halt decider @Ĥ.qx bases its halting decision on simulating its input,
>>>>> and it has (Ĥ,  Ĥ) as its input that:
>>>>> Ĥ.q0 would copy its input and then Ĥ.qx would simulate its input with
>>>>> this copy then
>>>>> Ĥ.q0 would copy its input and then Ĥ.qx would simulate its input with
>>>>> this copy then
>>>>> Ĥ.q0 would copy its input and then Ĥ.qx would simulate its input with
>>>>> this copy...
>>>>> unless and until the halt decider @Ĥ.qx stops simulating its input.
>>>>>
>>>>> Linz, Peter 1990. An Introduction to Formal Languages and Automata.
>>>>> Lexington/Toronto: D. C. Heath and Company.
>>>>>
>>>>>
>>>>>
>>>> Key point to notice is that Linz's description doesn't have ANY
>>>> self-reference, or even things done via a 'reference'
>>>>
>>>> EVERYTHING is done with a copy, and there is no references to be self.
>>>
>>> The computation Ĥ(<Ĥ>) has no self-reference in the exactly same way
>>> that all entirely black cats are only rainbow colored and not black
>>> at all.
>>
>> Please show where in a proper encoding of H^(H^) you ever have something
>> generate an actual reference to something. PLEASE.
>>
>
> http://www.liarparadox.org/Peter_Linz_HP(Pages_315-320).pdf
>
>> H^ has a COPY OF (not a reference to) H within it.
>>
>> It is given a DESCRIPTION OF (not a reference to) H^
>>
>> No reference in sight!
>>
>
> I have provided the full reference at least 50 times now.

YOU have posted REFERENCES to articles, yes.

You haven't provided ANY indication of where the problem you are
describing actually includes anything IN THE PROBLEM that is actually a
reference to something else in th problem.

If nothing refers by reference, there can't be self-reference.

H^ includes the code for H not by reference, but by making a copy. When
H is deciding on H^, it doesn't see 'it self' in the machine, but
machine that just happens to match what it does.

The input to H^ isn't a reference to itself, but a pattern that just
happens to match a description of itself.

At no point can anything in the problem just look at what it is given
and say, oh, that's ME!

YOU change the definition of the problem to convert these copies into
actual references, and in doing so you actually break the Turing
Equivalence, because at the fundamental level, Turing Machines don't do
references.

I will again challenge you, WHERE in the original problem is there
actually a reference that becomes a self-reference?

>
>> YOU fail to copy Halts, and make H_Hat use a reference to it, but that
>> is actually in violation to the structure described in Linz.
>>
>> Turing Machines do not DO 'references'.
>>
>
> I changed the subject from the x86utm H_Hat C/x86 computation to the
> actual Linz: Ĥ(Ĥ) a few messages ago and you didn't notice.
>
>

Non-responsive. Just proves that you didn't actually read things but
just throw out random words when you feel cornered.

Yes, a machine that claims to be a decider and just starts by blindly
simulating will get into an infinite loop of recusing down the
simulation tree. These means that said claimed decider will not be able
to answer in finite time. This makes that claimed decider wrong, not the
problem.

If said claimed decider is improved to see the problem and stop it, now
said decider may be able to answer in time, but, at least with your
method, it can get the wrong answer because it doesn't get to see what
the machine it is deciding on will do with that answer.

Again, that is the problem with the design of that claimed decider, not
the problem.

ALL you have shown is that the method you claim is the obvious way to
try to solve the problem doesn't work, not that some how the problem is
defective.

There is actually no basis to claim that there actually NEEDS to be a
way to solve the problem, the answer that you can't build a Halt Decider
that get all problems correctly is a perfectly good answer.

Re: Infinitely Recursive input on HP Proofs

<15406379-420c-4c32-b713-be57e31901ban@googlegroups.com>

  copy mid

https://www.novabbs.com/devel/article-flat.php?id=15645&group=comp.theory#15645

  copy link   Newsgroups: comp.theory
X-Received: by 2002:a37:aa0b:: with SMTP id t11mr56580235qke.70.1621255528887;
Mon, 17 May 2021 05:45:28 -0700 (PDT)
X-Received: by 2002:a25:d257:: with SMTP id j84mr72012669ybg.251.1621255528715;
Mon, 17 May 2021 05:45:28 -0700 (PDT)
Path: i2pn2.org!i2pn.org!weretis.net!feeder8.news.weretis.net!proxad.net!feeder1-2.proxad.net!209.85.160.216.MISMATCH!news-out.google.com!nntp.google.com!postnews.google.com!google-groups.googlegroups.com!not-for-mail
Newsgroups: comp.theory
Date: Mon, 17 May 2021 05:45:28 -0700 (PDT)
In-Reply-To: <GpsoI.240833$PE7.20906@fx39.iad>
Injection-Info: google-groups.googlegroups.com; posting-host=2a00:23a8:400a:5601:95a9:12e4:8c0a:4a4;
posting-account=Dz2zqgkAAADlK5MFu78bw3ab-BRFV4Qn
NNTP-Posting-Host: 2a00:23a8:400a:5601:95a9:12e4:8c0a:4a4
References: <918df253-d4f0-4370-8f73-88e6690380a1@googlegroups.com>
<a4ydnWkMIKhS8Dz9nZ2dnUU7-L3NnZ2d@giganews.com> <87im3i5t12.fsf@bsb.me.uk>
<0sCdnWsgz4JPGjz9nZ2dnUU7-RvNnZ2d@giganews.com> <R%foI.542844$nn2.335922@fx48.iad>
<-rednavQTY_BDTz9nZ2dnUU7-SXNnZ2d@giganews.com> <_yhoI.542847$nn2.449398@fx48.iad>
<EsCdnduL051HNTz9nZ2dnUU7-d_NnZ2d@giganews.com> <HojoI.604824$%W6.542760@fx44.iad>
<daudnYwj2vzXUzz9nZ2dnUU7-XPNnZ2d@giganews.com> <ngloI.149087$gq3.16218@fx04.iad>
<lO2dncjmT5ftfDz9nZ2dnUU7-IWdnZ2d@giganews.com> <GpsoI.240833$PE7.20906@fx39.iad>
User-Agent: G2/1.0
MIME-Version: 1.0
Message-ID: <15406379-420c-4c32-b713-be57e31901ban@googlegroups.com>
Subject: Re: Infinitely Recursive input on HP Proofs
From: malcolm....@gmail.com (Malcolm McLean)
Injection-Date: Mon, 17 May 2021 12:45:28 +0000
Content-Type: text/plain; charset="UTF-8"
 by: Malcolm McLean - Mon, 17 May 2021 12:45 UTC

On Monday, 17 May 2021 at 12:26:33 UTC+1, Richard Damon wrote:
>
> If said claimed decider is improved to see the problem and stop it, now
> said decider may be able to answer in time, but, at least with your
> method, it can get the wrong answer because it doesn't get to see what
> the machine it is deciding on will do with that answer.
>
> Again, that is the problem with the design of that claimed decider, not
> the problem.
>
It's an inherent problem with all deciders. You can simulate until it
"looks stuck" and you might have a very good decider. But there will
be some inputs which "look stuck" but aren't, and you will decide
wrongly, and you can't design that out, because whatever your criteria
an attacker can always look stuck, add one one step, then halt.

Re: Infinitely Recursive input on HP Proofs

<Va-dnaC0HKatFz_9nZ2dnUU7-bfNnZ2d@giganews.com>

  copy mid

https://www.novabbs.com/devel/article-flat.php?id=15649&group=comp.theory#15649

  copy link   Newsgroups: comp.theory
Path: i2pn2.org!i2pn.org!weretis.net!feeder8.news.weretis.net!news.uzoreto.com!tr1.eu1.usenetexpress.com!feeder.usenetexpress.com!tr3.iad1.usenetexpress.com!border1.nntp.dca1.giganews.com!nntp.giganews.com!buffer1.nntp.dca1.giganews.com!news.giganews.com.POSTED!not-for-mail
NNTP-Posting-Date: Mon, 17 May 2021 10:22:24 -0500
Subject: Re: Infinitely Recursive input on HP Proofs
Newsgroups: comp.theory
References: <918df253-d4f0-4370-8f73-88e6690380a1@googlegroups.com> <a4ydnWkMIKhS8Dz9nZ2dnUU7-L3NnZ2d@giganews.com> <87im3i5t12.fsf@bsb.me.uk> <0sCdnWsgz4JPGjz9nZ2dnUU7-RvNnZ2d@giganews.com> <R%foI.542844$nn2.335922@fx48.iad> <-rednavQTY_BDTz9nZ2dnUU7-SXNnZ2d@giganews.com> <_yhoI.542847$nn2.449398@fx48.iad> <EsCdnduL051HNTz9nZ2dnUU7-d_NnZ2d@giganews.com> <HojoI.604824$%W6.542760@fx44.iad> <daudnYwj2vzXUzz9nZ2dnUU7-XPNnZ2d@giganews.com> <ngloI.149087$gq3.16218@fx04.iad> <lO2dncjmT5ftfDz9nZ2dnUU7-IWdnZ2d@giganews.com> <GpsoI.240833$PE7.20906@fx39.iad> <15406379-420c-4c32-b713-be57e31901ban@googlegroups.com>
From: NoO...@NoWhere.com (olcott)
Date: Mon, 17 May 2021 10:23:19 -0500
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.10.1
MIME-Version: 1.0
In-Reply-To: <15406379-420c-4c32-b713-be57e31901ban@googlegroups.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Message-ID: <Va-dnaC0HKatFz_9nZ2dnUU7-bfNnZ2d@giganews.com>
Lines: 82
X-Usenet-Provider: http://www.giganews.com
X-Trace: sv3-eLrHnKcz6qippIWmFTcl5l9wNSmTae09E4BNWMfGvOfcfztlFGrGfno/ItVdu65H0cyIS4Enjr2QEKb!iKXIWpEaGVOAvHfzibqRC7TNLYHlF8SyUWmuotCIlPkfBGm1WkmKJWN460p8fFjIfPif/qnoSLzq!3Q==
X-Complaints-To: abuse@giganews.com
X-DMCA-Notifications: http://www.giganews.com/info/dmca.html
X-Abuse-and-DMCA-Info: Please be sure to forward a copy of ALL headers
X-Abuse-and-DMCA-Info: Otherwise we will be unable to process your complaint properly
X-Postfilter: 1.3.40
X-Original-Bytes: 5292
 by: olcott - Mon, 17 May 2021 15:23 UTC

On 5/17/2021 7:45 AM, Malcolm McLean wrote:
> On Monday, 17 May 2021 at 12:26:33 UTC+1, Richard Damon wrote:
>>
>> If said claimed decider is improved to see the problem and stop it, now
>> said decider may be able to answer in time, but, at least with your
>> method, it can get the wrong answer because it doesn't get to see what
>> the machine it is deciding on will do with that answer.
>>
>> Again, that is the problem with the design of that claimed decider, not
>> the problem.
>>
> It's an inherent problem with all deciders. You can simulate until it
> "looks stuck" and you might have a very good decider. But there will
> be some inputs which "look stuck" but aren't, and you will decide
> wrongly, and you can't design that out, because whatever your criteria
> an attacker can always look stuck, add one one step, then halt.
>

When a sufficient non-halting behavior pattern of [infinite_loop] or
[infinitely_nested_simulation] has been matched then it has been proven
on the basis that counter-examples do not exist that these patterns do
match behavior that will never stop unless its simulation is aborted.

The [infinitely_nested_simulation] behavior pattern must be adapted to
the Linz proof Ĥ(<Ĥ>).

That the behavior Ĥ(<Ĥ>) would meet a [infinitely_nested_simulation]
behavior pattern can be seen on the basis of the execution trace of
Ĥ(<Ĥ>) shown below:

Ĥ.q0 wM ⊢* Ĥ.qx wM wM ⊢* Ĥ.qy ∞
Ĥ.q0 wM ⊢* Ĥ.qx wM wM ⊢* Ĥ.qn

The above is adapted from (Linz:1990:319).
It shows that Turing machine Ĥ copies its input at (q0) and begins
executing an embedded copy of the original halt decider with this input
at (qx).

The (qy) state indicates that the halt decider decides that its input
would halt. The ((qn)) state indicates the input would not halt. The
appended (qa) and (qb) states cause Ĥ to infinitely loop if the halt
decider decides that its input would halt.

Linz, Peter 1990. An Introduction to Formal Languages and Automata.
Lexington/Toronto: D. C. Heath and Company.

The above definition specifies this execution trace:
It can be understood from the above specification that when the embedded
halt decider @Ĥ.qx bases its halting decision on simulating its input,
and it has (<Ĥ>,<Ĥ>) as its input that:
Ĥ.q0 would copy its input and then Ĥ.qx would simulate its input with
this copy then
Ĥ.q0 would copy its input and then Ĥ.qx would simulate its input with
this copy then
Ĥ.q0 would copy its input and then Ĥ.qx would simulate its input with
this copy...
unless and until the halt decider @Ĥ.qx stops simulating its input.

As long as any halt decider must ever stop simulating its input the
input does specify non-halting. The first halt decider that see this
reports it.

The convoluted way of saying Ĥ(<Ĥ>):
Now Ĥ is a Turing machine, so that it will have some description in Σ*,
say ŵ. This string, in addition to being the description of Ĥ can also
be used
as input string. We can therefore legitimately ask what would happen if Ĥ is
applied to ŵ.

Because Ĥ(<Ĥ>) must abort the simulation of its input ∴ this input <is>
correctly decided as non-halting.

Because H(<Ĥ>,<Ĥ>) must abort the simulation of its input ∴ this input
<is> correctly decided as non-halting.

--
Copyright 2021 Pete Olcott

"Great spirits have always encountered violent opposition from mediocre
minds." Einstein

Re: Infinitely Recursive input on HP Proofs

<87sg2l2ma2.fsf@bsb.me.uk>

  copy mid

https://www.novabbs.com/devel/article-flat.php?id=15664&group=comp.theory#15664

  copy link   Newsgroups: comp.theory
Path: i2pn2.org!i2pn.org!eternal-september.org!reader02.eternal-september.org!.POSTED!not-for-mail
From: ben.use...@bsb.me.uk (Ben Bacarisse)
Newsgroups: comp.theory
Subject: Re: Infinitely Recursive input on HP Proofs
Date: Mon, 17 May 2021 20:27:49 +0100
Organization: A noiseless patient Spider
Lines: 20
Message-ID: <87sg2l2ma2.fsf@bsb.me.uk>
References: <918df253-d4f0-4370-8f73-88e6690380a1@googlegroups.com>
<a4ydnWkMIKhS8Dz9nZ2dnUU7-L3NnZ2d@giganews.com>
<87im3i5t12.fsf@bsb.me.uk>
<0sCdnWsgz4JPGjz9nZ2dnUU7-RvNnZ2d@giganews.com>
<R%foI.542844$nn2.335922@fx48.iad>
<-rednavQTY_BDTz9nZ2dnUU7-SXNnZ2d@giganews.com>
<_yhoI.542847$nn2.449398@fx48.iad>
<EsCdnduL051HNTz9nZ2dnUU7-d_NnZ2d@giganews.com>
<HojoI.604824$%W6.542760@fx44.iad>
<daudnYwj2vzXUzz9nZ2dnUU7-XPNnZ2d@giganews.com>
<ngloI.149087$gq3.16218@fx04.iad>
<lO2dncjmT5ftfDz9nZ2dnUU7-IWdnZ2d@giganews.com>
<GpsoI.240833$PE7.20906@fx39.iad>
<15406379-420c-4c32-b713-be57e31901ban@googlegroups.com>
Mime-Version: 1.0
Content-Type: text/plain
Injection-Info: reader02.eternal-september.org; posting-host="342c78f756b73b7a65cfaf9b40e676c4";
logging-data="18640"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1+JpJfMvs7eKzLnra0JvW9lPrX8A8jn8N8="
Cancel-Lock: sha1:l0dRpcHaykqY8x/IcUmkucgsCbQ=
sha1:szuFjvzvewIh4RG1hNyJcX5Ee7g=
X-BSB-Auth: 1.de62fa2303e209b304c8.20210517202749BST.87sg2l2ma2.fsf@bsb.me.uk
 by: Ben Bacarisse - Mon, 17 May 2021 19:27 UTC

Malcolm McLean <malcolm.arthur.mclean@gmail.com> writes:

> On Monday, 17 May 2021 at 12:26:33 UTC+1, Richard Damon wrote:
>>
>> If said claimed decider is improved to see the problem and stop it, now
>> said decider may be able to answer in time, but, at least with your
>> method, it can get the wrong answer because it doesn't get to see what
>> the machine it is deciding on will do with that answer.
>>
>> Again, that is the problem with the design of that claimed decider, not
>> the problem.
>>
> It's an inherent problem with all deciders. You can simulate until it
> "looks stuck" and you might have a very good decider.

You seem determined to encourage PO's misconceptions. PO assumes
simulation is involved. No one else should.

--
Ben.

Re: Infinitely Recursive input on HP Proofs

<356dndvIucnMWT_9nZ2dnUU7-bmdnZ2d@giganews.com>

  copy mid

https://www.novabbs.com/devel/article-flat.php?id=15665&group=comp.theory#15665

  copy link   Newsgroups: comp.theory
Path: i2pn2.org!i2pn.org!weretis.net!feeder6.news.weretis.net!news.snarked.org!border2.nntp.dca1.giganews.com!nntp.giganews.com!buffer2.nntp.dca1.giganews.com!news.giganews.com.POSTED!not-for-mail
NNTP-Posting-Date: Mon, 17 May 2021 14:30:25 -0500
Subject: Re: Infinitely Recursive input on HP Proofs
Newsgroups: comp.theory
References: <918df253-d4f0-4370-8f73-88e6690380a1@googlegroups.com>
<a4ydnWkMIKhS8Dz9nZ2dnUU7-L3NnZ2d@giganews.com> <87im3i5t12.fsf@bsb.me.uk>
<0sCdnWsgz4JPGjz9nZ2dnUU7-RvNnZ2d@giganews.com>
<R%foI.542844$nn2.335922@fx48.iad>
<-rednavQTY_BDTz9nZ2dnUU7-SXNnZ2d@giganews.com>
<_yhoI.542847$nn2.449398@fx48.iad>
<EsCdnduL051HNTz9nZ2dnUU7-d_NnZ2d@giganews.com>
<HojoI.604824$%W6.542760@fx44.iad>
<daudnYwj2vzXUzz9nZ2dnUU7-XPNnZ2d@giganews.com>
<ngloI.149087$gq3.16218@fx04.iad>
<lO2dncjmT5ftfDz9nZ2dnUU7-IWdnZ2d@giganews.com>
<GpsoI.240833$PE7.20906@fx39.iad>
<15406379-420c-4c32-b713-be57e31901ban@googlegroups.com>
<87sg2l2ma2.fsf@bsb.me.uk>
From: NoO...@NoWhere.com (olcott)
Date: Mon, 17 May 2021 14:31:20 -0500
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101
Thunderbird/78.10.1
MIME-Version: 1.0
In-Reply-To: <87sg2l2ma2.fsf@bsb.me.uk>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Message-ID: <356dndvIucnMWT_9nZ2dnUU7-bmdnZ2d@giganews.com>
Lines: 43
X-Usenet-Provider: http://www.giganews.com
X-Trace: sv3-mB6f/iLSrD4y0QaHL0m8fHWxRAyjez8pZw8UhxWPsy/X5oAnAp6sIXvweaIaJvXfKULAAbperJhmFr4!Zt1sHkQJ4KVAocL61ldXOsU9OaORVmnmIhYpt4g9XY0hbbowR/CfRY5sPmUVntrNicWTmeqVQ9SB!MA==
X-Complaints-To: abuse@giganews.com
X-DMCA-Notifications: http://www.giganews.com/info/dmca.html
X-Abuse-and-DMCA-Info: Please be sure to forward a copy of ALL headers
X-Abuse-and-DMCA-Info: Otherwise we will be unable to process your complaint properly
X-Postfilter: 1.3.40
X-Original-Bytes: 3318
 by: olcott - Mon, 17 May 2021 19:31 UTC

On 5/17/2021 2:27 PM, Ben Bacarisse wrote:
> Malcolm McLean <malcolm.arthur.mclean@gmail.com> writes:
>
>> On Monday, 17 May 2021 at 12:26:33 UTC+1, Richard Damon wrote:
>>>
>>> If said claimed decider is improved to see the problem and stop it, now
>>> said decider may be able to answer in time, but, at least with your
>>> method, it can get the wrong answer because it doesn't get to see what
>>> the machine it is deciding on will do with that answer.
>>>
>>> Again, that is the problem with the design of that claimed decider, not
>>> the problem.
>>>
>> It's an inherent problem with all deciders. You can simulate until it
>> "looks stuck" and you might have a very good decider.
>
> You seem determined to encourage PO's misconceptions. PO assumes
> simulation is involved. No one else should.
>

None-the-less you cannot possibly provide any correct rebuttal because
none exists.

My current proof simply shows exactly how the exact Peter Linz H would
correctly decide not halting on the exact Peter Linz Ĥ.

This definition of halting circumvents the pathological self-reference
error for every simulating halt decider:

An input is decided to be halting only if its simulation never needs to
be stopped by any simulating halt decider anywhere in its entire
invocation chain.

On that basis:
Ĥ(<Ĥ>) ⊢* Ĥ.qn
H(<Ĥ>,<Ĥ>) ⊢* H.qn

--
Copyright 2021 Pete Olcott

"Great spirits have always encountered violent opposition from mediocre
minds." Einstein

Re: Infinitely Recursive input on HP Proofs

<87eee43mgf.fsf@bsb.me.uk>

  copy mid

https://www.novabbs.com/devel/article-flat.php?id=15686&group=comp.theory#15686

  copy link   Newsgroups: comp.theory
Path: i2pn2.org!i2pn.org!eternal-september.org!reader02.eternal-september.org!.POSTED!not-for-mail
From: ben.use...@bsb.me.uk (Ben Bacarisse)
Newsgroups: comp.theory
Subject: Re: Infinitely Recursive input on HP Proofs
Date: Tue, 18 May 2021 01:38:40 +0100
Organization: A noiseless patient Spider
Lines: 51
Message-ID: <87eee43mgf.fsf@bsb.me.uk>
References: <918df253-d4f0-4370-8f73-88e6690380a1@googlegroups.com>
<a4ydnWkMIKhS8Dz9nZ2dnUU7-L3NnZ2d@giganews.com>
<87im3i5t12.fsf@bsb.me.uk>
<0sCdnWsgz4JPGjz9nZ2dnUU7-RvNnZ2d@giganews.com>
<R%foI.542844$nn2.335922@fx48.iad>
<-rednavQTY_BDTz9nZ2dnUU7-SXNnZ2d@giganews.com>
<_yhoI.542847$nn2.449398@fx48.iad>
<EsCdnduL051HNTz9nZ2dnUU7-d_NnZ2d@giganews.com>
<HojoI.604824$%W6.542760@fx44.iad>
<daudnYwj2vzXUzz9nZ2dnUU7-XPNnZ2d@giganews.com>
<ngloI.149087$gq3.16218@fx04.iad>
<lO2dncjmT5ftfDz9nZ2dnUU7-IWdnZ2d@giganews.com>
<GpsoI.240833$PE7.20906@fx39.iad>
<15406379-420c-4c32-b713-be57e31901ban@googlegroups.com>
<87sg2l2ma2.fsf@bsb.me.uk>
<356dndvIucnMWT_9nZ2dnUU7-bmdnZ2d@giganews.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
Injection-Info: reader02.eternal-september.org; posting-host="96ba1fa8f20f5cf3885819b660d77fb9";
logging-data="23163"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1+4p8Gy8QsB6Jhu3tBNNXrHxXHQ1b7qXAM="
Cancel-Lock: sha1:PpwDmQV7U3ojZTB4XPtzWRqiiAQ=
sha1:Bjh0VHmnN2gZBM1sfMR1txMuJQw=
X-BSB-Auth: 1.0bd0bf1b39a1d175034c.20210518013840BST.87eee43mgf.fsf@bsb.me.uk
 by: Ben Bacarisse - Tue, 18 May 2021 00:38 UTC

olcott <NoOne@NoWhere.com> writes:

> On 5/17/2021 2:27 PM, Ben Bacarisse wrote:
>> Malcolm McLean <malcolm.arthur.mclean@gmail.com> writes:
>>
>>> On Monday, 17 May 2021 at 12:26:33 UTC+1, Richard Damon wrote:
>>>>
>>>> If said claimed decider is improved to see the problem and stop it, now
>>>> said decider may be able to answer in time, but, at least with your
>>>> method, it can get the wrong answer because it doesn't get to see what
>>>> the machine it is deciding on will do with that answer.
>>>>
>>>> Again, that is the problem with the design of that claimed decider, not
>>>> the problem.
>>>>
>>> It's an inherent problem with all deciders. You can simulate until it
>>> "looks stuck" and you might have a very good decider.
>>
>> You seem determined to encourage PO's misconceptions. PO assumes
>> simulation is involved. No one else should.
>
> None-the-less you cannot possibly provide any correct rebuttal because
> none exists.

There's nothing to rebut as far as I can see. You've defined a "new
kind if halting" which no one cares about. What you need is someone to
tell you to stop lying about it being halting. Is there no friend you
can turn to who will help you stay honest?

> My current proof simply shows exactly how the exact Peter Linz H would
> correctly decide not halting on the exact Peter Linz Ĥ.

Don't be silly. The rebuttal is in Linz.

> This definition of halting circumvents the pathological self-reference
> error for every simulating halt decider:

The definition is halting is already settled. You need a new name for
whatever property you think we should care about. Whatever you think
your mysterious and hidden Halts function decides, it is not halting.

> An input is decided to be halting only if its simulation never needs
> to be stopped by any simulating halt decider anywhere in its entire
> invocation chain.

However, an input /should/ be decided to be halting only if the sequence
of machine configurations it generates is finite. No one cares about
whatever it is you've decided to misname halting.

--
Ben.


devel / comp.theory / Re: Infinitely Recursive input on HP Proofs

Pages:12
server_pubkey.txt

rocksolid light 0.9.81
clearnet tor