Liste des Groupes | Revenir à theory |
olcott <polcott333@gmail.com> wrote:<MIT Professor Sipser agreed to ONLY these verbatim words 10/13/2022>On 7/27/2024 4:16 PM, Alan Mackenzie wrote:olcott <polcott333@gmail.com> wrote:On 7/27/2024 3:20 PM, Alan Mackenzie wrote:olcott <polcott333@gmail.com> wrote:On 7/27/2024 1:14 PM, Alan Mackenzie wrote:olcott <polcott333@gmail.com> wrote:Stopping running is not the same as halting.
DDD emulated by HHH stops running when its emulation has been aborted.
This is not the same as reaching its ret instruction and terminating
normally (AKA halting).I think you're wrong, here. All your C programs are a stand in
for turing machines. A turing machine is either running or
halted. There is no third state "aborted".Until you take the conventional ideas of
(a) UTM
(b) TM Description
(c) Decider
and combine them together to become a simulating partial halt decider.Where does the notion of "aborted", as being distinct from halted, come
from?After all of these years and you don't get that?"Aborted" being distinct from halted is an incoherent notion. It isn't
consistent with turing machines. I was hoping you could give a
justification for it.A simulating partial halt decider can stop simulating
its input when it detects a non-halting behavior pattern.
This does not count as the input halting.Says who? Well, OK, it would be the machine halting, not the input, but
that's a small point.void Infinite_Recursion()[ .... ]
{
Infinite_Recursion();
}
Do you understand that HHH(Infinite_Recursion) correctlyThere's nothing wrong with my understanding, but I'm not sure what
implements this criteria for the above input?
"implementing a criterion (not "criteria")" means,
Les messages affichés proviennent d'usenet.