Rocksolid Light

Welcome to Rocksolid Light

mail  files  register  newsreader  groups  login

Message-ID:  

"We don't care. We don't have to. We're the Phone Company."


computers / comp.ai.philosophy / Re: Refutation of the Ben Bacarisse Rebuttal

Re: Refutation of the Ben Bacarisse Rebuttal

<LiBkM.9826$8fUf.8969@fx16.iad>

  copy mid

https://news.novabbs.org/computers/article-flat.php?id=11427&group=comp.ai.philosophy#11427

  copy link   Newsgroups: comp.theory sci.logic comp.ai.philosophy
Path: i2pn2.org!i2pn.org!weretis.net!feeder6.news.weretis.net!panix!usenet.blueworldhosting.com!diablo1.usenet.blueworldhosting.com!peer03.iad!feed-me.highwinds-media.com!news.highwinds-media.com!fx16.iad.POSTED!not-for-mail
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:102.0)
Gecko/20100101 Thunderbird/102.12.0
Subject: Re: Refutation of the Ben Bacarisse Rebuttal
Newsgroups: comp.theory,sci.logic,comp.ai.philosophy
References: <u6qell$25lfs$1@dont-email.me> <rE6kM.5962$zcM5.3620@fx11.iad>
<u6qtqj$273dd$2@dont-email.me> <u6quge$277en$1@dont-email.me>
<u6r7dt$2bi2u$3@dont-email.me> <JWfkM.7457$Zq81.4718@fx15.iad>
<u6sf1o$2fgh0$1@dont-email.me> <gTjkM.3651$WpOe.3136@fx18.iad>
<u6solb$2ggcv$1@dont-email.me> <06mkM.4327$1CTd.966@fx03.iad>
<u6sre8$2go01$1@dont-email.me> <H1okM.865$Ect9.276@fx44.iad>
<u6t2nm$2hh2e$1@dont-email.me> <1fokM.7187$Vpga.2560@fx09.iad>
<u6t5jr$2hu9u$1@dont-email.me> <JgpkM.839$3XE8.474@fx42.iad>
<u6t8kt$2iavi$1@dont-email.me> <u4qkM.9814$8fUf.1381@fx16.iad>
<u6tb1f$2iisn$1@dont-email.me> <yGrkM.7192$Vpga.651@fx09.iad>
<u6tk6j$2nal3$1@dont-email.me> <sjtkM.307$_%y4.301@fx48.iad>
<u6tp20$2ns03$1@dont-email.me>
From: Richard@Damon-Family.org (Richard Damon)
Content-Language: en-US
In-Reply-To: <u6tp20$2ns03$1@dont-email.me>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Lines: 326
Message-ID: <LiBkM.9826$8fUf.8969@fx16.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: Wed, 21 Jun 2023 07:38:19 -0400
X-Received-Bytes: 16830
 by: Richard Damon - Wed, 21 Jun 2023 11:38 UTC

On 6/20/23 10:59 PM, olcott wrote:
> On 6/20/2023 9:32 PM, Richard Damon wrote:
>> On 6/20/23 9:36 PM, olcott wrote:
>>> On 6/20/2023 7:41 PM, Richard Damon wrote:
>>>> On 6/20/23 6:59 PM, olcott wrote:
>>>>> On 6/20/2023 5:52 PM, Richard Damon wrote:
>>>>>> On 6/20/23 6:19 PM, olcott wrote:
>>>>>>> On 6/20/2023 4:56 PM, Richard Damon wrote:
>>>>>>>> On 6/20/23 5:27 PM, olcott wrote:
>>>>>>>>> On 6/20/2023 3:46 PM, Richard Damon wrote:
>>>>>>>>>> On 6/20/23 4:38 PM, olcott wrote:
>>>>>>>>>>> On 6/20/2023 3:32 PM, Richard Damon wrote:
>>>>>>>>>>>> On 6/20/23 2:33 PM, olcott wrote:
>>>>>>>>>>>>> On 6/20/2023 1:20 PM, Richard Damon wrote:
>>>>>>>>>>>>>> On 6/20/23 1:46 PM, olcott wrote:
>>>>>>>>>>>>>>> On 6/20/2023 10:48 AM, Richard Damon wrote:
>>>>>>>>>>>>>>>> On 6/20/23 11:02 AM, olcott wrote:
>>>>>>>>>>>>>>>>> On 6/20/2023 6:19 AM, Richard Damon wrote:
>>>>>>>>>>>>>>>>>> On 6/19/23 11:46 PM, olcott wrote:
>>>>>>>>>>>>>>>>>>> On 6/19/2023 8:13 PM, Richard Damon wrote:
>>>>>>>>>>>>>>>>>>>> On 6/19/23 9:02 PM, olcott wrote:
>>>>>>>>>>>>>>>>>>>>> On 6/19/2023 7:45 PM, Richard Damon wrote:
>>>>>>>>>>>>>>>>>>>>>> On 6/19/23 4:43 PM, olcott wrote:
>>>>>>>>>>>>>>>>>>>>>>> The behavior of the directly executed P(P) is
>>>>>>>>>>>>>>>>>>>>>>> different than the
>>>>>>>>>>>>>>>>>>>>>>> behavior of P(P) correctly simulated by H because
>>>>>>>>>>>>>>>>>>>>>>> in the first case H
>>>>>>>>>>>>>>>>>>>>>>> has already aborted its simulation of its input
>>>>>>>>>>>>>>>>>>>>>>> and in the second case
>>>>>>>>>>>>>>>>>>>>>>> this has not yet occurred.
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>> By what definition of "Correctly Simulated"?
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>> The fact that H aborts its simulation has NO
>>>>>>>>>>>>>>>>>>>>>> affect on the direct execution of the machine, so
>>>>>>>>>>>>>>>>>>>>>> all you are saying that H has shut its eyes and
>>>>>>>>>>>>>>>>>>>>>> said "I don't see it, so it didn't happen".
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>> That is just FALSEHOOD.
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>> I now refer to P(P) as D(D).
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>> Can D correctly simulated by H terminate normally?
>>>>>>>>>>>>>>>>>>>>>>> No it cannot see the details below.
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>> Which is not the question being asked. The fact
>>>>>>>>>>>>>>>>>>>>>> that it is impossible to design an H that can
>>>>>>>>>>>>>>>>>>>>>> correctly simulate its input to a halting state
>>>>>>>>>>>>>>>>>>>>>> just proves that H can not correctly decider that
>>>>>>>>>>>>>>>>>>>>>> its input is Halting.
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>> This does NOT mean that the input can't be
>>>>>>>>>>>>>>>>>>>>>> Halting, just that H can never prove it.
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>> IF H doesn't ever abort its simulation, then yes,
>>>>>>>>>>>>>>>>>>>>>> the D built on that H is non-halting, but that H
>>>>>>>>>>>>>>>>>>>>>> never gives that answer, so it is still wrong.
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>> Each H gets a DIFFERENT D, since they include the
>>>>>>>>>>>>>>>>>>>>>> H that the "pathological test" is to be performed
>>>>>>>>>>>>>>>>>>>>>> on, so the behavior of one D built on a different
>>>>>>>>>>>>>>>>>>>>>> H doesn't apply, and for correct reasoning, you
>>>>>>>>>>>>>>>>>>>>>> really need to give each one a different name.
>>>>>>>>>>>>>>>>>>>>>> Reusing the same name for different machine, and
>>>>>>>>>>>>>>>>>>>>>> then trying to confuse which one is which is just
>>>>>>>>>>>>>>>>>>>>>> a sign of being intentionally deceptive to try to
>>>>>>>>>>>>>>>>>>>>>> tell a LIE.
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>> The x86utm operating system based on an open
>>>>>>>>>>>>>>>>>>>>>>> source x86 emulator. This
>>>>>>>>>>>>>>>>>>>>>>> system enables one C function to execute another
>>>>>>>>>>>>>>>>>>>>>>> C function in debug
>>>>>>>>>>>>>>>>>>>>>>> step mode. When H simulates D it creates a
>>>>>>>>>>>>>>>>>>>>>>> separate process context for
>>>>>>>>>>>>>>>>>>>>>>> D with its own memory, stack and virtual
>>>>>>>>>>>>>>>>>>>>>>> registers. H is able to
>>>>>>>>>>>>>>>>>>>>>>> simulate D simulating itself, thus the only limit
>>>>>>>>>>>>>>>>>>>>>>> to recursive
>>>>>>>>>>>>>>>>>>>>>>> simulations is RAM.
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>> But D is not SPECIFIED in a seperate context, but
>>>>>>>>>>>>>>>>>>>>>> share code space with H, which means it fails to
>>>>>>>>>>>>>>>>>>>>>> be truely distinctly, like a Turing Machine would be.
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>> It is NOT a full "separate process context" as all
>>>>>>>>>>>>>>>>>>>>>> the contexts share code space.
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>> // The following is written in C
>>>>>>>>>>>>>>>>>>>>>>> //
>>>>>>>>>>>>>>>>>>>>>>> 01 typedef int (*ptr)(); // pointer to int function
>>>>>>>>>>>>>>>>>>>>>>> 02 int H(ptr x, ptr y)   // uses x86 emulator to
>>>>>>>>>>>>>>>>>>>>>>> simulate its input
>>>>>>>>>>>>>>>>>>>>>>> 03
>>>>>>>>>>>>>>>>>>>>>>> 04 int D(ptr x)
>>>>>>>>>>>>>>>>>>>>>>> 05 {
>>>>>>>>>>>>>>>>>>>>>>> 06   int Halt_Status = H(x, x);
>>>>>>>>>>>>>>>>>>>>>>> 07   if (Halt_Status)
>>>>>>>>>>>>>>>>>>>>>>> 08     HERE: goto HERE;
>>>>>>>>>>>>>>>>>>>>>>> 09   return Halt_Status;
>>>>>>>>>>>>>>>>>>>>>>> 10 }
>>>>>>>>>>>>>>>>>>>>>>> 11
>>>>>>>>>>>>>>>>>>>>>>> 12 void main()
>>>>>>>>>>>>>>>>>>>>>>> 13 {
>>>>>>>>>>>>>>>>>>>>>>> 14   D(D);
>>>>>>>>>>>>>>>>>>>>>>> 15 }
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>> D correctly simulated by H cannot possibly
>>>>>>>>>>>>>>>>>>>>>>> terminate normally by reaching its own final
>>>>>>>>>>>>>>>>>>>>>>> state at line 09.
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>> But D correctly simulated by a correct simulator
>>>>>>>>>>>>>>>>>>>>>> would, at least as long as you are using an H that
>>>>>>>>>>>>>>>>>>>>>> answer H(D,D) as 0, as you claim.
>>>>>>>>>>>>>>>>>>>>> H correctly simulates N steps of D until H
>>>>>>>>>>>>>>>>>>>>> correctly predicts through
>>>>>>>>>>>>>>>>>>>>> the type of mathematical induction used by
>>>>>>>>>>>>>>>>>>>>> termination analyzers that D
>>>>>>>>>>>>>>>>>>>>> correctly simulated by H cannot possibly terminate
>>>>>>>>>>>>>>>>>>>>> normally.
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> But that is the wrong prediction. It needs to
>>>>>>>>>>>>>>>>>>>> predict if the input when run will halt, as THAT is
>>>>>>>>>>>>>>>>>>>> the Halting Question.
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> That is just like Jack's question posed to Jack,
>>>>>>>>>>>>>>>>>>> self-contradictory.
>>>>>>>>>>>>>>>>>>> ChatGPT could understand that I am correct.
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> Nope, and you just seem too stupid to understand.
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> Thus, you are just admitting to working on POOP
>>>>>>>>>>>>>>>>>>>> instead of Halting, and ALL your statements are just
>>>>>>>>>>>>>>>>>>>> LIES.
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> int factorial(int n)
>>>>>>>>>>>>>>>>>>>>> {
>>>>>>>>>>>>>>>>>>>>>    if(n==0)
>>>>>>>>>>>>>>>>>>>>>      return(1);
>>>>>>>>>>>>>>>>>>>>>    return(n*factorial(n-1));
>>>>>>>>>>>>>>>>>>>>> }
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> AProVE correctly determines that factorial(5) halts by
>>>>>>>>>>>>>>>>>>>>> boiling the key behavior of entire function to this:
>>>>>>>>>>>>>>>>>>>>> f(x) → f(x-1) :|: x > 0 && x <= 5
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>  > Wrong Question leads to incorrect answer, and all
>>>>>>>>>>>>>>>>>>>> your work goes down
>>>>>>>>>>>>>>>>>>>> the drain.
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> AProVE is the largest termination analysis project in
>>>>>>>>>>>>>>>>>>> the world.
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> Yes, and it probably uses the RIGHT question, will the
>>>>>>>>>>>>>>>>>> program halt when actually run.
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> It will probably also tell you that D(D) will Halt
>>>>>>>>>>>>>>>>>> since H(D,D) returns 0.
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> Thus, it likely shows you are wrong about everything.
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> When we use the criteria:
>>>>>>>>>>>>>>>>> Can D correctly simulated by H ever terminate normally?
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> So you are ADMITTING to working on a different problem,
>>>>>>>>>>>>>>>> and lying about what you are doing. Thank you for being
>>>>>>>>>>>>>>>> honest about that.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Ben is just pointing out the ERRORS in your logic
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> When Ben pointed out that H(P,P) reports that P(P) does
>>>>>>>>>>>>>>> not halt when
>>>>>>>>>>>>>>> P(P) does halt this seems to be a contradiction to people
>>>>>>>>>>>>>>> that lack a
>>>>>>>>>>>>>>> complete understanding.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> NO, it is a TRUE statement. H is NOT a correct HALT DECIDER.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> It might be a valid POOP decider with your altered
>>>>>>>>>>>>>> criteria, but it isn't correct as a Halt Decider.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> You don't get to change the meaning of words, attempting
>>>>>>>>>>>>>> to just shows you are a liar.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Halting is a property of the original machine, not of the
>>>>>>>>>>>>>> partial simulation that H does.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Because of this I changed the semantic meaning of a
>>>>>>>>>>>>>>> return value of 0
>>>>>>>>>>>>>>> from H to mean either that P(P) does not halt or P(P)
>>>>>>>>>>>>>>> specifically
>>>>>>>>>>>>>>> targets H to do the opposite of whatever Boolean value
>>>>>>>>>>>>>>> that H returns.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Which means you H need to return BOTH a 0 and 1 at the
>>>>>>>>>>>>>> same time,
>>>>>>>>>>>>> Not at all. Not the least little bit.
>>>>>>>>>>>>> A return value of 0 also indicates that input D
>>>>>>>>>>>>> intentionally targets
>>>>>>>>>>>>> H by doing the opposite of whatever Boolean value that H
>>>>>>>>>>>>> returns.
>>>>>>>>>>>>
>>>>>>>>>>>> But a return of 1 signals that it halts, which it does.
>>>>>>>>>>>>
>>>>>>>>>>>> You don't seem to understand English.
>>>>>>>>>>>>
>>>>>>>>>>>> The Halting Problem asks if the Machine Described by the
>>>>>>>>>>>> input Halts.
>>>>>>>>>>>>
>>>>>>>>>>>> It Does (for the H that you are cliaming to be correct)
>>>>>>>>>>>>
>>>>>>>>>>>> Therefore, the correct answer is YES / Halting, and you are
>>>>>>>>>>>> PROVED to be a LIAR.
>>>>>>>>>>> If I am the one that is a Liar then why did you already say
>>>>>>>>>>> that 1 is
>>>>>>>>>>> the wrong answer and are now saying that it is the right answer?
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> Where did I say that 1 is the wrong answer to THAT question.
>>>>>>>>>>
>>>>>>>>> What happens when H returns 1 to D?
>>>>>>>>>
>>>>>>>>
>>>>>>>> But it doesn't, so it doesn't matter.
>>>>>>> No H can possibly be defined that can be embedded within
>>>>>>> Linz Ĥ such that embedded_H ⟨Ĥ⟩ ⟨Ĥ⟩ transitions to Ĥ.qy or Ĥ.qn
>>>>>>> consistently with the behavior of Ĥ applied to ⟨Ĥ⟩.
>>>>>>
>>>>>> Right, which is why it is impossible to make a correct Halt Decider.
>>>>>>
>>>>>>>
>>>>>>> The reason for this is that Ĥ does the opposite of both
>>>>>>> Ĥ.qy and Ĥ.qn. This makes the input ⟨Ĥ⟩ ⟨Ĥ⟩ to embedded_H
>>>>>>> self-contradictory for embedded_H.
>>>>>>
>>>>>> Not SELF contradicotory, but just contradictory.
>>>>>>
>>>>>
>>>>> OK that may make sense. One of our very rare agreements. The
>>>>> question does not contradict itself it contradicts every answer.
>>>>>
>>>>> Contradictory questions are also incorrect questions.
>>>>> Likewise Jack's question contradicts every answer.
>>>>>
>>>>
>>>> It doesn't contradict the answer to the actual question,
>>> If this is true then you can say which of yes/no are correct for Jack to
>>> reply and which of true/false that H can return.
>>>
>>
>> SO, you are just to dumb to understand
>
> That simply dodges my yes/no question.
>
> My IQ is probably higher than yours. Did you pass the Mensa test?
> In any case creative genius has its algorithm:
> https://www.scientificamerican.com/article/the-science-of-genius1/

I never took the Mensa test, as I saw no benefit to taking it.

>
> If this is true then you can say which of yes/no are correct for
> Jack to reply and which of true/false that H can return.
>

How do you get that conclusion? You are working off BAD LOGIC.

> The only reason that no one can do this is that in both of
> these cases the correct reply from Jack and return value from H
> are contradicted by his question and the input to H.
>

Jack's question has a contradiction, because Jack has volition, and his
next answer isn't determined until he says it. Thus it can be that
neither answer is correct, as the volitional process of answering it
changes what answer is correct.

The question to H is not a contradiction, as H's answer has been fixed
before we ask it by the code of H (and D). Thus, we can see that H was
just always wrong, no matter how we designed it.

The fact that you just can't actualy keep the actual question in mind,
and keep on switching to a false question shows your mental defect. You
can't seem to understand that you can't think about changing something
that is fixed without resetting the whole problem. You can't ask in the
same manner what H should return as we can Does D(D) Halt or
equivalenetly what is the correct answer that H SHOULD have returned to
be correct.

The issue with your question is you don't actually have an input to
decide on, as the input isn't fully created until you have fixed H. All
you have is an input recipe for this particular problem. The recipe
doesn't affect the definition of the Halting Problem, as the Halting
Problem is about actual machines so only about the products of the
recipe, and irrespective of how a given machine was made, but ALLOWS the
recipe, as the requirement is to handle ALL Machines.

And it is the ALL MACHINES part of the problem that makes it
interesting, having a decider that just handles "many" cases, but not
all isn't very useful if the case you want to handle is one of the
exceptions.

The fact that you can't understand these fundamental facts, but keep on
insisting that you can correctly decide a Halting Machine as Non-Halting
because the problem is too tough for H just shows how little you
understand what truth and logic is actually about.

The smart man knows what he does not know. You don't, you seem to THINK
you know a lot about these things, but what you "know" is actually
falsehood and your own deception, so you have the opposite of
"Knowledge", you have true Ignorance.

You have destroyed your life, and your reputation. In some ways I feel
pity for you.

SubjectRepliesAuthor
o Refutation of the Ben Bacarisse Rebuttal

By: olcott on Mon, 19 Jun 2023

29olcott
server_pubkey.txt

rocksolid light 0.9.81
clearnet tor