Rocksolid Light

Welcome to novaBBS (click a section below)

mail  files  register  newsreader  groups  login

Message-ID:  

Life would be so much easier if we could just look at the source code. -- Dave Olson


computers / comp.theory / Re: Halting problem proofs refuted on the basis of software engineering ?

Re: Halting problem proofs refuted on the basis of software engineering ?

<cF7XK.652296$BKL8.317962@fx15.iad>

  copy mid

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

  copy link   Newsgroups: comp.theory
Path: i2pn2.org!i2pn.org!usenet.blueworldhosting.com!feed1.usenet.blueworldhosting.com!peer02.iad!feed-me.highwinds-media.com!news.highwinds-media.com!fx15.iad.POSTED!not-for-mail
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:91.0)
Gecko/20100101 Thunderbird/91.13.0
Subject: Re: Halting problem proofs refuted on the basis of software
engineering ?
Content-Language: en-US
Newsgroups: comp.theory
References: <tgcn30$1hr5j$1@dont-email.me> <EsrWK.418215$6Il8.304299@fx14.iad>
<tgdhph$1ka58$2@dont-email.me> <45tWK.418218$6Il8.45041@fx14.iad>
<tgdnah$1tu8$1@gioia.aioe.org> <tgdo81$7l4$1@gioia.aioe.org>
<tgdoru$crq$1@gioia.aioe.org> <pMtWK.632769$BKL8.247886@fx15.iad>
<tgdts3$1r0t$1@gioia.aioe.org> <l2vWK.42309$0qy7.30442@fx40.iad>
<tgdv84$5is$1@gioia.aioe.org> <wmvWK.303367$wLZ8.63666@fx18.iad>
<tge101$1nsnl$2@dont-email.me> <yPvWK.143777$IRd5.53996@fx10.iad>
<tge23a$1nsnl$4@dont-email.me> <_nCWK.198870$BQA7.175961@fx41.iad>
<tgfb7a$1rk5o$3@dont-email.me> <osMWK.136080$w35c.30681@fx47.iad>
<tgg7sh$nvu$1@gioia.aioe.org> <IvNWK.347516$SAT4.312085@fx13.iad>
<tgg9c6$163m$1@gioia.aioe.org> <23OWK.430767$6Il8.380479@fx14.iad>
<tghumo$26tsi$2@dont-email.me> <1t5XK.56020$OR4c.20701@fx46.iad>
<tgir6t$485$2@gioia.aioe.org>
From: Rich...@Damon-Family.org (Richard Damon)
In-Reply-To: <tgir6t$485$2@gioia.aioe.org>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Lines: 190
Message-ID: <cF7XK.652296$BKL8.317962@fx15.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: Thu, 22 Sep 2022 21:07:20 -0400
X-Received-Bytes: 10228
 by: Richard Damon - Fri, 23 Sep 2022 01:07 UTC

On 9/22/22 7:30 PM, olcott wrote:
> On 9/22/2022 5:37 PM, Richard Damon wrote:
>> On 9/22/22 11:24 AM, olcott wrote:
>>> On 9/21/2022 7:33 PM, Richard Damon wrote:
>>>> On 9/21/22 8:13 PM, olcott wrote:
>>>>> On 9/21/2022 6:55 PM, Richard Damon wrote:
>>>>>>
>>>>>> On 9/21/22 7:48 PM, olcott wrote:
>>>>>>> On 9/21/2022 5:43 PM, Richard Damon wrote:
>>>>>>>> On 9/21/22 11:39 AM, olcott wrote:
>>>>>>>>> On 9/21/2022 6:16 AM, Richard Damon wrote:
>>>>>>>>>> On 9/20/22 11:57 PM, olcott wrote:
>>>>>>>>>>> On 9/20/2022 10:47 PM, Richard Damon wrote:
>>>>>>>>>>>> On 9/20/22 11:38 PM, olcott wrote:
>>>>>>>>>>>>> On 9/20/2022 10:16 PM, Richard Damon wrote:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> On 9/20/22 11:08 PM, olcott wrote:
>>>>>>>>>>>>>>> On 9/20/2022 9:55 PM, Richard Damon wrote:
>>>>>>>>>>>>>>>> On 9/20/22 10:45 PM, olcott wrote:
>>>>>>>>>>>>>>>>> On 9/20/2022 8:27 PM, Richard Damon wrote:
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> On 9/20/22 9:19 PM, olcott wrote:
>>>>>>>>>>>>>>>>>>> On 9/20/2022 8:10 PM, Python wrote:
>>>>>>>>>>>>>>>>>>>> Demented crank Peter Olcott wrote:
>>>>>>>>>>>>>>>>>>>>> On 9/20/2022 7:41 PM, Richard Damon wrote:
>>>>>>>>>>>>>>>>>>>>>> On 9/20/22 7:19 PM, olcott wrote:
>>>>>>>>>>>>>>>>>>>>>>> On 9/20/2022 5:50 PM, Richard Damon wrote:
>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>> On 9/20/22 11:43 AM, olcott wrote:
>>>>>>>>>>>>>>>>>>>>>>>>> This is an explanation of a possible new
>>>>>>>>>>>>>>>>>>>>>>>>> insight into the halting problem provided in
>>>>>>>>>>>>>>>>>>>>>>>>> the language of software engineering. Technical
>>>>>>>>>>>>>>>>>>>>>>>>> computer science terms are explained using
>>>>>>>>>>>>>>>>>>>>>>>>> software engineering terms. No knowledge of the
>>>>>>>>>>>>>>>>>>>>>>>>> halting problem is required.
>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>> When the conventional “pathological” input
>>>>>>>>>>>>>>>>>>>>>>>>> (that does the opposite of whatever the halt
>>>>>>>>>>>>>>>>>>>>>>>>> decider decides) is the first argument to a
>>>>>>>>>>>>>>>>>>>>>>>>> simulating halt decider then this input becomes
>>>>>>>>>>>>>>>>>>>>>>>>> decidable as specifying infinitely recursive
>>>>>>>>>>>>>>>>>>>>>>>>> simulation.
>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>> Except it doesn't as if H is a Decider, it BE
>>>>>>>>>>>>>>>>>>>>>>>> DEFINITION has finite behavior so NO CALL to it
>>>>>>>>>>>>>>>>>>>>>>>> can be "infinite"
>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>> Another way that we can say this is that P
>>>>>>>>>>>>>>>>>>>>>>> specifies behavior that would never reach its own
>>>>>>>>>>>>>>>>>>>>>>> final state.
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>> No, because P DOES reach its final state when it
>>>>>>>>>>>>>>>>>>>>>> is run
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> // H(P,P) does not reach a final state when it is run
>>>>>>>>>>>>>>>>>>>>> int H(ptr x, ptr y)
>>>>>>>>>>>>>>>>>>>>> {
>>>>>>>>>>>>>>>>>>>>>    x(y);
>>>>>>>>>>>>>>>>>>>>> }
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> I keep correcting you and you keep dishonestly
>>>>>>>>>>>>>>>>>>>>> forgetting these corrections. *That is the main
>>>>>>>>>>>>>>>>>>>>> reason that it seems you may be a liar*
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> The liar is the one who uses H as a unique name to
>>>>>>>>>>>>>>>>>>>> qualify different
>>>>>>>>>>>>>>>>>>>> functions. Make up your mind about how H is supposed
>>>>>>>>>>>>>>>>>>>> to be an halt
>>>>>>>>>>>>>>>>>>>> decider and you'll see that you cannot avoid
>>>>>>>>>>>>>>>>>>>> Richard's objection
>>>>>>>>>>>>>>>>>>>> to your silliness. Which the main argument for such
>>>>>>>>>>>>>>>>>>>> an H not to
>>>>>>>>>>>>>>>>>>>> exist in the first place. Word salad won't help you
>>>>>>>>>>>>>>>>>>>> much.
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> You are the liar, Peter.
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> Every correct halt decider H must predict the
>>>>>>>>>>>>>>>>>>> behavior of its own direct execution of its input
>>>>>>>>>>>>>>>>>>> even though it does not perform a direct execution of
>>>>>>>>>>>>>>>>>>> this input.
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> And that statement is illogical because it asks what
>>>>>>>>>>>>>>>>>> would happen if something does something that it
>>>>>>>>>>>>>>>>>> doesn't do.
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> A halt decider can correctly predict that an infinite
>>>>>>>>>>>>>>>>> loop never halts without executing it. That you act
>>>>>>>>>>>>>>>>> like you keep forgetting this is either dishonest or
>>>>>>>>>>>>>>>>> you actually keep forgetting it, thus dementia.
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Yes, but if the loop isn't infinite (or not even a
>>>>>>>>>>>>>>>> loop), it is incorrect to predict that it is.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Remember, you AGREE that P(P) will Halt if H(P,P)
>>>>>>>>>>>>>>>> returns 0.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Of every input P to every H that either simulates or
>>>>>>>>>>>>>>> executes its input no H ever returns anything to P.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> A halt decider must compute the mapping
>>>>>>>>>>>>>>> FROM ITS INPUT
>>>>>>>>>>>>>>> FROM ITS INPUT
>>>>>>>>>>>>>>> FROM ITS INPUT
>>>>>>>>>>>>>>> FROM ITS INPUT
>>>>>>>>>>>>>>> FROM ITS INPUT
>>>>>>>>>>>>>>> To an accept or reject state.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Right, the input is the representation of P and its input P
>>>>>>>>>>>>>>
>>>>>>>>>>>>> It is the actual behavior of the actual executed or
>>>>>>>>>>>>> simulated input.
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> Which means, for H(P,P) the running of P(P) or UTM(P,P) as
>>>>>>>>>>>> independent computaitons.
>>>>>>>>>>>>
>>>>>>>>>>>> Those Halt.
>>>>>>>>>>>
>>>>>>>>>>> H is only allowed to report on the behavior that it sees.
>>>>>>>>>>> H is NOT allowed to report on behavior that it does not see.
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> Nope. That isn't the definition.
>>>>>>>>>
>>>>>>>>> Sure it is. A halt decider must compute the mapping from its
>>>>>>>>> input to an accept or reject state based on the actual behavior
>>>>>>>>> specified by the direct execution of this input.
>>>>>>>>
>>>>>>>> Right *THE* not *ITS* direct execution of its input.
>>>>>>>>
>>>>>>>> That is the behavior of executing its input as a totally
>>>>>>>> independent machine.
>>>>>>>>
>>>>>>>>>
>>>>>>>>> This is not the input thus not a direct execution of the input:
>>>>>>>>> int main() { P(P); }
>>>>>>>>
>>>>>>>> No, That IS the direct execution of its input per your model.
>>>>>>>
>>>>>>> Because this is not the actual input to H, and its behavior is
>>>>>>> not the same as the behavior of this actual input to H then it
>>>>>>> violates the principle that a halt decider must report on the
>>>>>>> actual behavior of its actual input.
>>>>>>
>>>>>> No, it IS its actual input, as specified by its representation.
>>>>> All that "representation" actually means is that the halt decider
>>>>> examines a finite string encoding of a Turing Machine thus not the
>>>>> Turing machine itself.
>>>>>
>>>>> It certainly does not mean that the halt decider must examine the
>>>>> mental idea that you have about what the input does.
>>>>>
>>>>
>>>> Except that it does.
>>> No competent software engineer or computer scientist will agree that
>>> ideas held within the mind that are not encoded as finite strings are
>>> legitimate inputs to any computation.
>>>
>>
>> Except that the behavior IS fully described by the finite string
>> description and not just "In the mind".
> This is easily proven false on the basis of the correct simulation of
> this finite string by the SHD.
>

Which is a LIE, because the SHD that answers 0 to H(P,P) DOESN'T do a
COMPLETE simulation, but stops because it INCORRECTLY assumes that
H(P,P) will never return.

The SHD that does simulate AN input completely showing that its input
doesn't halt, is simulationg a DIFFERENT input, because it is calling a
different H than the one that the actual one does.

You have provided that ACTUAL complete simulation of this input and
showed that it halts.

Thus, you are just proving that you just are ignorant about what you are
talking about, that you just lie about these things, and are just too
stupid to know what you are doing.

SubjectRepliesAuthor
o Halting problem proofs refuted on the basis of software engineering ?

By: olcott on Tue, 20 Sep 2022

67olcott
server_pubkey.txt

rocksolid light 0.9.81
clearnet tor