On 1/30/2024 8:21 PM, Richard Damon wrote:
On 1/30/24 10:46 AM, olcott wrote:
On 1/30/2024 9:38 AM, immibis wrote:
On 1/30/24 03:17, olcott wrote:
On 1/29/2024 6:48 PM, Richard Damon wrote:
On 1/29/24 8:53 AM, olcott wrote:Yet when H is asked this question it is an entirely different
On 1/29/2024 12:59 AM, Lawrence D'Oliveiro wrote:
On Sun, 28 Jan 2024 09:20:46 -0600, olcott wrote:
... professor Hehner proves my 2004 claim that the
halting problem is an ill-formed question.
Doesn’t matter how you phrase it, the fact remains that there is no >>>>>>>> logically self-consistent answer to the problem. That’s what Turing >>>>>>>> proved, and you have done nothing to change that.
Likewise there is no logically consistent answer to this question: >>>>>>> Is this sentence true or false: "this sentence is not true"?
It is undecidable because the question itself is incorrect.
Every yes/no question defined to have no correct yes/no answer is an >>>>>>> incorrect question.
And the question, "Does the Computation defined by this input
Halt?" always has a correct yes/no answer, so is a CORRECT question. >>>>>
question
Wrong
because the context of who is asked the question
DOES CHANGE THE MEANING OF THE QUESTION.
Wrong in mathematics
It is necessarily always right it is the case that math
guys hardly know any linguistics at all thus mistake their
own ignorance for knowledge.
The x86 machine code of D proves that it specifies recursive
simulation to H.
For this H, it specifies FINITE recursive simulation to H, so a
HALTING behavior.
When one understands that H is always correct to abort any
simulation that cannot possibly stop running unless aborted
01 int D(ptr x) // ptr is pointer to int function
02 {
03 int Halt_Status = H(x, x);
04 if (Halt_Status)
05 HERE: goto HERE;
06 return Halt_Status;
07 }
08
09 void main()
10 {
11 H(D,D);
12 }
As every H specified by the above template must do then each
and every element of this infinite set is correct to abort
its simulation and reject its input D as non-halting.
On 1/30/2024 8:21 PM, Richard Damon wrote:
On 1/30/24 10:46 AM, olcott wrote:
On 1/30/2024 9:38 AM, immibis wrote:
On 1/30/24 03:17, olcott wrote:
On 1/29/2024 6:48 PM, Richard Damon wrote:
On 1/29/24 8:53 AM, olcott wrote:Yet when H is asked this question it is an entirely different
On 1/29/2024 12:59 AM, Lawrence D'Oliveiro wrote:
On Sun, 28 Jan 2024 09:20:46 -0600, olcott wrote:
... professor Hehner proves my 2004 claim that the
halting problem is an ill-formed question.
Doesn’t matter how you phrase it, the fact remains that there is no >>>>>>>> logically self-consistent answer to the problem. That’s what Turing >>>>>>>> proved, and you have done nothing to change that.
Likewise there is no logically consistent answer to this question: >>>>>>> Is this sentence true or false: "this sentence is not true"?
It is undecidable because the question itself is incorrect.
Every yes/no question defined to have no correct yes/no answer is an >>>>>>> incorrect question.
And the question, "Does the Computation defined by this input
Halt?" always has a correct yes/no answer, so is a CORRECT question. >>>>>
question
Wrong
because the context of who is asked the question
DOES CHANGE THE MEANING OF THE QUESTION.
Wrong in mathematics
It is necessarily always right it is the case that math
guys hardly know any linguistics at all thus mistake their
own ignorance for knowledge.
The x86 machine code of D proves that it specifies recursive
simulation to H.
For this H, it specifies FINITE recursive simulation to H, so a
HALTING behavior.
When one understands that H is always correct to abort any
simulation that cannot possibly stop running unless aborted
01 int D(ptr x) // ptr is pointer to int function
02 {
03 int Halt_Status = H(x, x);
04 if (Halt_Status)
05 HERE: goto HERE;
06 return Halt_Status;
07 }
08
09 void main()
10 {
11 H(D,D);
12 }
As every H specified by the above template must do then each
and every element of this infinite set is correct to abort
its simulation and reject its input D as non-halting.
On 1/30/2024 8:21 PM, Richard Damon wrote:
On 1/30/24 10:46 AM, olcott wrote:
On 1/30/2024 9:38 AM, immibis wrote:
On 1/30/24 03:17, olcott wrote:
On 1/29/2024 6:48 PM, Richard Damon wrote:
On 1/29/24 8:53 AM, olcott wrote:Yet when H is asked this question it is an entirely different
On 1/29/2024 12:59 AM, Lawrence D'Oliveiro wrote:
On Sun, 28 Jan 2024 09:20:46 -0600, olcott wrote:
... professor Hehner proves my 2004 claim that the
halting problem is an ill-formed question.
Doesn’t matter how you phrase it, the fact remains that there is no >>>>>>>> logically self-consistent answer to the problem. That’s what Turing >>>>>>>> proved, and you have done nothing to change that.
Likewise there is no logically consistent answer to this question: >>>>>>> Is this sentence true or false: "this sentence is not true"?
It is undecidable because the question itself is incorrect.
Every yes/no question defined to have no correct yes/no answer is an >>>>>>> incorrect question.
And the question, "Does the Computation defined by this input
Halt?" always has a correct yes/no answer, so is a CORRECT question. >>>>>
question
Wrong
because the context of who is asked the question
DOES CHANGE THE MEANING OF THE QUESTION.
Wrong in mathematics
It is necessarily always right it is the case that math
guys hardly know any linguistics at all thus mistake their
own ignorance for knowledge.
The x86 machine code of D proves that it specifies recursive
simulation to H.
For this H, it specifies FINITE recursive simulation to H, so a
HALTING behavior.
When one understands that H is always correct to abort any
simulation that cannot possibly stop running unless aborted
01 int D(ptr x) // ptr is pointer to int function
02 {
03 int Halt_Status = H(x, x);
04 if (Halt_Status)
05 HERE: goto HERE;
06 return Halt_Status;
07 }
08
09 void main()
10 {
11 H(D,D);
12 }
As every H specified by the above template must do then each
and every element of this infinite set is correct to abort
its simulation and reject its input D as non-halting.
On 1/31/2024 6:25 AM, immibis wrote:
On 1/31/24 04:53, olcott wrote:
On 1/30/2024 8:21 PM, Richard Damon wrote:
On 1/30/24 10:46 AM, olcott wrote:
On 1/30/2024 9:38 AM, immibis wrote:
On 1/30/24 03:17, olcott wrote:
On 1/29/2024 6:48 PM, Richard Damon wrote:
On 1/29/24 8:53 AM, olcott wrote:
On 1/29/2024 12:59 AM, Lawrence D'Oliveiro wrote:
On Sun, 28 Jan 2024 09:20:46 -0600, olcott wrote:
... professor Hehner proves my 2004 claim that the
halting problem is an ill-formed question.
Doesn’t matter how you phrase it, the fact remains that there >>>>>>>>>> is no
logically self-consistent answer to the problem. That’s what >>>>>>>>>> Turing
proved, and you have done nothing to change that.
Likewise there is no logically consistent answer to this question: >>>>>>>>> Is this sentence true or false: "this sentence is not true"? >>>>>>>>> It is undecidable because the question itself is incorrect.
Every yes/no question defined to have no correct yes/no answer >>>>>>>>> is an
incorrect question.
And the question, "Does the Computation defined by this input
Halt?" always has a correct yes/no answer, so is a CORRECT
question.
Yet when H is asked this question it is an entirely different
question
Wrong
because the context of who is asked the question
DOES CHANGE THE MEANING OF THE QUESTION.
Wrong in mathematics
It is necessarily always right it is the case that math
guys hardly know any linguistics at all thus mistake their
own ignorance for knowledge.
The x86 machine code of D proves that it specifies recursive
simulation to H.
For this H, it specifies FINITE recursive simulation to H, so a
HALTING behavior.
When one understands that H is always correct to abort any
simulation that cannot possibly stop running unless aborted
01 int D(ptr x) // ptr is pointer to int function
02 {
03 int Halt_Status = H(x, x);
04 if (Halt_Status)
05 HERE: goto HERE;
06 return Halt_Status;
07 }
08
09 void main()
10 {
11 H(D,D);
12 }
As every H specified by the above template must do then each
and every element of this infinite set is correct to abort
its simulation and reject its input D as non-halting.
When one understands that a non-halting machine has an infinite
execution sequence and a halting machine has a finite execution
sequence, one sees that you are wrong.
Below I reference an infinite set of simulating termination
analyzers
On 1/31/2024 6:30 AM, Richard Damon wrote:
On 1/30/24 10:53 PM, olcott wrote:
On 1/30/2024 8:21 PM, Richard Damon wrote:
On 1/30/24 10:46 AM, olcott wrote:
On 1/30/2024 9:38 AM, immibis wrote:
On 1/30/24 03:17, olcott wrote:
On 1/29/2024 6:48 PM, Richard Damon wrote:
On 1/29/24 8:53 AM, olcott wrote:
On 1/29/2024 12:59 AM, Lawrence D'Oliveiro wrote:
On Sun, 28 Jan 2024 09:20:46 -0600, olcott wrote:
... professor Hehner proves my 2004 claim that the
halting problem is an ill-formed question.
Doesn’t matter how you phrase it, the fact remains that there >>>>>>>>>> is no
logically self-consistent answer to the problem. That’s what >>>>>>>>>> Turing
proved, and you have done nothing to change that.
Likewise there is no logically consistent answer to this question: >>>>>>>>> Is this sentence true or false: "this sentence is not true"? >>>>>>>>> It is undecidable because the question itself is incorrect.
Every yes/no question defined to have no correct yes/no answer >>>>>>>>> is an
incorrect question.
And the question, "Does the Computation defined by this input
Halt?" always has a correct yes/no answer, so is a CORRECT
question.
Yet when H is asked this question it is an entirely different
question
Wrong
because the context of who is asked the question
DOES CHANGE THE MEANING OF THE QUESTION.
Wrong in mathematics
It is necessarily always right it is the case that math
guys hardly know any linguistics at all thus mistake their
own ignorance for knowledge.
The x86 machine code of D proves that it specifies recursive
simulation to H.
For this H, it specifies FINITE recursive simulation to H, so a
HALTING behavior.
When one understands that H is always correct to abort any
simulation that cannot possibly stop running unless aborted
01 int D(ptr x) // ptr is pointer to int function
02 {
03 int Halt_Status = H(x, x);
04 if (Halt_Status)
05 HERE: goto HERE;
06 return Halt_Status;
07 }
08
09 void main()
10 {
11 H(D,D);
12 }
As every H specified by the above template must do then each
and every element of this infinite set is correct to abort
its simulation and reject its input D as non-halting.
No, H is only correct to abort and report non-halting, if that exact
same program it was looking at (using the exact same H as that H was)
will not halt when run.
That you can't seem to fully grasp the concept of a program
template is your own short-coming and not mine.
On 1/31/2024 3:38 AM, Fred. Zwarts wrote:
Op 31.jan.2024 om 04:53 schreef olcott:
On 1/30/2024 8:21 PM, Richard Damon wrote:
On 1/30/24 10:46 AM, olcott wrote:
On 1/30/2024 9:38 AM, immibis wrote:
On 1/30/24 03:17, olcott wrote:
On 1/29/2024 6:48 PM, Richard Damon wrote:
On 1/29/24 8:53 AM, olcott wrote:
On 1/29/2024 12:59 AM, Lawrence D'Oliveiro wrote:
On Sun, 28 Jan 2024 09:20:46 -0600, olcott wrote:
... professor Hehner proves my 2004 claim that the
halting problem is an ill-formed question.
Doesn’t matter how you phrase it, the fact remains that there >>>>>>>>>> is no
logically self-consistent answer to the problem. That’s what >>>>>>>>>> Turing
proved, and you have done nothing to change that.
Likewise there is no logically consistent answer to this question: >>>>>>>>> Is this sentence true or false: "this sentence is not true"? >>>>>>>>> It is undecidable because the question itself is incorrect.
Every yes/no question defined to have no correct yes/no answer >>>>>>>>> is an
incorrect question.
And the question, "Does the Computation defined by this input
Halt?" always has a correct yes/no answer, so is a CORRECT
question.
Yet when H is asked this question it is an entirely different
question
Wrong
because the context of who is asked the question
DOES CHANGE THE MEANING OF THE QUESTION.
Wrong in mathematics
It is necessarily always right it is the case that math
guys hardly know any linguistics at all thus mistake their
own ignorance for knowledge.
The x86 machine code of D proves that it specifies recursive
simulation to H.
For this H, it specifies FINITE recursive simulation to H, so a
HALTING behavior.
When one understands that H is always correct to abort any
simulation that cannot possibly stop running unless aborted
01 int D(ptr x) // ptr is pointer to int function
02 {
03 int Halt_Status = H(x, x);
04 if (Halt_Status)
05 HERE: goto HERE;
06 return Halt_Status;
07 }
08
09 void main()
10 {
11 H(D,D);
12 }
As every H specified by the above template must do then each
and every element of this infinite set is correct to abort
its simulation and reject its input D as non-halting.
No, Han aborts is simulation, so it is not necessary to abort Dan, which
Below I reference an infinite set of simulating termination
analyzers that each correctly aborts its simulation of D
and correctly rejects D as non-halting.
When one understands that simulating termination analyzer H
is always correct to abort any simulation that cannot possibly
stop running unless aborted:
01 int D(ptr x) // ptr is pointer to int function
02 {
03 int Halt_Status = H(x, x);
04 if (Halt_Status)
05 HERE: goto HERE;
06 return Halt_Status;
07 }
08
09 void main()
10 {
11 H(D,D);
12 }
Then every simulating termination analyzer H specified by
the above template correctly aborts its simulation of D
and correctly rejects D as non-halting.
Pages 661 to 696 of Halt7.c specify the H that does this https://github.com/plolcott/x86utm/blob/master/Halt7.c
On 1/31/24 16:40, olcott wrote:
On 1/31/2024 6:30 AM, Richard Damon wrote:
On 1/30/24 10:53 PM, olcott wrote:
On 1/30/2024 8:21 PM, Richard Damon wrote:
On 1/30/24 10:46 AM, olcott wrote:
On 1/30/2024 9:38 AM, immibis wrote:
On 1/30/24 03:17, olcott wrote:
On 1/29/2024 6:48 PM, Richard Damon wrote:
On 1/29/24 8:53 AM, olcott wrote:
On 1/29/2024 12:59 AM, Lawrence D'Oliveiro wrote:
On Sun, 28 Jan 2024 09:20:46 -0600, olcott wrote:
... professor Hehner proves my 2004 claim that the
halting problem is an ill-formed question.
Doesn’t matter how you phrase it, the fact remains that there >>>>>>>>>>> is no
logically self-consistent answer to the problem. That’s what >>>>>>>>>>> Turing
proved, and you have done nothing to change that.
Likewise there is no logically consistent answer to this
question:
Is this sentence true or false: "this sentence is not true"? >>>>>>>>>> It is undecidable because the question itself is incorrect. >>>>>>>>>>
Every yes/no question defined to have no correct yes/no answer >>>>>>>>>> is an
incorrect question.
And the question, "Does the Computation defined by this input >>>>>>>>> Halt?" always has a correct yes/no answer, so is a CORRECT
question.
Yet when H is asked this question it is an entirely different
question
Wrong
because the context of who is asked the question
DOES CHANGE THE MEANING OF THE QUESTION.
Wrong in mathematics
It is necessarily always right it is the case that math
guys hardly know any linguistics at all thus mistake their
own ignorance for knowledge.
The x86 machine code of D proves that it specifies recursive
simulation to H.
For this H, it specifies FINITE recursive simulation to H, so a
HALTING behavior.
When one understands that H is always correct to abort any
simulation that cannot possibly stop running unless aborted
01 int D(ptr x) // ptr is pointer to int function
02 {
03 int Halt_Status = H(x, x);
04 if (Halt_Status)
05 HERE: goto HERE;
06 return Halt_Status;
07 }
08
09 void main()
10 {
11 H(D,D);
12 }
As every H specified by the above template must do then each
and every element of this infinite set is correct to abort
its simulation and reject its input D as non-halting.
No, H is only correct to abort and report non-halting, if that exact
same program it was looking at (using the exact same H as that H was)
will not halt when run.
That you can't seem to fully grasp the concept of a program
template is your own short-coming and not mine.
Halting is about programs, not program templates. A program halts or
doesn't. A program template does neither because it is just a template.
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 307 |
Nodes: | 16 (2 / 14) |
Uptime: | 45:20:12 |
Calls: | 6,910 |
Files: | 12,377 |
Messages: | 5,429,445 |