Re: What. A. Slog.

Liste des GroupesRevenir à theory 
Sujet : Re: What. A. Slog.
De : news.dead.person.stones (at) *nospam* darjeeling.plus.com (Mike Terry)
Groupes : comp.theory
Date : 14. May 2025, 20:06:08
Autres entêtes
Organisation : A noiseless patient Spider
Message-ID : <1002pj0$2ldvf$1@dont-email.me>
References : 1 2
User-Agent : Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101 Firefox/91.0 SeaMonkey/2.53.18.2
On 14/05/2025 18:50, Mike Terry wrote:
On 14/05/2025 08:11, vallor wrote:
Spent a couple of hours reading back the last few days of posts.  Huboy,
what a train wreck.  (But like a train wreck, it's hard to look
away, which might explain how this has been going on for 20(?) years.)
>
I want to thank both Richard's, wij, dbush, Mike, Keith, Fred,
Mikko, and anybody else I've forgotten for trying to explain to
Mr. Olcott and Mr. Flibble how you all see their claims.  I wanted to
point out three things:
>
a) Mr. Olcott claims his HHH simulator detects an non-terminating
input and halts.  But others (I forget who) report that -- due
to a bug -- D would actually terminate on its own.  His HHH
simulator therefore gives the wrong answer.
 Not really due to a bug.  D actually /does/ terminate on its own, and that's a consequence of PO's intended design.  (Yes, there are bugs, but D's coding is what PO intended.)
 
Hmm, I thought some more about this.  What's considered a bug (rather than e.g. a design error) is entirely dependent on the program's specification.  It seems perfectly reasonable to say the spec. for HHH is to decide whether the computation represented by its input halts.  That's the HP specification, and PO is discussing halt deciders (or perhaps a "partial halt decider" but the spec covering input DD will be the same).
Accepting that specification, PO's HHH deviates from spec. when given input DD, so that can be filed under "bug".  The source of the misbehaviour is not the simulation code, but rather one of the specific tests HHH applies for non-halting, viz PO's "infinite recursive emulation" test.  That test is unsound, so we've found the bug!  The problem is there's no alternative test it can be changed to in order to fix the bug.  And it is the test which PO thought up many years ago, and probably sent him down the whole HP proof refutation path...
If this test were simply deleted from HHH to give a new HHH2, then HHH2 processing HHH2's corresponding new DD2 would never return, but that is also a violation of the HP spec, so there must still be some bug in the new HHH2, right?  PO might reason that to fix the "non-halting" bug he HAS TO introduce his unsound non-halting test (or similar), AND SO THE NON-HALTING TEST IS CORRECT. That's nonsense of course and PO has been told.
We might say "HHH2 never halts, due to a bug", and that seems technically correct as above, but then like the original HHH "bug" there's still no conceivable fix for it.
In the end, the HP spec cannot logically be satisfied (as shown by Linz proof), so /any/ claim to meet that spec is sure to "contain a bug".  I'm not sure whether that's a good use for the term "bug"...
Mike.

Date Sujet#  Auteur
14 May 25 * What. A. Slog.24vallor
14 May 25 +* Re: What. A. Slog.2olcott
15 May 25 i`- Re: What. A. Slog.1Richard Damon
14 May 25 +* Re: What. A. Slog.20Mike Terry
14 May 25 i+* The exact words of this spec are met2olcott
15 May 25 ii`- Re: The exact words of this spec are met1Richard Damon
14 May 25 i`* Re: What. A. Slog.17Mike Terry
14 May 25 i `* HHH(DDD) correctly determines the halt status of its input according to this specification16olcott
14 May 25 i  +* Re: HHH(DDD) correctly determines the halt status of its input according to this specification7dbush
14 May 25 i  i+- Re: HHH(DDD) correctly determines the halt status of its input according to this specification1olcott
14 May 25 i  i`* Re: HHH(DDD) correctly determines the halt status of its input according to this specification5olcott
14 May 25 i  i +- Re: HHH(DDD) correctly determines the halt status of its input according to this specification1dbush
15 May 25 i  i `* Re: HHH(DDD) correctly determines the halt status of its input according to this specification3Mikko
16 May 25 i  i  `* Re: HHH(DDD) correctly determines the halt status of its input according to this specification2olcott
16 May 25 i  i   `- Re: HHH(DDD) correctly determines the halt status of its input according to this specification1Mikko
15 May 25 i  `* Re: HHH(DDD) correctly determines the halt status of its input according to this specification8Richard Damon
15 May 25 i   `* Re: HHH(DDD) correctly determines the halt status of its input according to this specification7olcott
15 May 25 i    +* Re: HHH(DDD) correctly determines the halt status of its input according to this specification5Richard Damon
15 May 25 i    i`* Re: HHH(DDD) correctly determines the halt status of its input according to this specification4olcott
15 May 25 i    i +* Re: HHH(DDD) correctly determines the halt status of its input according to this specification2Fred. Zwarts
16 May 25 i    i i`- Re: HHH(DDD) correctly determines the halt status of its input according to this specification1Mikko
15 May 25 i    i `- Re: HHH(DDD) correctly determines the halt status of its input according to this specification1Richard Damon
15 May 25 i    `- Re: HHH(DDD) correctly determines the halt status of its input according to this specification1Richard Heathfield
15 May 25 `- Re: What. A. Slog.1Mikko

Haut de la page

Les messages affichés proviennent d'usenet.

NewsPortal