Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.software-eng > #2154 > unrolled thread

Re: olcott's correct refutation of the Peter Linz HP proof (now includes Sipser Kozen)

Started byolcott <NoOne@NoWhere.com>
First post2020-12-08 15:19 -0600
Last post2020-12-08 16:11 -0600
Articles 4 — 2 participants

Back to article view | Back to comp.software-eng

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.


Contents

  Re: olcott's correct refutation of the Peter Linz HP proof (now includes Sipser Kozen) olcott <NoOne@NoWhere.com> - 2020-12-08 15:19 -0600
    Re: olcott's correct refutation of the Peter Linz HP proof (now includes Sipser Kozen) Kaz Kylheku <563-365-8930@kylheku.com> - 2020-12-08 21:39 +0000
      Re: olcott's correct refutation of the Peter Linz HP proof (now includes Sipser Kozen) olcott <NoOne@NoWhere.com> - 2020-12-08 16:02 -0600
        Re: olcott's correct refutation of the Peter Linz HP proof (now includes Sipser Kozen) olcott <NoOne@NoWhere.com> - 2020-12-08 16:11 -0600

#2154 — Re: olcott's correct refutation of the Peter Linz HP proof (now includes Sipser Kozen)

Fromolcott <NoOne@NoWhere.com>
Date2020-12-08 15:19 -0600
SubjectRe: olcott's correct refutation of the Peter Linz HP proof (now includes Sipser Kozen)
Message-ID<GLydnXG7m55bcFLCnZ2dnUU7-KHNnZ2d@giganews.com>
On 12/8/2020 2:27 PM, Kaz Kylheku wrote:
> On 2020-12-08, olcott <NoOne@NoWhere.com> wrote:
>> On 12/6/2020 12:06 PM, Mostowski Collapse wrote:
>>>
>>> There are dozen and dozen University professors
>>> that need to teach something, do scaffold some
>>> script, maybe they even don't do it
>>>
>>> by themselves, more their assistants. Then
>>> maybe such a script becomes a book, carrying
>>> all the errors from the script into the
>>>
>>> book. What do you expect. That every book
>>> is error free? Then there is the problem
>>> that a moron like you interprets the script.
>>>
>> Both the Sipser proof and the Kozen proof succumb to my refutation of
>> Linz.
> 
> Correction; they succumb to the refutation you don't quite yet have, but
> supposedly will have this coming weekend.
> 
> You've not yet shown Halts() function returning the correct value, only
> the overall machine detecting runaway recursion (which causes he
> issue that Halts never returns, thereby failing to decide).
> 
> Minor interface problem, but important.
> 

Yes I will keep working on it yet we still need to keep the concept that 
a return value from the operating system <is> a valid return value and 
this is proven when the system terminates the execution of a program for 
a divide by zero error.

The alternative approach would be a try/catch block:
int main()
{
   try  // calls the halt decider
     H_Hat((u32)H_Hat);
   catch
     OutputString("Terminated because of infinite execution");
}


-- 
Copyright 2020 Pete Olcott

"Great spirits have always encountered violent opposition from mediocre 
minds." Einstein

[toc] | [next] | [standalone]


#2156

FromKaz Kylheku <563-365-8930@kylheku.com>
Date2020-12-08 21:39 +0000
Message-ID<20201208132638.228@kylheku.com>
In reply to#2154
On 2020-12-08, olcott <NoOne@NoWhere.com> wrote:
> On 12/8/2020 2:27 PM, Kaz Kylheku wrote:
>> On 2020-12-08, olcott <NoOne@NoWhere.com> wrote:
>>> On 12/6/2020 12:06 PM, Mostowski Collapse wrote:
>>>>
>>>> There are dozen and dozen University professors
>>>> that need to teach something, do scaffold some
>>>> script, maybe they even don't do it
>>>>
>>>> by themselves, more their assistants. Then
>>>> maybe such a script becomes a book, carrying
>>>> all the errors from the script into the
>>>>
>>>> book. What do you expect. That every book
>>>> is error free? Then there is the problem
>>>> that a moron like you interprets the script.
>>>>
>>> Both the Sipser proof and the Kozen proof succumb to my refutation of
>>> Linz.
>> 
>> Correction; they succumb to the refutation you don't quite yet have, but
>> supposedly will have this coming weekend.
>> 
>> You've not yet shown Halts() function returning the correct value, only
>> the overall machine detecting runaway recursion (which causes he
>> issue that Halts never returns, thereby failing to decide).
>> 
>> Minor interface problem, but important.
>> 
>
> Yes I will keep working on it yet we still need to keep the concept that 
> a return value from the operating system <is> a valid return value and 
> this is proven when the system terminates the execution of a program for 
> a divide by zero error.

I don't quite agree. If a program terminates due to a fatal condition,
that is called an abnormal termination. It has an associated termination
status, which is unsuccessful. Though that is valid,  it is different and
distinguishable from a normal termination which is unsuccessful.

A halting decider program might use a successful normal termination
to say "yes". It might use an usuccessful normal termination to say
"no".

E.g. this program terminates normally if Halts returns, and indicates
success or failure:

  #include <stdlib.h>

  int main(void)
  {
     if (Halts(whatever, whatever))
        return EXIT_SUCCESS;
     else
        return EXIT_FAILURE;
  }

If Halts hits a division by zero, the termination is neither of these
cases; it is abnormal.

If the caller which invokes the program detects a failed termination,
it must distinguish the normal versus abnormal case; it must not assume
that the decider decided "No".

-- 
TXR Programming Language: http://nongnu.org/txr

[toc] | [prev] | [next] | [standalone]


#2158

Fromolcott <NoOne@NoWhere.com>
Date2020-12-08 16:02 -0600
Message-ID<2pmdnTCN2O2VZVLCnZ2dnUU7-W_NnZ2d@giganews.com>
In reply to#2156
On 12/8/2020 3:39 PM, Kaz Kylheku wrote:
> On 2020-12-08, olcott <NoOne@NoWhere.com> wrote:
>> On 12/8/2020 2:27 PM, Kaz Kylheku wrote:
>>> On 2020-12-08, olcott <NoOne@NoWhere.com> wrote:
>>>> On 12/6/2020 12:06 PM, Mostowski Collapse wrote:
>>>>>
>>>>> There are dozen and dozen University professors
>>>>> that need to teach something, do scaffold some
>>>>> script, maybe they even don't do it
>>>>>
>>>>> by themselves, more their assistants. Then
>>>>> maybe such a script becomes a book, carrying
>>>>> all the errors from the script into the
>>>>>
>>>>> book. What do you expect. That every book
>>>>> is error free? Then there is the problem
>>>>> that a moron like you interprets the script.
>>>>>
>>>> Both the Sipser proof and the Kozen proof succumb to my refutation of
>>>> Linz.
>>>
>>> Correction; they succumb to the refutation you don't quite yet have, but
>>> supposedly will have this coming weekend.
>>>
>>> You've not yet shown Halts() function returning the correct value, only
>>> the overall machine detecting runaway recursion (which causes he
>>> issue that Halts never returns, thereby failing to decide).
>>>
>>> Minor interface problem, but important.
>>>
>>
>> Yes I will keep working on it yet we still need to keep the concept that
>> a return value from the operating system <is> a valid return value and
>> this is proven when the system terminates the execution of a program for
>> a divide by zero error.
> 
> I don't quite agree. If a program terminates due to a fatal condition,
> that is called an abnormal termination. It has an associated termination
> status, which is unsuccessful. Though that is valid,  it is different and
> distinguishable from a normal termination which is unsuccessful.
> 
> A halting decider program might use a successful normal termination
> to say "yes". It might use an usuccessful normal termination to say
> "no".
> 
> E.g. this program terminates normally if Halts returns, and indicates
> success or failure:
> 
>    #include <stdlib.h>
> 
>    int main(void)
>    {
>       if (Halts(whatever, whatever))
>          return EXIT_SUCCESS;
>       else
>          return EXIT_FAILURE;
>    }
> 
> If Halts hits a division by zero, the termination is neither of these
> cases; it is abnormal.
> 
> If the caller which invokes the program detects a failed termination,
> it must distinguish the normal versus abnormal case; it must not assume
> that the decider decided "No".
> 

I must apply the global halt decider to this case:
int main()
{
   H_Hat((u32)H_Hat);
}

Non-halting is a fatal error like this one:
int main()
{
   int X = 5 / 0;
}




-- 
Copyright 2020 Pete Olcott

"Great spirits have always encountered violent opposition from mediocre 
minds." Einstein

[toc] | [prev] | [next] | [standalone]


#2159

Fromolcott <NoOne@NoWhere.com>
Date2020-12-08 16:11 -0600
Message-ID<S-OdnSphXeOKZ1LCnZ2dnUU7-V3NnZ2d@giganews.com>
In reply to#2158
On 12/8/2020 4:02 PM, olcott wrote:
> On 12/8/2020 3:39 PM, Kaz Kylheku wrote:
>> On 2020-12-08, olcott <NoOne@NoWhere.com> wrote:
>>> On 12/8/2020 2:27 PM, Kaz Kylheku wrote:
>>>> On 2020-12-08, olcott <NoOne@NoWhere.com> wrote:
>>>>> On 12/6/2020 12:06 PM, Mostowski Collapse wrote:
>>>>>>
>>>>>> There are dozen and dozen University professors
>>>>>> that need to teach something, do scaffold some
>>>>>> script, maybe they even don't do it
>>>>>>
>>>>>> by themselves, more their assistants. Then
>>>>>> maybe such a script becomes a book, carrying
>>>>>> all the errors from the script into the
>>>>>>
>>>>>> book. What do you expect. That every book
>>>>>> is error free? Then there is the problem
>>>>>> that a moron like you interprets the script.
>>>>>>
>>>>> Both the Sipser proof and the Kozen proof succumb to my refutation of
>>>>> Linz.
>>>>
>>>> Correction; they succumb to the refutation you don't quite yet have, 
>>>> but
>>>> supposedly will have this coming weekend.
>>>>
>>>> You've not yet shown Halts() function returning the correct value, only
>>>> the overall machine detecting runaway recursion (which causes he
>>>> issue that Halts never returns, thereby failing to decide).
>>>>
>>>> Minor interface problem, but important.
>>>>
>>>
>>> Yes I will keep working on it yet we still need to keep the concept that
>>> a return value from the operating system <is> a valid return value and
>>> this is proven when the system terminates the execution of a program for
>>> a divide by zero error.
>>
>> I don't quite agree. If a program terminates due to a fatal condition,
>> that is called an abnormal termination. It has an associated termination
>> status, which is unsuccessful. Though that is valid,  it is different and
>> distinguishable from a normal termination which is unsuccessful.
>>
>> A halting decider program might use a successful normal termination
>> to say "yes". It might use an usuccessful normal termination to say
>> "no".
>>
>> E.g. this program terminates normally if Halts returns, and indicates
>> success or failure:
>>
>>    #include <stdlib.h>
>>
>>    int main(void)
>>    {
>>       if (Halts(whatever, whatever))
>>          return EXIT_SUCCESS;
>>       else
>>          return EXIT_FAILURE;
>>    }
>>
>> If Halts hits a division by zero, the termination is neither of these
>> cases; it is abnormal.
>>
>> If the caller which invokes the program detects a failed termination,
>> it must distinguish the normal versus abnormal case; it must not assume
>> that the decider decided "No".
>>
> 
> I must apply the global halt decider to this case:
> int main()
> {
>    H_Hat((u32)H_Hat);
> }
> 
> Non-halting is a fatal error like this one:
> int main()
> {
>    int X = 5 / 0;
> }

I can do this, it is like a try-catch statement:
int main()
{
   u32 Input_Halts = Halts((u32)H_Hat, (u32)H_Hat);
   Output("Input_Halts =", Input_Halts);
}


-- 
Copyright 2020 Pete Olcott

"Great spirits have always encountered violent opposition from mediocre 
minds." Einstein

[toc] | [prev] | [standalone]


Back to top | Article view | comp.software-eng


csiph-web