Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
| Subject | Re: Architectural design of a halting problem solution [ Bill the auto mechanic can fix your car ] |
|---|---|
| Newsgroups | comp.theory, comp.ai.philosophy |
| References | (18 earlier) <xZonH.387442$I15.245423@fx36.iad> <6MCdneBt6cJmtQPCnZ2dnUU7-LednZ2d@giganews.com> <HBynH.435717$%p.348448@fx33.iad> <x6SdnZwKP6BfVQPCnZ2dnUU7-c_NnZ2d@giganews.com> <dIqdna5UecSgQwPCnZ2dnUU78V_NnZ2d@brightview.co.uk> |
| From | olcott <NoOne@NoWhere.com> |
| Date | 2020-11-01 12:18 -0600 |
| Message-ID | <0e-dnRdIEbOYYQPCnZ2dnUU7-RnNnZ2d@giganews.com> (permalink) |
Cross-posted to 2 groups.
On 11/1/2020 10:11 AM, Mike Terry wrote:
> On 01/11/2020 14:40, olcott wrote:
>> On 11/1/2020 7:19 AM, Richard Damon wrote:
>>> On 10/31/20 11:18 PM, olcott wrote:
>>>>
>>>> It is apparently over your head that the above code specifies three
>>>> different instances of H_Hat and that
>>>> Aborted_Because_Non_Halting_Behavior_Detected(P, P) does correctly
>>>> decide one of these three different instances.
>>>
>>> You seem to be unaware that H_Hat is a Turing machine, and as such there
>>> is but one definition of it.
>>
>> It can have one Turing Machine description that is executed multiple
>> times by a master Turing machine. Each of these instances can have
>> different amounts of data on their local tape.
>>
>> So it is exactly the same thing as three different instances of H_Hat
>> each in their own local process context.
>>
>>> There is one embodiment of it as an actual machine in the probem, and
>>> multiple copies of a representation of it, suitable for H to process.
>>
>> If we think of all of the machines involved as Turing Machine
>> descriptions of UTMs that are executed by a single master UTM then we
>> can get rid of the tedious dichotomy of a machine and its description
>> and simply talk about machines that can execute other machines.
>>
>> In m y x86utm operting system the machine description language is x86
>> and it is always directly executable.
>>
>>> For a given input, H_Hat will always produce the same result, that is a
>>> fundamental property of Turing Machines.
>>
>> Yet with three different instances of the same machine each one having a
>> longer execution trace the outermost invocation has the data required
>> to make its halting decision first. As soon as it terminates its
>> subordinate the entire process chain stops running.
>
> The calculation H-Hat(H_Hat) as you have described it elsewhere halts
> (in some finite number of steps it reaches a halt state - you haven't
> denied this, bearing in mind we're talking of the HP/Linz defined term
> "halts").
int main()
{
H_Hat(H_Hat)
invokes Aborted_Because_Non_Halting_Behavior_Detected(H_Hat, H_Hat);
which correctly decides that its first parameter would never halt unless
its execution is terminated.
Everything else that you say is moot until you first understand the
details related to what I just said prove that what I just said is true.
> Let's imagine, just for illustrative purposes, that it halts in 10000
> steps. That's to say, 10000 /specific/ steps, each one consisting of
> one specific program state (current instruction within the program)
> together with its data state. We could write all these down exactly, if
> we could be bothered, and had a big enough notebook! The final step
> 10000 is of course the calculation's halt state.
>
> EVERY ONE OF YOUR EMULATIONS OF H_HAT ARE SIMPLY IN THE PROCESS OF
> ENUMERATING THE 10000 STATES OF THIS ONE SINGLE CALCULATION.
>
> The only difference between them is that at a given point in the (outer)
> H_Hat or H calculation, they will each have enumerated a different
> number of these steps. Maybe the outer one has enumerated the first
> 7000 steps out of the total 10000, while an inner one has only
> enumerated 2000 of the same 10000 states, or whatever.
>
> At this point, let's say the outer emulation process decides to stop
> emulating for whatever reason - its seen enough! So the emulation only
> ever enumerates 7000 of the 10000 steps. (Inner emulations enumerate
> less.)
>
> If you want to say that all the emulations had "different results" then
> all you're saying is that each proceeded for a different number of steps
> along one and the same calculation (which contains 10000 steps and then
> halts, however you try to confuse things).
>
>>
>>> If your 'UTM' gets a different answer when simulating the machine, then
>>> that is positive evidence that your UTM has a bug. The answer H gives
>>
>> Three identical function with different amounts of data can and do
>> derive different results.
>
> You mean, each emulation can be abandonned after enumerating a different
> number of steps before its emulator gives up. (The underlying
> calculation they are enumerating in each case is the same. In our
> illustration it is a calculation with 10000 steps, the last being the
> halt state for the calculation.)
>
>> The first one with complete data to make a
>> decision terminates the whole process chain of all the rest.
>>
>>> must match that actual answer that running the REAL H_Hat gives. If
>>> other instances act different, all that shows is that somewhere there is
>>> a discrepancy that invalidates the example.
>>>
>>
>> H_Hat(H_Hat)
>> There are three different instances of H_Hat having different lengths of
>> the execution trace of its subordinate. The halt decider has no data
>> regarding the execution trace of the first H_Hat because it has not been
>> invoked yet. When it is invoked if begins to acquire data regarding the
>> execution trace of its first parameter. As soon as it has a sufficiently
>> long execution trace it makes it halting decision.
>>
>
> You have said that its decision is not a "halting/non-halting" decision
> in the sense of HP/Linz proof. I.e. it is not a decision on whether its
> input is in class HALTING or NON_HALTING. (Those classes being the
> calculation that eventually reach a halt state, or don't, respectively.)
>
> Continuing the earlier illustration, the outer emulation was abandoned
> after enumerating only 7000 of the full 10000 steps in the calculation,
> because the internal code decided it had found evidence of non-halting
> behaviour. Clearly that evidence was wrong in any meaningful sense,
> because in 10000 steps the calculation reaches a halt step.
>
> There's no arguing with that - I've got each of those 10000 explicit
> steps written down exactly, in my notebood! :) And look, step 10000 is
> indeed a halt state, so the calculation DOES halt. Whatever you are
> deciding, it's not whether the input is in the NON_HALTING class.
>
> Somehow you have just become confused and are looking at this
> incorrectly. You say the calculation /only/ terminates in 10000 steps
> /because/ of the way its program is written (something about the
> internal ABNHBD choosing to abandon its emulation after 7000 steps).
> That doesn't matter - the calculation /does/ halt in 10000 steps.
> Internal emulations may be abandoned when only 7000 steps have been
> enumerated, but nobody but you cares about that!
>
> The fact that if we replace H_Hat with H_Hat_2 [a different program,
> where its internal routine ABNHBD lacks the "non-terminating behaviour"
> test] then calculation H_Hat_2(H_Hat_2) doesn't halt is also quite
> irrelevant.
>
> If your argument is that ABNHBD in H or H_Hat returned the "correct"
> result, because ABNHBD did indeed abort its emulation after looking at
> only 7000 of the 10000 steps in the calculation, then you would only be
> saying that H is a "did my internal routine think it had found
> non-terminating behaviour" decider. Nobody is interested in that. (It
> would be a totally crass argument, not refuting anything.)
>
> Mike.
>
>
>> None of the instances of H_Hat directly have any data about the
>> execution trace of their input. All of this execution trace data is
>> held in the halt decider that they invoke:
>> bool Aborted_Because_Non_Halting_Behavior_Detected(H_Hat, H_Hat);
>>
>> If we construe that an H_Hat instance has the data of the halt decider
>> that it invoked by proxy then no halt decider has any data about the
>> outermost H_Hat. The outermost H_Hat though its halt decider has the
>> execution trace data of its input. This is the longest execution trace
>> thus the most data. Each subsequent H_Hat halt decider has decreasingly
>> less data.
>>
>> The halt decider for out outermost H_Hat does not exist so it has no
>> data. The halt decider for the H_Hat parameter to the outermost H_Hat
>> has the most data. The subsequent invocations of halt deciders and H_Hat
>> has increasingly less data.
>>
>> So the reason why the different H_Hats have different behavior is they
>> have a different amount of data. There is zero data about the execution
>> trace of the first H_Hat. There is the most data about the execution
>> trace of the next _H_Hat and there is less data about the execution
>> trace of the third H_Hat.
>>
>> The first halt decider has the most data about the execution trace of
>> any instance of H_Hat thus providing the legitimate reason why its
>> behavior differs.
>>
--
Copyright 2020 Pete Olcott
"Great spirits have always encountered violent opposition from mediocre
minds." Einstein
Back to comp.theory | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Architectural design of a halting problem solution olcott <NoOne@NoWhere.com> - 2020-10-27 14:30 -0500
Re: Architectural design of a halting problem solution André G. Isaak <agisaak@gm.invalid> - 2020-10-27 13:46 -0600
Re: Architectural design of a halting problem solution olcott <NoOne@NoWhere.com> - 2020-10-27 15:02 -0500
Re: Architectural design of a halting problem solution Mike Terry <news.dead.person.stones@darjeeling.plus.com> - 2020-10-27 20:03 +0000
Re: Architectural design of a halting problem solution olcott <NoOne@NoWhere.com> - 2020-10-27 15:13 -0500
Re: Architectural design of a halting problem solution André G. Isaak <agisaak@gm.invalid> - 2020-10-27 14:34 -0600
Re: Architectural design of a halting problem solution Mike Terry <news.dead.person.stones@darjeeling.plus.com> - 2020-10-27 21:11 +0000
Re: Architectural design of a halting problem solution olcott <NoOne@NoWhere.com> - 2020-10-27 16:27 -0500
Re: Architectural design of a halting problem solution Mike Terry <news.dead.person.stones@darjeeling.plus.com> - 2020-10-27 21:33 +0000
Re: Architectural design of a halting problem solution olcott <NoOne@NoWhere.com> - 2020-10-27 16:57 -0500
Re: Architectural design of a halting problem solution Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2020-10-27 14:44 -0700
Re: Architectural design of a halting problem solution olcott <NoOne@NoWhere.com> - 2020-10-27 16:54 -0500
Re: Architectural design of a halting problem solution Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2020-10-27 15:07 -0700
Re: Architectural design of a halting problem solution olcott <NoOne@NoWhere.com> - 2020-10-27 18:43 -0500
Re: Architectural design of a halting problem solution Richard Damon <Richard@Damon-Family.org> - 2020-10-27 21:45 -0400
Re: Architectural design of a halting problem solution olcott <NoOne@NoWhere.com> - 2020-10-27 21:28 -0500
Re: Architectural design of a halting problem solution Richard Damon <Richard@Damon-Family.org> - 2020-10-27 22:48 -0400
Re: Architectural design of a halting problem solution olcott <NoOne@NoWhere.com> - 2020-10-27 21:55 -0500
Re: Architectural design of a halting problem solution Richard Damon <Richard@Damon-Family.org> - 2020-10-28 09:04 -0400
Re: Architectural design of a halting problem solution Mostowski Collapse <janburse@fastmail.fm> - 2020-10-28 14:13 +0100
Re: Architectural design of a halting problem solution David Brown <david.brown@hesbynett.no> - 2020-10-28 15:12 +0100
Re: Architectural design of a halting problem solution Mostowski Collapse <janburse@fastmail.fm> - 2020-10-28 14:13 +0100
Re: Architectural design of a halting problem solution olcott <NoOne@NoWhere.com> - 2020-10-28 18:18 -0500
Re: Architectural design of a halting problem solution Alan Mackenzie <acm@muc.de> - 2020-10-28 09:38 +0000
Re: Architectural design of a halting problem solution olcott <NoOne@NoWhere.com> - 2020-10-28 17:54 -0500
Re: Architectural design of a halting problem solution Alan Mackenzie <acm@muc.de> - 2020-10-29 06:59 +0000
Re: Architectural design of a halting problem solution olcott <NoOne@NoWhere.com> - 2020-10-29 07:28 -0500
Re: Architectural design of a halting problem solution olcott <NoOne@NoWhere.com> - 2020-10-29 07:35 -0500
Re: Architectural design of a halting problem solution olcott <NoOne@NoWhere.com> - 2020-10-27 16:23 -0500
Re: Architectural design of a halting problem solution André G. Isaak <agisaak@gm.invalid> - 2020-10-27 22:49 -0600
Re: Architectural design of a halting problem solution olcott <NoOne@NoWhere.com> - 2020-10-28 00:05 -0500
Re: Architectural design of a halting problem solution André G. Isaak <agisaak@gm.invalid> - 2020-10-27 23:25 -0600
Re: Architectural design of a halting problem solution olcott <NoOne@NoWhere.com> - 2020-10-28 00:31 -0500
Re: Architectural design of a halting problem solution André G. Isaak <agisaak@gm.invalid> - 2020-10-27 23:55 -0600
Re: Architectural design of a halting problem solution olcott <NoOne@NoWhere.com> - 2020-10-28 17:50 -0500
Re: Architectural design of a halting problem solution Ben Bacarisse <ben.usenet@bsb.me.uk> - 2020-10-28 23:27 +0000
Re: Architectural design of a halting problem solution olcott <NoOne@NoWhere.com> - 2020-10-28 21:09 -0500
Re: Architectural design of a halting problem solution André G. Isaak <agisaak@gm.invalid> - 2020-10-29 00:45 -0600
Re: Architectural design of a halting problem solution olcott <NoOne@NoWhere.com> - 2020-10-29 07:18 -0500
Re: Architectural design of a halting problem solution André G. Isaak <agisaak@gm.invalid> - 2020-10-29 07:30 -0600
Re: Architectural design of a halting problem solution olcott <NoOne@NoWhere.com> - 2020-10-29 11:05 -0500
Re: Architectural design of a halting problem solution André G. Isaak <agisaak@gm.invalid> - 2020-10-29 10:55 -0600
Re: Architectural design of a halting problem solution olcott <NoOne@NoWhere.com> - 2020-10-29 12:52 -0500
Re: Architectural design of a halting problem solution André G. Isaak <agisaak@gm.invalid> - 2020-10-29 11:58 -0600
Re: Architectural design of a halting problem solution olcott <NoOne@NoWhere.com> - 2020-10-29 13:25 -0500
Re: Architectural design of a halting problem solution André G. Isaak <agisaak@gm.invalid> - 2020-10-29 12:56 -0600
Re: Architectural design of a halting problem solution olcott <NoOne@NoWhere.com> - 2020-10-29 14:13 -0500
Re: Architectural design of a halting problem solution André G. Isaak <agisaak@gm.invalid> - 2020-10-29 13:50 -0600
Re: Architectural design of a halting problem solution olcott <NoOne@NoWhere.com> - 2020-10-29 15:18 -0500
Re: Architectural design of a halting problem solution André G. Isaak <agisaak@gm.invalid> - 2020-10-29 14:52 -0600
Re: Architectural design of a halting problem solution olcott <NoOne@NoWhere.com> - 2020-10-29 16:18 -0500
Re: Architectural design of a halting problem solution André G. Isaak <agisaak@gm.invalid> - 2020-10-30 08:53 -0600
Re: Architectural design of a halting problem solution olcott <NoOne@NoWhere.com> - 2020-10-30 10:55 -0500
Re: Architectural design of a halting problem solution André G. Isaak <agisaak@gm.invalid> - 2020-10-31 08:28 -0600
Re: Architectural design of a halting problem solution olcott <NoOne@NoWhere.com> - 2020-10-31 09:53 -0500
Re: Architectural design of a halting problem solution André G. Isaak <agisaak@gm.invalid> - 2020-10-31 09:23 -0600
Re: Architectural design of a halting problem solution olcott <NoOne@NoWhere.com> - 2020-10-31 10:35 -0500
Re: Architectural design of a halting problem solution André G. Isaak <agisaak@gm.invalid> - 2020-10-31 09:44 -0600
Re: Architectural design of a halting problem solution olcott <NoOne@NoWhere.com> - 2020-10-31 11:03 -0500
Re: Architectural design of a halting problem solution André G. Isaak <agisaak@gm.invalid> - 2020-11-01 07:46 -0700
Re: Architectural design of a halting problem solution olcott <NoOne@NoWhere.com> - 2020-11-01 12:12 -0600
Re: Architectural design of a halting problem solution olcott <NoOne@NoWhere.com> - 2020-11-01 12:45 -0600
Re: Architectural design of a halting problem solution Richard Damon <Richard@Damon-Family.org> - 2020-10-31 14:46 -0400
Re: Architectural design of a halting problem solution olcott <NoOne@NoWhere.com> - 2020-10-31 13:57 -0500
Re: Architectural design of a halting problem solution Richard Damon <Richard@Damon-Family.org> - 2020-10-31 16:00 -0400
Re: Architectural design of a halting problem solution olcott <NoOne@NoWhere.com> - 2020-10-31 15:34 -0500
Re: Architectural design of a halting problem solution olcott <NoOne@NoWhere.com> - 2020-10-31 15:42 -0500
Re: Architectural design of a halting problem solution Alan Mackenzie <acm@muc.de> - 2020-10-31 21:07 +0000
Re: Architectural design of a halting problem solution olcott <NoOne@NoWhere.com> - 2020-10-31 16:19 -0500
Re: Architectural design of a halting problem solution Alan Mackenzie <acm@muc.de> - 2020-10-31 21:33 +0000
Re: Architectural design of a halting problem solution olcott <NoOne@NoWhere.com> - 2020-10-31 16:50 -0500
Re: Architectural design of a halting problem solution Richard Damon <Richard@Damon-Family.org> - 2020-10-31 18:31 -0400
Re: Architectural design of a halting problem solution [ Bill the auto mechanic can fix your car ] olcott <NoOne@NoWhere.com> - 2020-10-31 17:50 -0500
Re: Architectural design of a halting problem solution [ Bill the auto mechanic can fix your car ] Richard Damon <Richard@Damon-Family.org> - 2020-10-31 19:53 -0400
Re: Architectural design of a halting problem solution [ Bill the auto mechanic can fix your car ] olcott <NoOne@NoWhere.com> - 2020-10-31 19:19 -0500
Re: Architectural design of a halting problem solution [ Bill the auto mechanic can fix your car ] Richard Damon <Richard@Damon-Family.org> - 2020-10-31 21:19 -0400
Re: Architectural design of a halting problem solution [ Bill the auto mechanic can fix your car ] Richard Damon <Richard@Damon-Family.org> - 2020-10-31 22:22 -0400
Re: Architectural design of a halting problem solution [ Bill the auto mechanic can fix your car ] olcott <NoOne@NoWhere.com> - 2020-10-31 21:36 -0500
Re: Architectural design of a halting problem solution [ Bill the auto mechanic can fix your car ] olcott <NoOne@NoWhere.com> - 2020-10-31 22:18 -0500
Re: Architectural design of a halting problem solution [ Bill the auto mechanic can fix your car ] Richard Damon <Richard@Damon-Family.org> - 2020-11-01 08:19 -0500
Re: Architectural design of a halting problem solution [ Bill the auto mechanic can fix your car ] olcott <NoOne@NoWhere.com> - 2020-11-01 08:40 -0600
Re: Architectural design of a halting problem solution [ Bill the auto mechanic can fix your car ] Mike Terry <news.dead.person.stones@darjeeling.plus.com> - 2020-11-01 16:11 +0000
Re: Architectural design of a halting problem solution [ Bill the auto mechanic can fix your car ] olcott <NoOne@NoWhere.com> - 2020-11-01 12:18 -0600
Re: Architectural design of a halting problem solution [ Bill the auto mechanic can fix your car ] Mike Terry <news.dead.person.stones@darjeeling.plus.com> - 2020-11-01 19:50 +0000
Re: Architectural design of a halting problem solution [ Bill the auto mechanic can fix your car ] olcott <NoOne@NoWhere.com> - 2020-11-01 14:09 -0600
Re: Architectural design of a halting problem solution [ Bill the auto mechanic can fix your car ] olcott <NoOne@NoWhere.com> - 2020-11-01 14:38 -0600
Re: Architectural design of a halting problem solution [ Bill the auto mechanic can fix your car ] Mike Terry <news.dead.person.stones@darjeeling.plus.com> - 2020-11-01 21:32 +0000
Re: Architectural design of a halting problem solution [ Bill the auto mechanic can fix your car ] olcott <NoOne@NoWhere.com> - 2020-11-01 15:54 -0600
Re: Architectural design of a halting problem solution [ Bill the auto mechanic can fix your car ] Ben Bacarisse <ben.usenet@bsb.me.uk> - 2020-11-02 00:46 +0000
Re: Architectural design of a halting problem solution [ Bill the auto mechanic can fix your car ] olcott <NoOne@NoWhere.com> - 2020-11-01 19:05 -0600
Re: Architectural design of a halting problem solution [ Bill the auto mechanic can fix your car ] olcott <NoOne@NoWhere.com> - 2020-11-01 19:10 -0600
Re: Architectural design of a halting problem solution [ Bill the auto mechanic can fix your car ] Richard Damon <Richard@Damon-Family.org> - 2020-11-01 21:57 -0500
Re: Architectural design of a halting problem solution [ Bill the auto mechanic can fix your car ] olcott <NoOne@NoWhere.com> - 2020-11-01 22:33 -0600
Re: Architectural design of a halting problem solution [ Bill the auto mechanic can fix your car ] Richard Damon <Richard@Damon-Family.org> - 2020-11-02 08:53 -0500
Re: Architectural design of a halting problem solution [ Bill the auto mechanic can fix your car ] olcott <NoOne@NoWhere.com> - 2020-11-02 08:04 -0600
Re: Architectural design of a halting problem solution [ Bill the auto mechanic can fix your car ] Richard Damon <Richard@Damon-Family.org> - 2020-11-02 10:45 -0500
Re: Architectural design of a halting problem solution [ Bill the auto mechanic can fix your car ] Ben Bacarisse <ben.usenet@bsb.me.uk> - 2020-11-02 03:00 +0000
Re: Architectural design of a halting problem solution [ Bill the auto mechanic can fix your car ] olcott <NoOne@NoWhere.com> - 2020-11-01 22:32 -0600
Re: Architectural design of a halting problem solution [ Bill the auto mechanic can fix your car ] Ben Bacarisse <ben.usenet@bsb.me.uk> - 2020-11-02 20:55 +0000
Re: Architectural design of a halting problem solution [ Bill the auto mechanic can fix your car ] olcott <NoOne@NoWhere.com> - 2020-11-02 15:20 -0600
Re: Architectural design of a halting problem solution [ Bill the auto mechanic can fix your car ] olcott <NoOne@NoWhere.com> - 2020-11-02 16:20 -0600
Re: Architectural design of a halting problem solution [ Bill the auto mechanic can fix your car ] Ben Bacarisse <ben.usenet@bsb.me.uk> - 2020-11-02 01:16 +0000
Re: Architectural design of a halting problem solution [ Bill the auto mechanic can fix your car ] olcott <NoOne@NoWhere.com> - 2020-11-01 19:28 -0600
Re: Architectural design of a halting problem solution [ Bill the auto mechanic can fix your car ] Ben Bacarisse <ben.usenet@bsb.me.uk> - 2020-11-02 03:15 +0000
Re: Architectural design of a halting problem solution [ Adaptation of Ben's code simplifications ] olcott <NoOne@NoWhere.com> - 2020-11-01 22:20 -0600
Re: Architectural design of a halting problem solution [ Bill the auto mechanic can fix your car ] Mike Terry <news.dead.person.stones@darjeeling.plus.com> - 2020-11-02 03:02 +0000
Re: Architectural design of a halting problem solution [ one paragraph says it all ] olcott <NoOne@NoWhere.com> - 2020-11-01 21:55 -0600
Re: Architectural design of a halting problem solution [ Bill the auto mechanic can fix your car ] olcott <NoOne@NoWhere.com> - 2020-11-01 22:25 -0600
Re: Architectural design of a halting problem solution [ Bill the auto mechanic can fix your car ] Mike Terry <news.dead.person.stones@darjeeling.plus.com> - 2020-11-02 02:45 +0000
Re: Architectural design of a halting problem solution [ non halting behavior detected ] olcott <NoOne@NoWhere.com> - 2020-11-01 23:14 -0600
Re: Architectural design of a halting problem solution [ Bill the auto mechanic can fix your car ] Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2020-11-02 03:12 -0800
Re: Architectural design of a halting problem solution [ Bill the auto mechanic can fix your car ] André G. Isaak <agisaak@gm.invalid> - 2020-11-02 04:52 -0700
Re: Architectural design of a halting problem solution [ Bill the auto mechanic can fix your car ] olcott <NoOne@NoWhere.com> - 2020-11-02 08:01 -0600
Re: Architectural design of a halting problem solution [ Bill the auto mechanic can fix your car ] André G. Isaak <agisaak@gm.invalid> - 2020-11-02 08:12 -0700
Re: Architectural design of a halting problem solution [ Bill the auto mechanic can fix your car ] Richard Damon <Richard@Damon-Family.org> - 2020-11-02 10:23 -0500
Re: Architectural design of a halting problem solution [ Bill the auto mechanic can fix your car ] olcott <NoOne@NoWhere.com> - 2020-11-02 07:58 -0600
Re: Architectural design of a halting problem solution [ Bill the auto mechanic can fix your car ] olcott <NoOne@NoWhere.com> - 2020-11-01 14:02 -0600
Re: Architectural design of a halting problem solution [ Bill the auto mechanic can fix your car ] Richard Damon <Richard@Damon-Family.org> - 2020-11-01 17:52 -0500
Re: Architectural design of a halting problem solution [ Bill the auto mechanic can fix your car ] olcott <NoOne@NoWhere.com> - 2020-11-01 17:59 -0600
Re: Architectural design of a halting problem solution [ Bill the auto mechanic can fix your car ] Richard Damon <Richard@Damon-Family.org> - 2020-11-01 21:38 -0500
Re: Architectural design of a halting problem solution [ Bill the auto mechanic can fix your car ] olcott <NoOne@NoWhere.com> - 2020-11-01 21:05 -0600
Re: Architectural design of a halting problem solution [ Bill the auto mechanic can fix your car ] Mike Terry <news.dead.person.stones@darjeeling.plus.com> - 2020-11-02 00:17 +0000
Re: Architectural design of a halting problem solution [ Bill the auto mechanic can fix your car ] olcott <NoOne@NoWhere.com> - 2020-11-01 19:53 -0600
Re: Architectural design of a halting problem solution Alan Mackenzie <acm@muc.de> - 2020-11-01 08:29 +0000
Re: Architectural design of a halting problem solution Richard Damon <Richard@Damon-Family.org> - 2020-10-31 18:28 -0400
Re: Architectural design of a halting problem solution olcott <NoOne@NoWhere.com> - 2020-10-31 17:42 -0500
Re: Architectural design of a halting problem solution olcott <NoOne@NoWhere.com> - 2020-10-31 15:47 -0500
Re: Architectural design of a halting problem solution Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2020-10-29 13:13 -0700
Re: Architectural design of a halting problem solution André G. Isaak <agisaak@gm.invalid> - 2020-10-29 14:46 -0600
Re: Architectural design of a halting problem solution Andy Walker <anw@cuboid.co.uk> - 2020-10-29 14:41 +0000
Re: Architectural design of a halting problem solution olcott <NoOne@NoWhere.com> - 2020-10-29 10:29 -0500
Re: Architectural design of a halting problem solution Ben Bacarisse <ben.usenet@bsb.me.uk> - 2020-10-28 04:17 +0000
Stop crossposting you imbecil spammer (Re: Architectural design of a halting problem solution) Mostowski Collapse <janburse@fastmail.fm> - 2020-10-29 14:00 +0100
Re: Stop crossposting you imbecil spammer (Re: Architectural design of a halting problem solution) Joe Pfeiffer <pfeiffer@cs.nmsu.edu> - 2020-10-29 08:48 -0600
Re: Stop crossposting you imbecil spammer (Re: Architectural design of a halting problem solution) Mike Terry <news.dead.person.stones@darjeeling.plus.com> - 2020-10-29 15:17 +0000
Re: Stop crossposting you imbecil spammer (Re: Architectural design of a halting problem solution) olcott <NoOne@NoWhere.com> - 2020-10-29 11:13 -0500
Re: Stop crossposting you imbecil spammer (Re: Architectural design of a halting problem solution) Mike Terry <news.dead.person.stones@darjeeling.plus.com> - 2020-10-29 16:39 +0000
Re: Stop crossposting you imbecil spammer (Re: Architectural design of a halting problem solution) Manfred <noname@add.invalid> - 2020-10-29 19:20 +0100
Re: Stop crossposting you imbecil spammer (Re: Architectural design of a halting problem solution) Mike Terry <news.dead.person.stones@darjeeling.plus.com> - 2020-10-29 18:55 +0000
Re: Stop crossposting you imbecil spammer (Re: Architectural design of a halting problem solution) David Brown <david.brown@hesbynett.no> - 2020-10-30 11:02 +0100
Re: Stop crossposting you imbecil spammer (Re: Architectural design of a halting problem solution) Ben Bacarisse <ben.usenet@bsb.me.uk> - 2020-10-30 10:52 +0000
Re: Stop crossposting you imbecil spammer (Re: Architectural design of a halting problem solution) Jorgen Grahn <grahn+nntp@snipabacken.se> - 2020-10-30 19:47 +0000
Re: Stop crossposting you imbecil spammer (Re: Architectural design of a halting problem solution) Ralf Goertz <me@myprovider.invalid> - 2020-10-30 12:55 +0100
Re: Stop crossposting you imbecil spammer (Re: Architectural design of a halting problem solution) Mike Terry <news.dead.person.stones@darjeeling.plus.com> - 2020-10-30 16:33 +0000
Re: Stop crossposting you imbecil spammer (Re: Architectural design of a halting problem solution Mostowski Collapse <janburse@fastmail.fm> - 2020-10-29 19:40 +0100
csiph-web