comp.theory

Liste des Groupes Pages :12345678910111213141516171819202122232425262728293031323334
Date Sujet#  Auteur
14 Aug 24 i i   i       i   ii   ii       i   i i `* Re: Overview of proof that DDD specifies non-halting behavior --- point by point2joes
14 Aug 24 i i   i       i   ii   ii       i   i i  `- Re: Overview of proof that DDD specifies non-halting behavior --- point by point1olcott
14 Aug 24 i i   i       i   ii   ii       i   i `- Re: HHH maps its input to the behavior specified by it --- never reaches its halt state ---natural number mapping1Richard Damon
13 Aug 24 i i   i       i   ii   ii       i   +- Re: HHH maps its input to the behavior specified by it --- never reaches its halt state ---natural number mapping1Fred. Zwarts
14 Aug 24 i i   i       i   ii   ii       i   `- Re: HHH maps its input to the behavior specified by it --- never reaches its halt state ---natural number mapping1Richard Damon
13 Aug 24 i i   i       i   ii   ii       `* Re: HHH maps its input to the behavior specified by it --- never reaches its halt state ---natural number mapping10Mikko
13 Aug 24 i i   i       i   ii   ii        `* Re: HHH maps its input to the behavior specified by it --- never reaches its halt state ---natural number mapping9olcott
13 Aug 24 i i   i       i   ii   ii         +- Re: HHH maps its input to the behavior specified by it --- never reaches its halt state ---natural number mapping1Fred. Zwarts
14 Aug 24 i i   i       i   ii   ii         `* Re: HHH maps its input to the behavior specified by it --- never reaches its halt state ---natural number mapping7Mikko
14 Aug 24 i i   i       i   ii   ii          `* Re: HHH maps its input to the behavior specified by it --- never reaches its halt state ---6olcott
14 Aug 24 i i   i       i   ii   ii           +- Re: HHH maps its input to the behavior specified by it --- never reaches its halt state ---1Fred. Zwarts
14 Aug 24 i i   i       i   ii   ii           +- Re: HHH maps its input to the behavior specified by it --- never reaches its halt state1joes
15 Aug 24 i i   i       i   ii   ii           `* Re: HHH maps its input to the behavior specified by it --- never reaches its halt state ---3Mikko
15 Aug 24 i i   i       i   ii   ii            `* Re: HHH maps its input to the behavior specified by it --- never reaches its halt state ---2olcott
16 Aug 24 i i   i       i   ii   ii             `- Re: HHH maps its input to the behavior specified by it --- never reaches its halt state ---1Mikko
8 Aug 24 i i   i       i   ii   i`- Re: HHH maps its input to the behavior specified by it --- never reaches its halt state1Richard Damon
8 Aug 24 i i   i       i   ii   +* Re: HHH maps its input to the behavior specified by it --- never reaches its halt state2olcott
9 Aug 24 i i   i       i   ii   i`- Re: HHH maps its input to the behavior specified by it --- never reaches its halt state1Richard Damon
8 Aug 24 i i   i       i   ii   `* Re: HHH maps its input to the behavior specified by it --- never reaches its halt state2olcott
9 Aug 24 i i   i       i   ii    `- Re: HHH maps its input to the behavior specified by it --- never reaches its halt state1Richard Damon
8 Aug 24 i i   i       i   i`- Re: HHH maps its input to the behavior specified by it1Mikko
8 Aug 24 i i   i       i   `- Re: HHH computes the mapping from its input finite sting to the actual behavior specified by this finite string (Which is the results of running the input)1Richard Damon
7 Aug 24 i i   i       `* Re: Who knows that DDD correctly simulated by HHH cannot possibly reach its own return instruction final state?4Keith Thompson
7 Aug 24 i i   i        `* Re: Who knows that DDD correctly simulated by HHH cannot possibly reach its own return instruction final state?3olcott
7 Aug 24 i i   i         +- Re: Who knows that DDD correctly simulated by HHH cannot possibly reach its own return instruction final state?1Richard Damon
7 Aug 24 i i   i         `- Re: Who knows that DDD correctly simulated by HHH cannot possibly reach its own return instruction final state?1joes
4 Aug 24 i i   `- Re: Who here is too stupid to know that DDD correctly simulated by HHH cannot possibly reach its own return instruction?1Fred. Zwarts
3 Aug 24 i `- Re: Who here is too stupid to know that DDD correctly simulated by HHH cannot possibly reach its own return instruction?1Richard Damon
3 Aug 24 `* Re: Who here is too stupid to know that DDD correctly simulated by HHH cannot possibly reach its own return instruction?96Mikko
3 Aug 24  `* Re: Who here is too stupid to know that DDD correctly simulated by HHH cannot possibly reach its own return instruction?95olcott
3 Aug 24   +* Re: Who here is too stupid to know that DDD correctly simulated by HHH cannot possibly reach its own return instruction?83Fred. Zwarts
3 Aug 24   i`* Re: Who here is too stupid to know that DDD correctly simulated by HHH cannot possibly reach its own return instruction?82olcott
3 Aug 24   i `* Re: Who here is too stupid to know that DDD correctly simulated by HHH cannot possibly reach its own return instruction?81Fred. Zwarts
3 Aug 24   i  `* Re: Who here is too stupid to know that DDD correctly simulated by HHH cannot possibly reach its own return instruction?80olcott
4 Aug 24   i   `* Re: Who here is too stupid to know that DDD correctly simulated by HHH cannot possibly reach its own return instruction?79Fred. Zwarts
4 Aug 24   i    `* Re: Who here is too stupid to know that DDD correctly simulated by HHH cannot possibly reach its own return instruction?78olcott
4 Aug 24   i     +* Re: Who here is too stupid to know that DDD correctly simulated by HHH cannot possibly reach its own return instruction?6Richard Damon
4 Aug 24   i     i`* Re: Who here is too stupid to know that DDD correctly simulated by HHH cannot possibly reach its own return instruction?5olcott
4 Aug 24   i     i +- Re: Who here is too stupid to know that DDD correctly simulated by HHH cannot possibly reach its own return instruction?1Richard Damon
7 Aug 24   i     i `* Re: Who here is too stupid to know that DDD correctly simulated by HHH cannot possibly reach its own return instruction?3Fred. Zwarts
7 Aug 24   i     i  `* Re: Who here is too stupid to know that DDD correctly simulated by HHH cannot possibly reach its own return instruction?2olcott
8 Aug 24   i     i   `- Re: Who here is too stupid to know that DDD correctly simulated by HHH cannot possibly reach its own return instruction?1Mikko
5 Aug 24   i     +* Re: Who here is too stupid to know that DDD correctly simulated by HHH cannot possibly reach its own return instruction?15Mikko
5 Aug 24   i     i`* Re: Who here is too stupid to know that DDD correctly simulated by HHH cannot possibly reach its own return instruction?14olcott
7 Aug 24   i     i `* Re: Who here is too stupid to know that DDD correctly simulated by HHH cannot possibly reach its own return instruction?13Mikko
7 Aug 24   i     i  `* Re: Who here is too stupid to know that DDD correctly simulated by HHH cannot possibly reach its own return instruction?12olcott
7 Aug 24   i     i   +* Re: Who here is too stupid to know that DDD correctly simulated by HHH cannot possibly reach its own return instruction?4Python
7 Aug 24   i     i   i+* Re: Who here is too stupid to know that DDD correctly simulated by HHH cannot possibly reach its own return instruction?2olcott
8 Aug 24   i     i   ii`- Re: Who here is too stupid to know that DDD correctly simulated by HHH cannot possibly reach its own return instruction?1Richard Damon
8 Aug 24   i     i   i`- Re: Who here is too stupid to know that DDD correctly simulated by HHH cannot possibly reach its own return instruction?1Mikko
7 Aug 24   i     i   `* Re: Who here is too stupid to know that DDD simulated by HHH cannot reach its own return?7joes
7 Aug 24   i     i    `* Re: Who here is too stupid to know that DDD simulated by HHH cannot reach its own return?6olcott
7 Aug 24   i     i     +* Re: Who here is too stupid to know that DDD simulated by HHH cannot reach its own return? (typos fixed)3olcott
8 Aug 24   i     i     i+- Re: Who here is too stupid to know that DDD simulated by HHH cannot reach its own return? (typos fixed)1Richard Damon
8 Aug 24   i     i     i`- Re: Who here is too stupid to know that DDD simulated by HHH cannot reach its own return? (typos fixed)1Mikko
8 Aug 24   i     i     +- Re: Who here is too stupid to know that DDD simulated by HHH cannot reach its own return?1Richard Damon
8 Aug 24   i     i     `- Re: Who here is too stupid to know that DDD simulated by HHH cannot reach its own return?1Mikko
7 Aug 24   i     `* Re: Who here is too stupid to know that DDD correctly simulated by HHH cannot possibly reach its own return instruction?56Fred. Zwarts
7 Aug 24   i      `* Re: Who here is too stupid to know that DDD correctly simulated by HHH cannot possibly reach its own return instruction?55olcott
8 Aug 24   i       +- Re: Who here is too stupid to know that DDD correctly simulated by HHH cannot possibly reach its own return instruction?1Richard Damon
8 Aug 24   i       `* Re: Who here is too stupid to know that DDD correctly simulated by HHH cannot possibly reach its own return instruction?53Fred. Zwarts
8 Aug 24   i        `* HHH maps its input to the behavior specified by it --- never reaches its halt state52olcott
8 Aug 24   i         +* Re: HHH maps its input to the behavior specified by it --- never reaches its halt state13Fred. Zwarts
8 Aug 24   i         i`* Re: HHH maps its input to the behavior specified by it --- never reaches its halt state12olcott
8 Aug 24   i         i `* Re: HHH maps its input to the behavior specified by it --- never reaches its halt state11Fred. Zwarts
8 Aug 24   i         i  `* Re: HHH maps its input to the behavior specified by it --- never reaches its halt state10olcott
9 Aug 24   i         i   `* Re: HHH maps its input to the behavior specified by it --- never reaches its halt state9Fred. Zwarts
9 Aug 24   i         i    `* Re: HHH maps its input to the behavior specified by it --- never reaches its halt state8olcott
9 Aug 24   i         i     `* Re: HHH maps its input to the behavior specified by it --- never reaches its halt state7Fred. Zwarts
9 Aug 24   i         i      `* Re: HHH maps its input to the behavior specified by it --- never reaches its halt state6olcott
9 Aug 24   i         i       +* Re: HHH maps its input to the behavior specified by it --- never reaches its halt state4Fred. Zwarts
9 Aug 24   i         i       i`* Re: HHH maps its input to the behavior specified by it --- never reaches its halt state3olcott
10 Aug 24   i         i       i +- Re: HHH maps its input to the behavior specified by it --- partial simulation never reaches its halt state, but the actual behavior of the actual program does1Richard Damon
10 Aug 24   i         i       i `- Re: HHH maps its input to the behavior specified by it --- never reaches its halt state1Fred. Zwarts
10 Aug 24   i         i       `- Re: HHH maps its input to the behavior specified by it --- partial simulation never reaches its halt state, but the program does.1Richard Damon
9 Aug 24   i         `* Re: HHH maps its input to the behavior specified by it --- never reaches its halt state38Richard Damon
9 Aug 24   i          `* Re: HHH maps its input to the behavior specified by it --- never reaches its halt state ---37olcott
9 Aug 24   i           +* Re: HHH maps its input to the behavior specified by it --- never reaches its halt state ---22Richard Damon
9 Aug 24   i           i+* Re: HHH maps its input to the behavior specified by it --- never reaches its halt state ---19olcott
9 Aug 24   i           ii`* Re: HHH maps its input to the behavior specified by it --- never reaches its halt state ---18Richard Damon
9 Aug 24   i           ii `* Re: HHH maps its input to the behavior specified by it --- never reaches its halt state ---17olcott
9 Aug 24   i           ii  `* Re: HHH maps its input to the behavior specified by it --- reaches its halt state ---16Richard Damon
9 Aug 24   i           ii   `* Re: HHH maps its input to the behavior specified by it --- reaches its halt state ---15olcott
10 Aug 24   i           ii    `* Re: HHH maps its input to the behavior specified by it --- reaches its halt state --- Which DDD does if HHH(DDD) returns and answer, which it does since it is a decider.14Richard Damon
10 Aug 24   i           ii     `* Re: HHH maps its input to the behavior specified by it --- reaches its halt state --- Which DDD does if HHH(DDD) returns and answer, which it does since it is a decider.13olcott
10 Aug 24   i           ii      `* Re: HHH maps its input to the behavior specified by it --- reaches its halt state --- Which DDD does if HHH(DDD) returns and answer, which it does since it is a decider.12Richard Damon
10 Aug 24   i           ii       `* Re: HHH maps its input to the behavior specified by it --- reaches its halt state --- Which DDD does if HHH(DDD) returns and answer, which it does since it is a decider.11olcott
10 Aug 24   i           ii        `* Re: HHH maps its input to the behavior specified by it --- reaches its halt state --- Which DDD does if HHH(DDD) returns and answer, which it does since it is a decider.10Richard Damon
10 Aug 24   i           ii         `* Re: HHH maps its input to the behavior specified by it --- reaches its halt state --- Which DDD does if HHH(DDD) returns and answer, which it does since it is a decider.9olcott
10 Aug 24   i           ii          `* Re: HHH maps its input to the behavior specified by it --- reaches its halt state --- Which DDD does if HHH(DDD) returns and answer, which it does since it is a decider.8Richard Damon
10 Aug 24   i           ii           `* Re: HHH maps its input to the behavior specified by it --- reaches its halt state --- Which DDD does if HHH(DDD) returns and answer, which it does since it is a decider.7olcott
10 Aug 24   i           ii            +* Re: HHH maps its input to the behavior specified by it --- reaches its halt state --- Which DDD does if HHH(DDD) returns and answer, which it does since it is a decider.5Richard Damon
10 Aug 24   i           ii            i`* Re: HHH maps its input to the behavior specified by it --- reaches its halt state --- Which DDD does if HHH(DDD) returns and answer, which it does since it is a decider.4olcott
10 Aug 24   i           ii            i `* Re: HHH maps its input to the behavior specified by it --- reaches its halt state --- Which DDD does if HHH(DDD) returns and answer, which it does since it is a decider.3Richard Damon
10 Aug 24   i           ii            i  `* Re: HHH maps its input to the behavior specified by it --- reaches its halt state --- Which DDD does if HHH(DDD) returns and answer, which it does since it is a decider.2olcott
10 Aug 24   i           ii            i   `- Re: HHH maps its input to the behavior specified by it --- reaches its halt state --- Which DDD does if HHH(DDD) returns and answer, which it does since it is a decider.1Richard Damon
10 Aug 24   i           ii            `- Re: HHH maps its input to the behavior specified by it --- reaches its halt state --- Which DDD does if HHH(DDD) returns and answer, which it does since it is a decider.1Mikko
9 Aug 24   i           i`* Re: HHH maps its input to the behavior specified by it --- never reaches its halt state ---2olcott
10 Aug 24   i           i `- Re: HHH maps its input to the behavior specified by it --- partial simulation never reaches its halt state, but the actual behavior of the actual program does1Richard Damon
9 Aug 24   i           `* Re: HHH maps its input to the behavior specified by it --- never reaches its halt state ---14Fred. Zwarts
9 Aug 24   i            `* Re: HHH maps its input to the behavior specified by it --- never reaches its halt state ---13olcott
9 Aug 24   i             `* Re: HHH maps its input to the behavior specified by it --- never reaches its halt state ---12Fred. Zwarts
9 Aug 24   i              `* Re: HHH maps its input to the behavior specified by it --- never reaches its halt state ---11olcott
9 Aug 24   i               `* Re: HHH maps its input to the behavior specified by it --- never reaches its halt state ---10Fred. Zwarts
9 Aug 24   i                `* Re: HHH maps its input to the behavior specified by it --- never reaches its halt state ---9olcott
10 Aug 24   i                 `* Re: HHH maps its input to the behavior specified by it --- never reaches its halt state ---8Fred. Zwarts
10 Aug 24   i                  `* Re: HHH maps its input to the behavior specified by it --- never reaches its halt state ---7olcott
10 Aug 24   i                   +* Re: HHH maps its input to the behavior specified by it --- never reaches its halt state ---3Richard Damon
10 Aug 24   i                   i`* Re: HHH maps its input to the behavior specified by it --- never reaches its halt state ---2olcott
10 Aug 24   i                   i `- Re: HHH maps its input to the behavior specified by it --- partial simulation never reaches its halt state --- but full simulaition does.1Richard Damon
10 Aug 24   i                   `* Re: HHH maps its input to the behavior specified by it --- never reaches its halt state ---3Fred. Zwarts
10 Aug 24   i                    `* Re: HHH maps its input to the behavior specified by it --- never reaches its halt state ---2olcott
10 Aug 24   i                     `- Re: HHH maps its input to the behavior specified by it --- never reaches its halt state ---1Fred. Zwarts
4 Aug 24   `* Re: Who here is too stupid to know that DDD correctly simulated by HHH cannot possibly reach its own return instruction?11Mikko
4 Aug 24    `* Re: Who here is too stupid to know that DDD correctly simulated by HHH cannot possibly reach its own return instruction?10olcott
5 Aug 24     `* Re: Who here is too stupid to know that DDD correctly simulated by HHH cannot possibly reach its own return instruction?9Mikko
5 Aug 24      `* Re: Who here is too stupid to know that DDD correctly simulated by HHH cannot possibly reach its own return instruction?8olcott
7 Aug 24       `* Re: Who here is too stupid to know that DDD correctly simulated by HHH cannot possibly reach its own return instruction?7Mikko
7 Aug 24        `* Re: Who here is too stupid to know that DDD correctly simulated by HHH cannot possibly reach its own return instruction?6olcott
8 Aug 24         `* Re: Who here is too stupid to know that DDD correctly simulated by HHH cannot possibly reach its own return instruction?5Mikko
8 Aug 24          `* HHH maps its input to the behavior specified by it --- never reaches its halt state4olcott
9 Aug 24           `* Re: HHH maps its input to the behavior specified by it --- never reaches its halt state3Mikko
9 Aug 24            `* Re: HHH maps its input to the behavior specified by it --- never reaches its halt state2olcott
10 Aug 24             `- Re: HHH maps its input to the behavior specified by it --- never reaches its halt state1Mikko
13 Aug 24 * Overview of proof that the input to HHH(DDD) specifies non-halting behavior29olcott
13 Aug 24 +- Re: Overview of proof that the input to HHH(DDD) specifies non-halting behavior1Python
13 Aug 24 +- Re: Overview of proof that the input to HHH(DDD) specifies non-halting behavior1Richard Damon
13 Aug 24 +* Re: Overview of proof that the input to HHH(DDD) specifies non-halting behavior23Mikko
13 Aug 24 i`* Re: Overview of proof that the input to HHH(DDD) specifies non-halting behavior --- Mike22olcott
13 Aug 24 i +* Re: Overview of proof that the input to HHH(DDD) specifies non-halting behavior --- Mike15Fred. Zwarts
13 Aug 24 i i`* Re: Overview of proof that the input to HHH(DDD) specifies non-halting behavior --- Mike --- point by point14olcott
13 Aug 24 i i +* Re: Overview of proof that the input to HHH(DDD) specifies non-halting behavior --- Mike --- point by point12Fred. Zwarts
13 Aug 24 i i i`* Re: Overview of proof that the input to HHH(DDD) specifies non-halting behavior --- Mike --- point by point11olcott
13 Aug 24 i i i +* Re: Overview of proof that the input to HHH(DDD) specifies non-halting behavior --- Mike --- point by point9Fred. Zwarts
13 Aug 24 i i i i`* Re: Overview of proof that the input to HHH(DDD) specifies non-halting behavior --- Mike --- point by point8olcott
13 Aug 24 i i i i +* Re: Overview of proof that the input to HHH(DDD) specifies non-halting behavior --- Mike --- point by point6Fred. Zwarts
13 Aug 24 i i i i i`* Re: Overview of proof that the input to HHH(DDD) specifies non-halting behavior --- Mike --- point by point5olcott
14 Aug 24 i i i i i +- Re: Overview of proof that the input to HHH(DDD) specifies non-halting behavior --- Mike --- point by point1Richard Damon
14 Aug 24 i i i i i `* Re: Overview of proof that the input to HHH(DDD) specifies non-halting behavior --- Mike --- point by point3Fred. Zwarts
14 Aug 24 i i i i i  `* Re: Overview of proof that the input to HHH(DDD) specifies non-halting behavior --- Mike --- in our head2olcott
14 Aug 24 i i i i i   `- Re: Overview of proof that the input to HHH(DDD) specifies non-halting behavior --- Mike --- in our head1Fred. Zwarts
14 Aug 24 i i i i `- Re: Overview of proof that the input to HHH(DDD) specifies non-halting behavior --- Mike --- point by point1Richard Damon
14 Aug 24 i i i `- Re: Overview of proof that the input to HHH(DDD) specifies non-halting behavior --- Mike --- point by point1Richard Damon
14 Aug 24 i i `- Re: Overview of proof that the input to HHH(DDD) specifies non-halting behavior --- Mike --- point by point1Richard Damon
14 Aug 24 i `* Re: Overview of proof that the input to HHH(DDD) specifies non-halting behavior --- Mike6Mikko
14 Aug 24 i  `* Re: Overview of proof that the input to HHH(DDD) specifies non-halting behavior --- Mike5olcott
14 Aug 24 i   +- Re: Overview of proof that the input to HHH(DDD) specifies non-halting behavior --- Mike1Fred. Zwarts
15 Aug 24 i   `* Re: Overview of proof that the input to HHH(DDD) specifies non-halting behavior --- Mike3Mikko
15 Aug 24 i    `* Re: Overview of proof that the input to HHH(DDD) specifies non-halting behavior --- Mike2olcott
16 Aug 24 i     `- Re: Overview of proof that the input to HHH(DDD) specifies non-halting behavior --- Mike1Mikko
13 Aug 24 `* Re: Overview of proof that the input to HHH(DDD) specifies non-halting behavior3olcott
14 Aug 24  +- Re: Overview of proof that the input to HHH(DDD) specifies non-halting behavior1Richard Damon
14 Aug 24  `- Re: Overview of proof that the input to HHH(DDD) specifies non-halting behavior1Richard Damon
4 Aug 24 * Defining a correct halt decider67olcott
4 Aug 24 +* Re: Defining a correct halt decider45Richard Damon
4 Aug 24 i`* Re: Defining a correct halting decidability decider44olcott
4 Aug 24 i `* Re: Defining a correct halting decidability decider43Richard Damon
4 Aug 24 i  `* Re: Defining a correct halting decidability decider42olcott
4 Aug 24 i   +* Re: Defining a correct halting decidability decider20Richard Damon
4 Aug 24 i   i`* Re: Defining a correct halting decidability decider19olcott
4 Aug 24 i   i `* Re: Defining a correct halting decidability decider18Richard Damon
4 Aug 24 i   i  `* Re: Defining a correct halting decidability decider17olcott
5 Aug 24 i   i   `* Re: Defining a correct halting decidability decider16Richard Damon
5 Aug 24 i   i    `* Re: Defining a correct halting decidability decider15olcott
5 Aug 24 i   i     `* Re: Defining a correct halting decidability decider14Richard Damon
5 Aug 24 i   i      `* Re: Defining a correct halting decidability decider13olcott
5 Aug 24 i   i       `* Re: Defining a correct halting decidability decider12Richard Damon
5 Aug 24 i   i        `* Re: Defining a correct halting decidability decider11olcott
5 Aug 24 i   i         `* Re: Defining a correct halting decidability decider10Richard Damon
5 Aug 24 i   i          `* You still seem too dishonest to admit that DDD correctly emulated by any HHH cannot possibly reach its own ,"return" instruction9olcott
5 Aug 24 i   i           `* Re: You still seem too dishonest to admit that DDD correctly emulated by any HHH cannot possibly reach its own ,"return" instruction8Richard Damon
5 Aug 24 i   i            `* Re: You still seem too dishonest to admit that DDD correctly emulated by any HHH cannot possibly reach its own ,"return" instruction7olcott
5 Aug 24 i   i             `* Re: You still seem too dishonest to admit that DDD correctly emulated by any HHH cannot possibly reach its own ,"return" instruction6Richard Damon
5 Aug 24 i   i              `* Re: You still seem too dishonest to admit that DDD correctly emulated by any HHH cannot possibly reach its own ,"return" instruction5olcott
5 Aug 24 i   i               `* Re: You still seem too dishonest to admit that DDD correctly emulated by any HHH cannot possibly reach its own ,"return" instruction4Richard Damon
5 Aug 24 i   i                `* Re: You still seem too dishonest to admit that DDD correctly emulated by any HHH cannot possibly reach its own ,"return" instruction3wij
5 Aug 24 i   i                 `* Re: You still seem too dishonest to admit that DDD correctly emulated by any HHH cannot possibly reach its own ,"return" instruction2olcott
6 Aug 24 i   i                  `- Re: Olcott still seems too dishonest to admit that his HHH doesn't correctly emulate DDD1Richard Damon
7 Aug 24 i   `* Re: Defining a correct halting decidability decider21Mikko
7 Aug 24 i    `* Re: Defining a correct halting decidability decider20olcott
8 Aug 24 i     +- Re: Defining a correct halting decidability decider (Which isn't a valid criteria for a decider)1Richard Damon
8 Aug 24 i     `* Re: Defining a correct halting decidability decider18Mikko
8 Aug 24 i      `* Re: Defining a correct halting decidability decider17olcott
8 Aug 24 i       +* Re: Defining a correct halting decidability decider4Python
8 Aug 24 i       i`* Re: Defining a correct halting decidability decider3olcott
9 Aug 24 i       i +- Re: Defining a correct halting decidability decider1Richard Damon
9 Aug 24 i       i `- Re: Defining a correct halting decidability decider1Python
9 Aug 24 i       +- Re: Defining a correct halting decidability decider1Richard Damon
9 Aug 24 i       `* Re: Defining a correct halting decidability decider11Mikko
9 Aug 24 i        `* Re: Defining a correct halting decidability decider10olcott
10 Aug 24 i         +- Re: Defining a correct halting decidability decider1Richard Damon
10 Aug 24 i         `* Re: Defining a correct halting decidability decider8Mikko
10 Aug 24 i          `* Re: Defining a correct halting decidability decider7olcott
10 Aug 24 i           +* Re: Defining a correct halting decidability decider3Richard Damon
10 Aug 24 i           i`* Re: Defining a correct halting decidability decider2olcott
10 Aug 24 i           i `- Re: Defining a correct halting decidability decider1Richard Damon
11 Aug 24 i           `* Re: Defining a correct halting decidability decider3Mikko
11 Aug 24 i            `* Re: Defining a correct halting decidability decider2olcott
11 Aug 24 i             `- Re: Defining a correct halting decidability decider1Richard Damon
5 Aug 24 `* Re: Defining a correct halt decider21Mikko
5 Aug 24  `* I call it a halting decidability decider20olcott
5 Aug 24   +* Re: I call it a halting decidability decider14Python
5 Aug 24   i`* Re: I call it a halting decidability decider13olcott
6 Aug 24   i +* Re: I call it a halting decidability decider, and thus isn't actually a computability decider.5Richard Damon
6 Aug 24   i i`* Re: I call it a halting decidability decider, and thus isn't actually a computability decider.4olcott
6 Aug 24   i i `* Re: I call it a halting decidability decider, and thus isn't actually a computability decider.3Richard Damon
6 Aug 24   i i  `* Re: I call it a halting decidability decider, and thus isn't actually a computability decider.2olcott
6 Aug 24   i i   `- Re: I call it a halting decidability decider, and thus isn't actually a computability decider.1Richard Damon
7 Aug 24   i `* Re: I call it a halting decidability decider7Mikko
7 Aug 24   i  `* HHH decides a non-trivial semantic property of its input6olcott
8 Aug 24   i   +- Re: HHH decides a trivial semantic non-property of its input1Richard Damon
8 Aug 24   i   +* Re: HHH decides a non-trivial semantic property of its input3Mikko
8 Aug 24   i   i`* Re: HHH decides a non-trivial semantic property of its input2olcott
9 Aug 24   i   i `- Re: HHH decides a non-trivial semantic property of its input1Richard Damon
8 Aug 24   i   `- Re: HHH decides a trivial non-semantic non-property of its input1Richard Damon
6 Aug 24   +- Re: I call it a halting decidability decider, and thus doesn't say anything about the halting problem1Richard Damon
7 Aug 24   `* Re: I call it a halting decidability decider4Mikko
7 Aug 24    `* Re: I call it a halting decidability decider3olcott
8 Aug 24     +- Re: I call it a halting decidability decider1Richard Damon
8 Aug 24     `- Re: I call it a halting decidability decider1Mikko
5 Aug 24 * Is everyone here faking that they know anything about the x86 language?8olcott
6 Aug 24 +- Re: Is everyone here faking that they know anything about the x86 language? Peter Olcott sure is,1Richard Damon
7 Aug 24 `* Re: Is everyone here faking that they know anything about the x86 language?6Mikko
7 Aug 24  `* Re: Is everyone here faking that they know anything about the x86 language?5olcott
8 Aug 24   +- Re: Is everyone here faking that they know anything about the x86 language?1Richard Damon
8 Aug 24   `* Re: Is everyone here faking that they know anything about the x86 language?3Mikko
8 Aug 24    `* HHH maps its input to the behavior specified by it --- never reaches its halt state2olcott
9 Aug 24     `- Re: HHH maps its input to the behavior specified by it --- never reaches its halt state1Richard Damon
6 Aug 24 * Latest revision of my paper incorporating feedback --- last remaining sticking point26olcott
6 Aug 24 +* Re: behaviour and description18joes
6 Aug 24 i`* Re: behaviour and description17olcott
7 Aug 24 i `* Re: behaviour and description16Richard Damon
7 Aug 24 i  `* Re: behaviour and description --- Trust Mike?15olcott
7 Aug 24 i   `* Re: behaviour and description --- Lying Peter14Richard Damon
7 Aug 24 i    +* Re: behaviour and description --- Lying Peter2olcott
7 Aug 24 i    i`- Re: behaviour and description --- Lying Peter1Richard Damon
7 Aug 24 i    +* Re: behavior and description --- All Rebuttals have been pure bluster2olcott
7 Aug 24 i    i`- Re: behavior and description --- Peter Olcott's Rebuttals have been pure bluster1Richard Damon
7 Aug 24 i    `* Re: behavior and description --- All rebuttals have been pure bluster V39olcott
7 Aug 24 i     `* Re: behavior and description --- Peter Olcott's rebuttals have been pure bluster V38Richard Damon
7 Aug 24 i      `* Re: behavior and description --- Rebuttals have been pure bluster V37olcott
7 Aug 24 i       `* Re: behavior and description --- Peter Olcott's Rebuttals have been pure bluster V36Richard Damon
7 Aug 24 i        `* Re: behavior and description --- Richard still only has pure bluster5olcott
7 Aug 24 i         +* Re: behavior and description --- Peter still only has pure bluster and lies3Richard Damon
7 Aug 24 i         i`* Re: behavior and description --- All of the code is here it is just hard to find2olcott
8 Aug 24 i         i `- Re: behavior and description --- All of the code is here it is just hard to find (No its not, no HHH given)1Richard Damon
8 Aug 24 i         `- Re: behavior and description --- Richard still only has pure bluster1Mikko
7 Aug 24 +- Re: Latest revision of my paper incorporating feedback --- last remaining sticking point FAILED.1Richard Damon
7 Aug 24 +* Re: Latest revision of my paper incorporating feedback --- last remaining sticking point3Mikko
7 Aug 24 i`* Re: Latest revision of my paper incorporating feedback --- last remaining sticking point2olcott

Haut de la page

Les messages affichés proviennent d'usenet.

NewsPortal