Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.theory > #24537 > unrolled thread
| Started by | olcott <NoOne@NoWhere.com> |
|---|---|
| First post | 2020-10-27 14:30 -0500 |
| Last post | 2020-10-29 19:40 +0100 |
| Articles | 20 on this page of 145 — 15 participants |
Back to article view | Back to comp.theory
Architectural design of a halting problem solution olcott <NoOne@NoWhere.com> - 2020-10-27 14:30 -0500
Re: Architectural design of a halting problem solution André G. Isaak <agisaak@gm.invalid> - 2020-10-27 13:46 -0600
Re: Architectural design of a halting problem solution olcott <NoOne@NoWhere.com> - 2020-10-27 15:02 -0500
Re: Architectural design of a halting problem solution Mike Terry <news.dead.person.stones@darjeeling.plus.com> - 2020-10-27 20:03 +0000
Re: Architectural design of a halting problem solution olcott <NoOne@NoWhere.com> - 2020-10-27 15:13 -0500
Re: Architectural design of a halting problem solution André G. Isaak <agisaak@gm.invalid> - 2020-10-27 14:34 -0600
Re: Architectural design of a halting problem solution Mike Terry <news.dead.person.stones@darjeeling.plus.com> - 2020-10-27 21:11 +0000
Re: Architectural design of a halting problem solution olcott <NoOne@NoWhere.com> - 2020-10-27 16:27 -0500
Re: Architectural design of a halting problem solution Mike Terry <news.dead.person.stones@darjeeling.plus.com> - 2020-10-27 21:33 +0000
Re: Architectural design of a halting problem solution olcott <NoOne@NoWhere.com> - 2020-10-27 16:57 -0500
Re: Architectural design of a halting problem solution Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2020-10-27 14:44 -0700
Re: Architectural design of a halting problem solution olcott <NoOne@NoWhere.com> - 2020-10-27 16:54 -0500
Re: Architectural design of a halting problem solution Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2020-10-27 15:07 -0700
Re: Architectural design of a halting problem solution olcott <NoOne@NoWhere.com> - 2020-10-27 18:43 -0500
Re: Architectural design of a halting problem solution Richard Damon <Richard@Damon-Family.org> - 2020-10-27 21:45 -0400
Re: Architectural design of a halting problem solution olcott <NoOne@NoWhere.com> - 2020-10-27 21:28 -0500
Re: Architectural design of a halting problem solution Richard Damon <Richard@Damon-Family.org> - 2020-10-27 22:48 -0400
Re: Architectural design of a halting problem solution olcott <NoOne@NoWhere.com> - 2020-10-27 21:55 -0500
Re: Architectural design of a halting problem solution Richard Damon <Richard@Damon-Family.org> - 2020-10-28 09:04 -0400
Re: Architectural design of a halting problem solution Mostowski Collapse <janburse@fastmail.fm> - 2020-10-28 14:13 +0100
Re: Architectural design of a halting problem solution David Brown <david.brown@hesbynett.no> - 2020-10-28 15:12 +0100
Re: Architectural design of a halting problem solution Mostowski Collapse <janburse@fastmail.fm> - 2020-10-28 14:13 +0100
Re: Architectural design of a halting problem solution olcott <NoOne@NoWhere.com> - 2020-10-28 18:18 -0500
Re: Architectural design of a halting problem solution Alan Mackenzie <acm@muc.de> - 2020-10-28 09:38 +0000
Re: Architectural design of a halting problem solution olcott <NoOne@NoWhere.com> - 2020-10-28 17:54 -0500
Re: Architectural design of a halting problem solution Alan Mackenzie <acm@muc.de> - 2020-10-29 06:59 +0000
Re: Architectural design of a halting problem solution olcott <NoOne@NoWhere.com> - 2020-10-29 07:28 -0500
Re: Architectural design of a halting problem solution olcott <NoOne@NoWhere.com> - 2020-10-29 07:35 -0500
Re: Architectural design of a halting problem solution olcott <NoOne@NoWhere.com> - 2020-10-27 16:23 -0500
Re: Architectural design of a halting problem solution André G. Isaak <agisaak@gm.invalid> - 2020-10-27 22:49 -0600
Re: Architectural design of a halting problem solution olcott <NoOne@NoWhere.com> - 2020-10-28 00:05 -0500
Re: Architectural design of a halting problem solution André G. Isaak <agisaak@gm.invalid> - 2020-10-27 23:25 -0600
Re: Architectural design of a halting problem solution olcott <NoOne@NoWhere.com> - 2020-10-28 00:31 -0500
Re: Architectural design of a halting problem solution André G. Isaak <agisaak@gm.invalid> - 2020-10-27 23:55 -0600
Re: Architectural design of a halting problem solution olcott <NoOne@NoWhere.com> - 2020-10-28 17:50 -0500
Re: Architectural design of a halting problem solution Ben Bacarisse <ben.usenet@bsb.me.uk> - 2020-10-28 23:27 +0000
Re: Architectural design of a halting problem solution olcott <NoOne@NoWhere.com> - 2020-10-28 21:09 -0500
Re: Architectural design of a halting problem solution André G. Isaak <agisaak@gm.invalid> - 2020-10-29 00:45 -0600
Re: Architectural design of a halting problem solution olcott <NoOne@NoWhere.com> - 2020-10-29 07:18 -0500
Re: Architectural design of a halting problem solution André G. Isaak <agisaak@gm.invalid> - 2020-10-29 07:30 -0600
Re: Architectural design of a halting problem solution olcott <NoOne@NoWhere.com> - 2020-10-29 11:05 -0500
Re: Architectural design of a halting problem solution André G. Isaak <agisaak@gm.invalid> - 2020-10-29 10:55 -0600
Re: Architectural design of a halting problem solution olcott <NoOne@NoWhere.com> - 2020-10-29 12:52 -0500
Re: Architectural design of a halting problem solution André G. Isaak <agisaak@gm.invalid> - 2020-10-29 11:58 -0600
Re: Architectural design of a halting problem solution olcott <NoOne@NoWhere.com> - 2020-10-29 13:25 -0500
Re: Architectural design of a halting problem solution André G. Isaak <agisaak@gm.invalid> - 2020-10-29 12:56 -0600
Re: Architectural design of a halting problem solution olcott <NoOne@NoWhere.com> - 2020-10-29 14:13 -0500
Re: Architectural design of a halting problem solution André G. Isaak <agisaak@gm.invalid> - 2020-10-29 13:50 -0600
Re: Architectural design of a halting problem solution olcott <NoOne@NoWhere.com> - 2020-10-29 15:18 -0500
Re: Architectural design of a halting problem solution André G. Isaak <agisaak@gm.invalid> - 2020-10-29 14:52 -0600
Re: Architectural design of a halting problem solution olcott <NoOne@NoWhere.com> - 2020-10-29 16:18 -0500
Re: Architectural design of a halting problem solution André G. Isaak <agisaak@gm.invalid> - 2020-10-30 08:53 -0600
Re: Architectural design of a halting problem solution olcott <NoOne@NoWhere.com> - 2020-10-30 10:55 -0500
Re: Architectural design of a halting problem solution André G. Isaak <agisaak@gm.invalid> - 2020-10-31 08:28 -0600
Re: Architectural design of a halting problem solution olcott <NoOne@NoWhere.com> - 2020-10-31 09:53 -0500
Re: Architectural design of a halting problem solution André G. Isaak <agisaak@gm.invalid> - 2020-10-31 09:23 -0600
Re: Architectural design of a halting problem solution olcott <NoOne@NoWhere.com> - 2020-10-31 10:35 -0500
Re: Architectural design of a halting problem solution André G. Isaak <agisaak@gm.invalid> - 2020-10-31 09:44 -0600
Re: Architectural design of a halting problem solution olcott <NoOne@NoWhere.com> - 2020-10-31 11:03 -0500
Re: Architectural design of a halting problem solution André G. Isaak <agisaak@gm.invalid> - 2020-11-01 07:46 -0700
Re: Architectural design of a halting problem solution olcott <NoOne@NoWhere.com> - 2020-11-01 12:12 -0600
Re: Architectural design of a halting problem solution olcott <NoOne@NoWhere.com> - 2020-11-01 12:45 -0600
Re: Architectural design of a halting problem solution Richard Damon <Richard@Damon-Family.org> - 2020-10-31 14:46 -0400
Re: Architectural design of a halting problem solution olcott <NoOne@NoWhere.com> - 2020-10-31 13:57 -0500
Re: Architectural design of a halting problem solution Richard Damon <Richard@Damon-Family.org> - 2020-10-31 16:00 -0400
Re: Architectural design of a halting problem solution olcott <NoOne@NoWhere.com> - 2020-10-31 15:34 -0500
Re: Architectural design of a halting problem solution olcott <NoOne@NoWhere.com> - 2020-10-31 15:42 -0500
Re: Architectural design of a halting problem solution Alan Mackenzie <acm@muc.de> - 2020-10-31 21:07 +0000
Re: Architectural design of a halting problem solution olcott <NoOne@NoWhere.com> - 2020-10-31 16:19 -0500
Re: Architectural design of a halting problem solution Alan Mackenzie <acm@muc.de> - 2020-10-31 21:33 +0000
Re: Architectural design of a halting problem solution olcott <NoOne@NoWhere.com> - 2020-10-31 16:50 -0500
Re: Architectural design of a halting problem solution Richard Damon <Richard@Damon-Family.org> - 2020-10-31 18:31 -0400
Re: Architectural design of a halting problem solution [ Bill the auto mechanic can fix your car ] olcott <NoOne@NoWhere.com> - 2020-10-31 17:50 -0500
Re: Architectural design of a halting problem solution [ Bill the auto mechanic can fix your car ] Richard Damon <Richard@Damon-Family.org> - 2020-10-31 19:53 -0400
Re: Architectural design of a halting problem solution [ Bill the auto mechanic can fix your car ] olcott <NoOne@NoWhere.com> - 2020-10-31 19:19 -0500
Re: Architectural design of a halting problem solution [ Bill the auto mechanic can fix your car ] Richard Damon <Richard@Damon-Family.org> - 2020-10-31 21:19 -0400
Re: Architectural design of a halting problem solution [ Bill the auto mechanic can fix your car ] Richard Damon <Richard@Damon-Family.org> - 2020-10-31 22:22 -0400
Re: Architectural design of a halting problem solution [ Bill the auto mechanic can fix your car ] olcott <NoOne@NoWhere.com> - 2020-10-31 21:36 -0500
Re: Architectural design of a halting problem solution [ Bill the auto mechanic can fix your car ] olcott <NoOne@NoWhere.com> - 2020-10-31 22:18 -0500
Re: Architectural design of a halting problem solution [ Bill the auto mechanic can fix your car ] Richard Damon <Richard@Damon-Family.org> - 2020-11-01 08:19 -0500
Re: Architectural design of a halting problem solution [ Bill the auto mechanic can fix your car ] olcott <NoOne@NoWhere.com> - 2020-11-01 08:40 -0600
Re: Architectural design of a halting problem solution [ Bill the auto mechanic can fix your car ] Mike Terry <news.dead.person.stones@darjeeling.plus.com> - 2020-11-01 16:11 +0000
Re: Architectural design of a halting problem solution [ Bill the auto mechanic can fix your car ] olcott <NoOne@NoWhere.com> - 2020-11-01 12:18 -0600
Re: Architectural design of a halting problem solution [ Bill the auto mechanic can fix your car ] Mike Terry <news.dead.person.stones@darjeeling.plus.com> - 2020-11-01 19:50 +0000
Re: Architectural design of a halting problem solution [ Bill the auto mechanic can fix your car ] olcott <NoOne@NoWhere.com> - 2020-11-01 14:09 -0600
Re: Architectural design of a halting problem solution [ Bill the auto mechanic can fix your car ] olcott <NoOne@NoWhere.com> - 2020-11-01 14:38 -0600
Re: Architectural design of a halting problem solution [ Bill the auto mechanic can fix your car ] Mike Terry <news.dead.person.stones@darjeeling.plus.com> - 2020-11-01 21:32 +0000
Re: Architectural design of a halting problem solution [ Bill the auto mechanic can fix your car ] olcott <NoOne@NoWhere.com> - 2020-11-01 15:54 -0600
Re: Architectural design of a halting problem solution [ Bill the auto mechanic can fix your car ] Ben Bacarisse <ben.usenet@bsb.me.uk> - 2020-11-02 00:46 +0000
Re: Architectural design of a halting problem solution [ Bill the auto mechanic can fix your car ] olcott <NoOne@NoWhere.com> - 2020-11-01 19:05 -0600
Re: Architectural design of a halting problem solution [ Bill the auto mechanic can fix your car ] olcott <NoOne@NoWhere.com> - 2020-11-01 19:10 -0600
Re: Architectural design of a halting problem solution [ Bill the auto mechanic can fix your car ] Richard Damon <Richard@Damon-Family.org> - 2020-11-01 21:57 -0500
Re: Architectural design of a halting problem solution [ Bill the auto mechanic can fix your car ] olcott <NoOne@NoWhere.com> - 2020-11-01 22:33 -0600
Re: Architectural design of a halting problem solution [ Bill the auto mechanic can fix your car ] Richard Damon <Richard@Damon-Family.org> - 2020-11-02 08:53 -0500
Re: Architectural design of a halting problem solution [ Bill the auto mechanic can fix your car ] olcott <NoOne@NoWhere.com> - 2020-11-02 08:04 -0600
Re: Architectural design of a halting problem solution [ Bill the auto mechanic can fix your car ] Richard Damon <Richard@Damon-Family.org> - 2020-11-02 10:45 -0500
Re: Architectural design of a halting problem solution [ Bill the auto mechanic can fix your car ] Ben Bacarisse <ben.usenet@bsb.me.uk> - 2020-11-02 03:00 +0000
Re: Architectural design of a halting problem solution [ Bill the auto mechanic can fix your car ] olcott <NoOne@NoWhere.com> - 2020-11-01 22:32 -0600
Re: Architectural design of a halting problem solution [ Bill the auto mechanic can fix your car ] Ben Bacarisse <ben.usenet@bsb.me.uk> - 2020-11-02 20:55 +0000
Re: Architectural design of a halting problem solution [ Bill the auto mechanic can fix your car ] olcott <NoOne@NoWhere.com> - 2020-11-02 15:20 -0600
Re: Architectural design of a halting problem solution [ Bill the auto mechanic can fix your car ] olcott <NoOne@NoWhere.com> - 2020-11-02 16:20 -0600
Re: Architectural design of a halting problem solution [ Bill the auto mechanic can fix your car ] Ben Bacarisse <ben.usenet@bsb.me.uk> - 2020-11-02 01:16 +0000
Re: Architectural design of a halting problem solution [ Bill the auto mechanic can fix your car ] olcott <NoOne@NoWhere.com> - 2020-11-01 19:28 -0600
Re: Architectural design of a halting problem solution [ Bill the auto mechanic can fix your car ] Ben Bacarisse <ben.usenet@bsb.me.uk> - 2020-11-02 03:15 +0000
Re: Architectural design of a halting problem solution [ Adaptation of Ben's code simplifications ] olcott <NoOne@NoWhere.com> - 2020-11-01 22:20 -0600
Re: Architectural design of a halting problem solution [ Bill the auto mechanic can fix your car ] Mike Terry <news.dead.person.stones@darjeeling.plus.com> - 2020-11-02 03:02 +0000
Re: Architectural design of a halting problem solution [ one paragraph says it all ] olcott <NoOne@NoWhere.com> - 2020-11-01 21:55 -0600
Re: Architectural design of a halting problem solution [ Bill the auto mechanic can fix your car ] olcott <NoOne@NoWhere.com> - 2020-11-01 22:25 -0600
Re: Architectural design of a halting problem solution [ Bill the auto mechanic can fix your car ] Mike Terry <news.dead.person.stones@darjeeling.plus.com> - 2020-11-02 02:45 +0000
Re: Architectural design of a halting problem solution [ non halting behavior detected ] olcott <NoOne@NoWhere.com> - 2020-11-01 23:14 -0600
Re: Architectural design of a halting problem solution [ Bill the auto mechanic can fix your car ] Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2020-11-02 03:12 -0800
Re: Architectural design of a halting problem solution [ Bill the auto mechanic can fix your car ] André G. Isaak <agisaak@gm.invalid> - 2020-11-02 04:52 -0700
Re: Architectural design of a halting problem solution [ Bill the auto mechanic can fix your car ] olcott <NoOne@NoWhere.com> - 2020-11-02 08:01 -0600
Re: Architectural design of a halting problem solution [ Bill the auto mechanic can fix your car ] André G. Isaak <agisaak@gm.invalid> - 2020-11-02 08:12 -0700
Re: Architectural design of a halting problem solution [ Bill the auto mechanic can fix your car ] Richard Damon <Richard@Damon-Family.org> - 2020-11-02 10:23 -0500
Re: Architectural design of a halting problem solution [ Bill the auto mechanic can fix your car ] olcott <NoOne@NoWhere.com> - 2020-11-02 07:58 -0600
Re: Architectural design of a halting problem solution [ Bill the auto mechanic can fix your car ] olcott <NoOne@NoWhere.com> - 2020-11-01 14:02 -0600
Re: Architectural design of a halting problem solution [ Bill the auto mechanic can fix your car ] Richard Damon <Richard@Damon-Family.org> - 2020-11-01 17:52 -0500
Re: Architectural design of a halting problem solution [ Bill the auto mechanic can fix your car ] olcott <NoOne@NoWhere.com> - 2020-11-01 17:59 -0600
Re: Architectural design of a halting problem solution [ Bill the auto mechanic can fix your car ] Richard Damon <Richard@Damon-Family.org> - 2020-11-01 21:38 -0500
Re: Architectural design of a halting problem solution [ Bill the auto mechanic can fix your car ] olcott <NoOne@NoWhere.com> - 2020-11-01 21:05 -0600
Re: Architectural design of a halting problem solution [ Bill the auto mechanic can fix your car ] Mike Terry <news.dead.person.stones@darjeeling.plus.com> - 2020-11-02 00:17 +0000
Re: Architectural design of a halting problem solution [ Bill the auto mechanic can fix your car ] olcott <NoOne@NoWhere.com> - 2020-11-01 19:53 -0600
Re: Architectural design of a halting problem solution Alan Mackenzie <acm@muc.de> - 2020-11-01 08:29 +0000
Re: Architectural design of a halting problem solution Richard Damon <Richard@Damon-Family.org> - 2020-10-31 18:28 -0400
Re: Architectural design of a halting problem solution olcott <NoOne@NoWhere.com> - 2020-10-31 17:42 -0500
Re: Architectural design of a halting problem solution olcott <NoOne@NoWhere.com> - 2020-10-31 15:47 -0500
Re: Architectural design of a halting problem solution Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2020-10-29 13:13 -0700
Re: Architectural design of a halting problem solution André G. Isaak <agisaak@gm.invalid> - 2020-10-29 14:46 -0600
Re: Architectural design of a halting problem solution Andy Walker <anw@cuboid.co.uk> - 2020-10-29 14:41 +0000
Re: Architectural design of a halting problem solution olcott <NoOne@NoWhere.com> - 2020-10-29 10:29 -0500
Re: Architectural design of a halting problem solution Ben Bacarisse <ben.usenet@bsb.me.uk> - 2020-10-28 04:17 +0000
Stop crossposting you imbecil spammer (Re: Architectural design of a halting problem solution) Mostowski Collapse <janburse@fastmail.fm> - 2020-10-29 14:00 +0100
Re: Stop crossposting you imbecil spammer (Re: Architectural design of a halting problem solution) Joe Pfeiffer <pfeiffer@cs.nmsu.edu> - 2020-10-29 08:48 -0600
Re: Stop crossposting you imbecil spammer (Re: Architectural design of a halting problem solution) Mike Terry <news.dead.person.stones@darjeeling.plus.com> - 2020-10-29 15:17 +0000
Re: Stop crossposting you imbecil spammer (Re: Architectural design of a halting problem solution) olcott <NoOne@NoWhere.com> - 2020-10-29 11:13 -0500
Re: Stop crossposting you imbecil spammer (Re: Architectural design of a halting problem solution) Mike Terry <news.dead.person.stones@darjeeling.plus.com> - 2020-10-29 16:39 +0000
Re: Stop crossposting you imbecil spammer (Re: Architectural design of a halting problem solution) Manfred <noname@add.invalid> - 2020-10-29 19:20 +0100
Re: Stop crossposting you imbecil spammer (Re: Architectural design of a halting problem solution) Mike Terry <news.dead.person.stones@darjeeling.plus.com> - 2020-10-29 18:55 +0000
Re: Stop crossposting you imbecil spammer (Re: Architectural design of a halting problem solution) David Brown <david.brown@hesbynett.no> - 2020-10-30 11:02 +0100
Re: Stop crossposting you imbecil spammer (Re: Architectural design of a halting problem solution) Ben Bacarisse <ben.usenet@bsb.me.uk> - 2020-10-30 10:52 +0000
Re: Stop crossposting you imbecil spammer (Re: Architectural design of a halting problem solution) Jorgen Grahn <grahn+nntp@snipabacken.se> - 2020-10-30 19:47 +0000
Re: Stop crossposting you imbecil spammer (Re: Architectural design of a halting problem solution) Ralf Goertz <me@myprovider.invalid> - 2020-10-30 12:55 +0100
Re: Stop crossposting you imbecil spammer (Re: Architectural design of a halting problem solution) Mike Terry <news.dead.person.stones@darjeeling.plus.com> - 2020-10-30 16:33 +0000
Re: Stop crossposting you imbecil spammer (Re: Architectural design of a halting problem solution Mostowski Collapse <janburse@fastmail.fm> - 2020-10-29 19:40 +0100
Page 7 of 8 — ← Prev page 1 2 3 4 5 6 [7] 8 Next page →
| From | olcott <NoOne@NoWhere.com> |
|---|---|
| Date | 2020-11-01 21:05 -0600 |
| Subject | Re: Architectural design of a halting problem solution [ Bill the auto mechanic can fix your car ] |
| Message-ID | <sJGdnX42k8QV6gLCnZ2dnUU7-LHNnZ2d@giganews.com> |
| In reply to | #24812 |
On 11/1/2020 8:38 PM, Richard Damon wrote:
> On 11/1/20 6:59 PM, olcott wrote:
>>
>> It can be very easily verified that it did not get the answer wrong by
>> simply commenting out (removing) the code that aborts the process and
>> let the process continue.
>
> And if you do this, and H doesn't return an answer in finite time, you
> have just shown that without this, H doesn't meet it specifications.
This is only a hypothetical case so that you will understand that this
is true:
int main()
{
H_Hat(H_Hat)
invokes Aborted_Because_Non_Halting_Behavior_Detected(H_Hat, H_Hat);
which correctly decides that its first parameter would never halt unless
its execution is terminated.
> By aborting the simulation inside H, then programs that depend on H, may
> be given the wrong answer if the non-halting behavior was actually due
> to a 'bug' in H, and not non-halting behavior
>
> As was shown in my H_Hat2, which CLEARLY runs to a halt as long as H
> meets its requirements, but your H decides it is non-halting and thus
> returns the wrong answer.
void H_Hat2(u32 P)
{
if (Aborted_Because_Non_Halting_Behavior_Detected(P, P))
HALT
else
HALT
}
int main()
{
H_Hat2(H_Hat2);
invokes Aborted_Because_Non_Halting_Behavior_Detected(H_Hat2, H_Hat2);
which correctly decides that its first parameter would never halt unless
its execution is terminated.
This stuff is apparently too difficult for you to understand.
I will see if I can get an execution trace to prove my point very soon.
> YOU make the mistake of confusing the aborting of the emulation of
> H_Hat2 inside H with needing to actually abort the real machine H_Hat2.
>
> Note, if your answer, which you claim to be correct, depends on details
> inside H, when the actual behavior doesn't depend on H, then your answer
> is wrong.
>
--
Copyright 2020 Pete Olcott
"Great spirits have always encountered violent opposition from mediocre
minds." Einstein
[toc] | [prev] | [next] | [standalone]
| From | Mike Terry <news.dead.person.stones@darjeeling.plus.com> |
|---|---|
| Date | 2020-11-02 00:17 +0000 |
| Subject | Re: Architectural design of a halting problem solution [ Bill the auto mechanic can fix your car ] |
| Message-ID | <raednS7VsK-YzQLCnZ2dnUU78bGdnZ2d@brightview.co.uk> |
| In reply to | #24801 |
On 01/11/2020 22:52, Richard Damon wrote:
> On 11/1/20 3:02 PM, olcott wrote:
>> Because it only makes this decision after its input has stopped
>> executing it is not subject to the conventional
>> "do the opposite of whatever the halt decider decides"
>> trick that shows that some inputs are undecidable.
>
> Note a simple fact.
>
> It may have decided that non-halting behavior was detected, but it can
> get the answer wrong. (which it has). Note the term in the name 'Needed'.
>
> This can be proven by looking at the execution trace of the exact same
> code that was allowed to execute longer (like the outer level) and
> seeing that it ultimately did halt.
>
> THUS, the determination that the behavior was inherently non-halting is
> incorrect.
>
> Or, are you saying that the machine that ran the outer version of the
> code was incorrect?
>
> Note, you need to be able to PROVE (despite the evidence of the outer
> machine) that the inner machine actually was going to run forever with
> non-halting behavior, and at the same time that H and the code inside it
> will always halt in finite time. THAT is a bigger contradiction than
> Linz used in H_Hat.
>
I think the issue is with the interpretation of "actually was going to
run forever", which you and I and everybody else would understand, but
PO intends his suspicious looking wording to mean something quite different:
"If you took the source for H_Hat, and went to its internal ABNHBD()
routine, and removed all the "detect non-halting-behaviour" test plus
abort logic, then you'd get a completely new program H_Hat_0, and for
THAT new program, H_Hat_0(H_Hat_0) doesn't halt." (This much is
correct, but the whole process is ridiculous!)
Turning things around into what I suspect was the historical development
order:
1) PO looked at H_0 / H_Hat_0, with no abort logic in ABNHBD().
Obviously this quickly leads to infinite recursive emulation
which is a big fail for H_0 as a decider.
2) so PO thought let's add in the "detect non-halting behaviour"
test and abort, to get new programs H/H_Hat. Sure enough
now the NEW program H doesn't have infinite
recursion, and also the new H_Hat(H_Hat) now halts.
3) So PO feels justified in saying that the abort added to the
new H_Hat is "the only thing" making H_Hat halt.
4) ..IOW, H_Hat /WOULD/ run for ever if its emulation wasn't
aborted by ABNHBD() !!
(But this is mixing up behaviour in two completely different
programs H_Hat and H_Hat_0.)
Mike.
[toc] | [prev] | [next] | [standalone]
| From | olcott <NoOne@NoWhere.com> |
|---|---|
| Date | 2020-11-01 19:53 -0600 |
| Subject | Re: Architectural design of a halting problem solution [ Bill the auto mechanic can fix your car ] |
| Message-ID | <hM6dnbD23JA1-wLCnZ2dnUU7-SnNnZ2d@giganews.com> |
| In reply to | #24805 |
On 11/1/2020 6:17 PM, Mike Terry wrote: > On 01/11/2020 22:52, Richard Damon wrote: >> On 11/1/20 3:02 PM, olcott wrote: >>> Because it only makes this decision after its input has stopped >>> executing it is not subject to the conventional >>> "do the opposite of whatever the halt decider decides" >>> trick that shows that some inputs are undecidable. >> >> Note a simple fact. >> >> It may have decided that non-halting behavior was detected, but it can >> get the answer wrong. (which it has). Note the term in the name 'Needed'. >> >> This can be proven by looking at the execution trace of the exact same >> code that was allowed to execute longer (like the outer level) and >> seeing that it ultimately did halt. >> >> THUS, the determination that the behavior was inherently non-halting is >> incorrect. >> >> Or, are you saying that the machine that ran the outer version of the >> code was incorrect? >> >> Note, you need to be able to PROVE (despite the evidence of the outer >> machine) that the inner machine actually was going to run forever with >> non-halting behavior, and at the same time that H and the code inside it >> will always halt in finite time. THAT is a bigger contradiction than >> Linz used in H_Hat. >> > > I think the issue is with the interpretation of "actually was going to > run forever", which you and I and everybody else would understand, but > PO intends his suspicious looking wording to mean something quite > different: > > "If you took the source for H_Hat, and went to its internal ABNHBD() > routine, and removed all the "detect non-halting-behaviour" test plus > abort logic, then you'd get a completely new program H_Hat_0, and for > THAT new program, H_Hat_0(H_Hat_0) doesn't halt." (This much is > correct, but the whole process is ridiculous!) It is literally true that unless the following function aborts the execution its H_Hat input that this input would never stop running: bool Aborted_Because_Non_Halting_Behavior_Detected(H_Hat, H_Hat); This logically entails that when it returns true this return value is indeed consistent with the actual facts and thus logically correct. Thus I closed the sneaky cognitive gap that made it seem like the halting problem was undecidable. > Turning things around into what I suspect was the historical development > order: > 1) PO looked at H_0 / H_Hat_0, with no abort logic in ABNHBD(). > Obviously this quickly leads to infinite recursive emulation > which is a big fail for H_0 as a decider. > 2) so PO thought let's add in the "detect non-halting behaviour" > test and abort, to get new programs H/H_Hat. Sure enough > now the NEW program H doesn't have infinite > recursion, and also the new H_Hat(H_Hat) now halts. > 3) So PO feels justified in saying that the abort added to the > new H_Hat is "the only thing" making H_Hat halt. > 4) ..IOW, H_Hat /WOULD/ run for ever if its emulation wasn't > aborted by ABNHBD() !! > (But this is mixing up behaviour in two completely different > programs H_Hat and H_Hat_0.) > > Mike. > -- Copyright 2020 Pete Olcott "Great spirits have always encountered violent opposition from mediocre minds." Einstein
[toc] | [prev] | [next] | [standalone]
| From | Alan Mackenzie <acm@muc.de> |
|---|---|
| Date | 2020-11-01 08:29 +0000 |
| Message-ID | <rnlrkm$1i8$1@news.muc.de> |
| In reply to | #24751 |
In comp.theory olcott <NoOne@nowhere.com> wrote: > On 10/31/2020 4:33 PM, Alan Mackenzie wrote: >> In comp.theory olcott <NoOne@nowhere.com> wrote: [ .... ] >>> As the definition of a non-halting decider with no undecidable inputs >>> it is fully implemented. >> The definition may have been implemented (whatever that might mean) >> the function has not. Any assertion that it has is a lie. > It is implemented as a mathematical function, that is why I provided > the definition of decider from computer science shown above. You're really a low-down liar. Your magic function has NOT been implemented. That last word implies a running computer program which incorporates that function. You do not have this, and will never have it. > The definition of the non-halting decider is provided below. The set of functions which satisfy that "definition" is empty. > Anyone bothering to pay attention will see that the conventional > "do the opposite of whatever the halt decider decides" > cannot possibly create undecidable input for this decider. Any proof of undecidability applies just as much to your purported halting detector as any other purported halting detector. > Everyone else either hardly knows this subject matter much at all or is > hardly bothering to pay any attention at all. You are the one who hardly knows the subject matter, and you certainly have not been paying attention to those who do. [ .... ] > -- > Copyright 2020 Pete Olcott -- Alan Mackenzie (Nuremberg, Germany).
[toc] | [prev] | [next] | [standalone]
| From | Richard Damon <Richard@Damon-Family.org> |
|---|---|
| Date | 2020-10-31 18:28 -0400 |
| Message-ID | <RxlnH.333086$RY8.280372@fx48.iad> |
| In reply to | #24743 |
On 10/31/20 4:42 PM, olcott wrote: > On 10/31/2020 3:34 PM, olcott wrote: >> On 10/31/2020 3:00 PM, Richard Damon wrote: >>> On 10/31/20 2:57 PM, olcott wrote: >>> >>>> This is literally true: >>>> bool Aborted_Because_Non_Halting_Behavior_Detected(u32 P, u32 I); >>>> Stops executing and Accepts any and all non-halting inputs and Rejects >>>> any and all halting inputs as soon as they halt. >>>> >>>> The only reason why it seems to not be true all the time it that people >>>> are not paying 100% complete attention to its precise specification. >>>> >>> >>> N N OOOOO >>> NN N O O >>> N N N O O >>> N NN O O >>> N N OOOOO >>> >>> THERE IS EXACTLY ONE SPECIFICATION THAT MATTERS TO THE HALTING PROBLEM >>> >>> Will M(N) Halt or not when Run? >>> >>> >>> ANY OTHER QUESTION IS A DIFFERENT QUESTION, AND NOT APPLICABLE. >> >> bool Aborted_Because_Non_Halting_Behavior_Detected(u32 P, u32 I); >> Stops executing and Accepts any and all non-halting inputs and Rejects >> any and all halting inputs as soon as they halt. >> > > -- If there is no inputs that exists that it decides incorrectly > > or fails to decide > > --then this is complete proof that I am correct and all rebuttals are > incorrect. > Is the final behavior of H_Hat(H_Hat) match what H(H_Hat, H_Hat) predicts? Note, Halting means that when we run H_Hat(H_Hat) as an independent machine (so the fact that H aborts some internal calculation doesn't count). Does if give the right results for my H_Hat2(H_Hat2)? Does H (even when embeded inside another machine) deliver consistent results? From all your discussion, H(H_Hat, H_Hat) is going to indicate non-Halting behavior, but the actual H_Hat(H_Hat) when run is going to halt.
[toc] | [prev] | [next] | [standalone]
| From | olcott <NoOne@NoWhere.com> |
|---|---|
| Date | 2020-10-31 17:42 -0500 |
| Message-ID | <xLKdnczd06OndQDCnZ2dnUU7-W3NnZ2d@giganews.com> |
| In reply to | #24756 |
On 10/31/2020 5:28 PM, Richard Damon wrote: > On 10/31/20 4:42 PM, olcott wrote: >> On 10/31/2020 3:34 PM, olcott wrote: >>> On 10/31/2020 3:00 PM, Richard Damon wrote: >>>> On 10/31/20 2:57 PM, olcott wrote: >>>> >>>>> This is literally true: >>>>> bool Aborted_Because_Non_Halting_Behavior_Detected(u32 P, u32 I); >>>>> Stops executing and Accepts any and all non-halting inputs and Rejects >>>>> any and all halting inputs as soon as they halt. >>>>> >>>>> The only reason why it seems to not be true all the time it that people >>>>> are not paying 100% complete attention to its precise specification. >>>>> >>>> >>>> N N OOOOO >>>> NN N O O >>>> N N N O O >>>> N NN O O >>>> N N OOOOO >>>> >>>> THERE IS EXACTLY ONE SPECIFICATION THAT MATTERS TO THE HALTING PROBLEM >>>> >>>> Will M(N) Halt or not when Run? >>>> >>>> >>>> ANY OTHER QUESTION IS A DIFFERENT QUESTION, AND NOT APPLICABLE. >>> >>> bool Aborted_Because_Non_Halting_Behavior_Detected(u32 P, u32 I); >>> Stops executing and Accepts any and all non-halting inputs and Rejects >>> any and all halting inputs as soon as they halt. >>> >> >> -- If there is no inputs that exists that it decides incorrectly >> >> or fails to decide >> >> --then this is complete proof that I am correct and all rebuttals are >> incorrect. >> > > Is the final behavior of H_Hat(H_Hat) match what H(H_Hat, H_Hat) predicts? bool Aborted_Because_Non_Halting_Behavior_Detected(u32 P, u32 I); Stops executing and Accepts any and all non-halting inputs and Rejects any and all halting inputs as soon as they halt. If no inputs exist that it fails to decide correctly then this is complete proof that the above definition is an actual halt decider. If no inputs exist that it fails to decide correctly then this is complete proof that the above definition is an actual halt decider. If no inputs exist that it fails to decide correctly then this is complete proof that the above definition is an actual halt decider. If no inputs exist that it fails to decide correctly then this is complete proof that the above definition is an actual halt decider. If no inputs exist that it fails to decide correctly then this is complete proof that the above definition is an actual halt decider. > Note, Halting means that when we run H_Hat(H_Hat) as an independent > machine (so the fact that H aborts some internal calculation doesn't count). > > Does if give the right results for my H_Hat2(H_Hat2)? > > Does H (even when embeded inside another machine) deliver consistent > results? > > From all your discussion, H(H_Hat, H_Hat) is going to indicate > non-Halting behavior, but the actual H_Hat(H_Hat) when run is going to halt. > -- Copyright 2020 Pete Olcott "Great spirits have always encountered violent opposition from mediocre minds." Einstein
[toc] | [prev] | [next] | [standalone]
| From | olcott <NoOne@NoWhere.com> |
|---|---|
| Date | 2020-10-31 15:47 -0500 |
| Message-ID | <jvmdneYeEZDNUADCnZ2dnUU7-fvNnZ2d@giganews.com> |
| In reply to | #24742 |
On 10/31/2020 3:34 PM, olcott wrote: > On 10/31/2020 3:00 PM, Richard Damon wrote: >> On 10/31/20 2:57 PM, olcott wrote: >> >>> This is literally true: >>> bool Aborted_Because_Non_Halting_Behavior_Detected(u32 P, u32 I); >>> Stops executing and Accepts any and all non-halting inputs and Rejects >>> any and all halting inputs as soon as they halt. >>> >>> The only reason why it seems to not be true all the time it that people >>> are not paying 100% complete attention to its precise specification. >>> >> >> N N OOOOO >> NN N O O >> N N N O O >> N NN O O >> N N OOOOO >> >> THERE IS EXACTLY ONE SPECIFICATION THAT MATTERS TO THE HALTING PROBLEM >> >> Will M(N) Halt or not when Run? >> >> >> ANY OTHER QUESTION IS A DIFFERENT QUESTION, AND NOT APPLICABLE. > > bool Aborted_Because_Non_Halting_Behavior_Detected(u32 P, u32 I); > Stops executing and Accepts any and all non-halting inputs and Rejects > any and all halting inputs as soon as they halt. > If no inputs exist that it decides incorrectly or fails to decide then this is complete proof that I am correct and all rebuttals are incorrect. -- Copyright 2020 Pete Olcott "Great spirits have always encountered violent opposition from mediocre minds." Einstein
[toc] | [prev] | [next] | [standalone]
| From | Keith Thompson <Keith.S.Thompson+u@gmail.com> |
|---|---|
| Date | 2020-10-29 13:13 -0700 |
| Message-ID | <875z6su6y6.fsf@nosuchdomain.example.com> |
| In reply to | #24625 |
André G. Isaak <agisaak@gm.invalid> writes:
> On 2020-10-29 10:05, olcott wrote:
[90 lines deleted]
André, *please* trim the newsgroups when you reply to olcott. I know
it's a pain to have to do it every time.
--
Keith Thompson (The_Other_Keith) Keith.S.Thompson+u@gmail.com
Working, but not speaking, for Philips Healthcare
void Void(void) { Void(); } /* The recursive call of the void */
[toc] | [prev] | [next] | [standalone]
| From | André G. Isaak <agisaak@gm.invalid> |
|---|---|
| Date | 2020-10-29 14:46 -0600 |
| Message-ID | <rnf9ms$ec0$1@dont-email.me> |
| In reply to | #24649 |
On 2020-10-29 14:13, Keith Thompson wrote: > André G. Isaak <agisaak@gm.invalid> writes: >> On 2020-10-29 10:05, olcott wrote: > [90 lines deleted] > > André, *please* trim the newsgroups when you reply to olcott. I know > it's a pain to have to do it every time. Apologies. I have been trying to remember to remove extraneous groups since the cross-posting was drawn to my attention, but he continues to add them back, and I occasionally neglect to read the headers. André -- To email remove 'invalid' & replace 'gm' with well known Google mail service.
[toc] | [prev] | [next] | [standalone]
| From | Andy Walker <anw@cuboid.co.uk> |
|---|---|
| Date | 2020-10-29 14:41 +0000 |
| Message-ID | <rnekbl$1tnn$1@gioia.aioe.org> |
| In reply to | #24595 |
On 29/10/2020 12:18, olcott wrote:
> On the top of page 320 H_Hat is applied to itself:
No, it isn't. It's [putatively] applied to a description
of itself. As you have been told several times. Thus, there is
/no/ recursion, actual or implicit, finite or infinite, involved.
If you would, as I have suggested, distinguish executables from
sources, you would not make this /repeated/ mistake.
You will also perhaps note that Linz gives a quite different
proof on that /same page/.
--
Andy Walker, Nottingham.
Andy's music pages: www.cuboid.me.uk/andy/Music
Composer of the day: www.cuboid.me.uk/andy/Music/Composers/Hause
[toc] | [prev] | [next] | [standalone]
| From | olcott <NoOne@NoWhere.com> |
|---|---|
| Date | 2020-10-29 10:29 -0500 |
| Message-ID | <BuqdnbjBhKZtQgfCnZ2dnUU7-UfNnZ2d@giganews.com> |
| In reply to | #24610 |
On 10/29/2020 9:41 AM, Andy Walker wrote: > On 29/10/2020 12:18, olcott wrote: >> On the top of page 320 H_Hat is applied to itself: > > No, it isn't. It's [putatively] applied to a description > of itself. As you have been told several times. Thus, there is > /no/ recursion, actual or implicit, finite or infinite, involved. > If you would, as I have suggested, distinguish executables from > sources, you would not make this /repeated/ mistake. If we simulate the debug trace based on source code or have a description language that is executable machine code there is infinite recursion in either case, yet former case is much more clumsy. The description language of the x86utm system is x86 machine language that is disassembled into human readable form on the fly only for the benefit of humans. It turns out to be the case that analyzing the control flow of a program is much easier in machine language because all of the control flow is already in the form of a directed graph with integer labeled nodes. > You will also perhaps note that Linz gives a quite different > proof on that /same page/. > x86 language ≡ von Neumann architecture ≡ UTM ≡ RASP Machine The RASP is a random-access machine (RAM) model that, unlike the RAM, has its program in its "registers" together with its input. The registers are unbounded (infinite in capacity); whether the number of registers is finite is model-specific. Thus the RASP is to the RAM as the Universal Turing machine is to the Turing machine. The RASP is an example of the von Neumann architecture whereas the RAM is an example of the Harvard architecture. https://en.wikipedia.org/wiki/Random-access_stored-program_machine -- Copyright 2020 Pete Olcott
[toc] | [prev] | [next] | [standalone]
| From | Ben Bacarisse <ben.usenet@bsb.me.uk> |
|---|---|
| Date | 2020-10-28 04:17 +0000 |
| Message-ID | <87v9evyoeh.fsf@bsb.me.uk> |
| In reply to | #24537 |
olcott <NoOne@NoWhere.com> writes: > The halt decider divides all of its inputs into: > (a) HALTS > (b) DOES_NOT_HALT And interesting division of the set of inputs (not leas because there is no algorithm that can do it). > The halt decider that divides all of its inputs into: > (a) INPUT_PROGRAM_ABORTED_BECAUSE_NON_HALTING_BEHAVIOR_DETECTED > (b) INPUT_PROGRAM_HAS_TERMINATED Why should anyone be interested in this division of the inputs? There are lots of deciders that don't divide the inputs into interesting HALTS and DOES_NOT_HALT categories. -- Ben.
[toc] | [prev] | [next] | [standalone]
| From | Mostowski Collapse <janburse@fastmail.fm> |
|---|---|
| Date | 2020-10-29 14:00 +0100 |
| Subject | Stop crossposting you imbecil spammer (Re: Architectural design of a halting problem solution) |
| Message-ID | <rneee3$d0j$2@solani.org> |
| In reply to | #24537 |
For gods sacke stop cross posting on 4 newsgroups. Especially comp.lang.prolog doesn't make much sense. RAM/RASP is probably best housed on comp.theory. olcott schrieb: > I am a complete imbecial spammer
[toc] | [prev] | [next] | [standalone]
| From | Joe Pfeiffer <pfeiffer@cs.nmsu.edu> |
|---|---|
| Date | 2020-10-29 08:48 -0600 |
| Subject | Re: Stop crossposting you imbecil spammer (Re: Architectural design of a halting problem solution) |
| Message-ID | <1bd011ccls.fsf@pfeifferfamily.net> |
| In reply to | #24602 |
Mostowski Collapse <janburse@fastmail.fm> writes: > For gods sacke stop cross posting on 4 newsgroups. > > Especially comp.lang.prolog doesn't make much sense. > > RAM/RASP is probably best housed on comp.theory. Many people have asked this, and have made no impact on him. The best you can do is not interact with him on newsgroups where his crackpottery is off-topic (sadly, to the best of my knoweldge there is no alt.crackpot newsgroup, as that is the only one where he would really be on-topic).
[toc] | [prev] | [next] | [standalone]
| From | Mike Terry <news.dead.person.stones@darjeeling.plus.com> |
|---|---|
| Date | 2020-10-29 15:17 +0000 |
| Subject | Re: Stop crossposting you imbecil spammer (Re: Architectural design of a halting problem solution) |
| Message-ID | <3c6dndQ5KJWQQAfCnZ2dnUU78InNnZ2d@brightview.co.uk> |
| In reply to | #24611 |
On 29/10/2020 14:48, Joe Pfeiffer wrote: > Mostowski Collapse <janburse@fastmail.fm> writes: > >> For gods sacke stop cross posting on 4 newsgroups. >> >> Especially comp.lang.prolog doesn't make much sense. >> >> RAM/RASP is probably best housed on comp.theory. > > Many people have asked this, and have made no impact on him. The best > you can do is not interact with him on newsgroups where his crackpottery > is off-topic (sadly, to the best of my knoweldge there is no > alt.crackpot newsgroup, as that is the only one where he would really be > on-topic). > There IS an alt.crackpot newsgroup! :) Of course PO will not post there. Anyway, the obvious solution to all this is that if someone doesn't want to be bothered by PO crackpottery in a particular newsgroup, they should just filter PO's posts from those groups. I find that "ignore subthread" works best, as it also ignores any replies to PO. Mike.
[toc] | [prev] | [next] | [standalone]
| From | olcott <NoOne@NoWhere.com> |
|---|---|
| Date | 2020-10-29 11:13 -0500 |
| Subject | Re: Stop crossposting you imbecil spammer (Re: Architectural design of a halting problem solution) |
| Message-ID | <2bednaGvMZqEdwfCnZ2dnUU7-T3NnZ2d@giganews.com> |
| In reply to | #24612 |
On 10/29/2020 10:17 AM, Mike Terry wrote: > On 29/10/2020 14:48, Joe Pfeiffer wrote: >> Mostowski Collapse <janburse@fastmail.fm> writes: >> >>> For gods sacke stop cross posting on 4 newsgroups. >>> >>> Especially comp.lang.prolog doesn't make much sense. >>> >>> RAM/RASP is probably best housed on comp.theory. >> >> Many people have asked this, and have made no impact on him. The best >> you can do is not interact with him on newsgroups where his crackpottery >> is off-topic (sadly, to the best of my knoweldge there is no >> alt.crackpot newsgroup, as that is the only one where he would really be >> on-topic). >> > > There IS an alt.crackpot newsgroup! :) Of course PO will not post there. > > Anyway, the obvious solution to all this is that if someone doesn't want > to be bothered by PO crackpottery in a particular newsgroup, they should > just filter PO's posts from those groups. I find that "ignore > subthread" works best, as it also ignores any replies to PO. > > Mike. > Sure these kind of ad homimen attacks are the first resort of clueless wonders and the last resort of people like yourself that diligently try to find a legitimate rebuttal. Failing at that these people resort to ad hominem attacks because their only interest was in forming one kind of rebuttal or another and they never had any interest in forming mutual understanding. -- Copyright 2020 Pete Olcott
[toc] | [prev] | [next] | [standalone]
| From | Mike Terry <news.dead.person.stones@darjeeling.plus.com> |
|---|---|
| Date | 2020-10-29 16:39 +0000 |
| Subject | Re: Stop crossposting you imbecil spammer (Re: Architectural design of a halting problem solution) |
| Message-ID | <h6GdnRL9oO24bQfCnZ2dnUU78Q_NnZ2d@brightview.co.uk> |
| In reply to | #24619 |
On 29/10/2020 16:13, olcott wrote: > On 10/29/2020 10:17 AM, Mike Terry wrote: >> On 29/10/2020 14:48, Joe Pfeiffer wrote: >>> Mostowski Collapse <janburse@fastmail.fm> writes: >>> >>>> For gods sacke stop cross posting on 4 newsgroups. >>>> >>>> Especially comp.lang.prolog doesn't make much sense. >>>> >>>> RAM/RASP is probably best housed on comp.theory. >>> >>> Many people have asked this, and have made no impact on him. The best >>> you can do is not interact with him on newsgroups where his crackpottery >>> is off-topic (sadly, to the best of my knoweldge there is no >>> alt.crackpot newsgroup, as that is the only one where he would really be >>> on-topic). >>> >> >> There IS an alt.crackpot newsgroup! :) Of course PO will not post >> there. >> >> Anyway, the obvious solution to all this is that if someone doesn't >> want to be bothered by PO crackpottery in a particular newsgroup, they >> should just filter PO's posts from those groups. I find that "ignore >> subthread" works best, as it also ignores any replies to PO. >> >> Mike. >> > > Sure these kind of ad homimen attacks are the first resort of clueless > wonders and the last resort of people like yourself that diligently try > to find a legitimate rebuttal. > > Failing at that these people resort to ad hominem attacks because their > only interest was in forming one kind of rebuttal or another and they > never had any interest in forming mutual understanding. You misunderstand - "these people" are not trying to rebut you; they're trying to get you to stop abusing newsgroups with off topic posts. And they're perfectly entitled to express their opinion that you're a crackpot - that's not an ad hominen attack. (They're NOT saying that some argument you're making is incorrect because you're a crackpot.) If your thread is off topic for a particular newsgroup, but you think that there might be some readers there that would be interested, then the thing to do is post only newsgroups where your topic is on topic, and in those other newsgroups make ONE separate post saying "You may interested in an ongoing discussion in comp.theory regarding XXXXX". If someone there IS genuinely interested they will subscribe to comp.theory to follow the thread. Simples. Mike.
[toc] | [prev] | [next] | [standalone]
| From | Manfred <noname@add.invalid> |
|---|---|
| Date | 2020-10-29 19:20 +0100 |
| Subject | Re: Stop crossposting you imbecil spammer (Re: Architectural design of a halting problem solution) |
| Message-ID | <rnf161$m68$1@gioia.aioe.org> |
| In reply to | #24612 |
On 10/29/2020 4:17 PM, Mike Terry wrote: > On 29/10/2020 14:48, Joe Pfeiffer wrote: >> Mostowski Collapse <janburse@fastmail.fm> writes: >> >>> For gods sacke stop cross posting on 4 newsgroups. >>> >>> Especially comp.lang.prolog doesn't make much sense. >>> >>> RAM/RASP is probably best housed on comp.theory. >> >> Many people have asked this, and have made no impact on him. The best >> you can do is not interact with him on newsgroups where his crackpottery >> is off-topic (sadly, to the best of my knoweldge there is no >> alt.crackpot newsgroup, as that is the only one where he would really be >> on-topic). >> > > There IS an alt.crackpot newsgroup! :) Of course PO will not post there. > > Anyway, the obvious solution to all this is that if someone doesn't want > to be bothered by PO crackpottery in a particular newsgroup, they should > just filter PO's posts from those groups. I find that "ignore > subthread" works best, as it also ignores any replies to PO. > > Mike. > The problem is that some repliers use poor newsreaders that break thread ID consistency, and their replies manage to get through the "ignore subthread" killfile directive. So, the advise still holds that those repliers should better remove the language groups from their replies, unless they aim at landing into the killfile themselves.
[toc] | [prev] | [next] | [standalone]
| From | Mike Terry <news.dead.person.stones@darjeeling.plus.com> |
|---|---|
| Date | 2020-10-29 18:55 +0000 |
| Subject | Re: Stop crossposting you imbecil spammer (Re: Architectural design of a halting problem solution) |
| Message-ID | <x_idnannRP6KjQbCnZ2dnUU78I3NnZ2d@brightview.co.uk> |
| In reply to | #24631 |
On 29/10/2020 18:20, Manfred wrote: > On 10/29/2020 4:17 PM, Mike Terry wrote: >> On 29/10/2020 14:48, Joe Pfeiffer wrote: >>> Mostowski Collapse <janburse@fastmail.fm> writes: >>> >>>> For gods sacke stop cross posting on 4 newsgroups. >>>> >>>> Especially comp.lang.prolog doesn't make much sense. >>>> >>>> RAM/RASP is probably best housed on comp.theory. >>> >>> Many people have asked this, and have made no impact on him. The best >>> you can do is not interact with him on newsgroups where his crackpottery >>> is off-topic (sadly, to the best of my knoweldge there is no >>> alt.crackpot newsgroup, as that is the only one where he would really be >>> on-topic). >>> >> >> There IS an alt.crackpot newsgroup! :) Of course PO will not post >> there. >> >> Anyway, the obvious solution to all this is that if someone doesn't >> want to be bothered by PO crackpottery in a particular newsgroup, they >> should just filter PO's posts from those groups. I find that "ignore >> subthread" works best, as it also ignores any replies to PO. >> >> Mike. >> > > The problem is that some repliers use poor newsreaders that break thread > ID consistency, and their replies manage to get through the "ignore > subthread" killfile directive. > So, the advise still holds that those repliers should better remove the > language groups from their replies, unless they aim at landing into the > killfile themselves. Interesting - I'm not familiar with that problem. Perhaps you give me a couple of recent examples of such responses, and the newsgroup where you're seeing them? (msgid values would be enough) On the sci.math newsgroup I use ignore subthread fairly extensively and it pretty much eliminates posts by the well-known trolls/crackpots. Sometimes I think "why am I seeing this post about TrollPoster who's in my filter?". But when I look closer I see it's not down to poor newsreaders - typically it is either that the post is merely /about/ TrollPoster and not actually a reply to her, or it is a reply to a TrollPoster post from such a long time ago that it's not recorded in my local newsreader. (Neither of these is down to posters using poor newsreaders.) Mike.
[toc] | [prev] | [next] | [standalone]
| From | David Brown <david.brown@hesbynett.no> |
|---|---|
| Date | 2020-10-30 11:02 +0100 |
| Subject | Re: Stop crossposting you imbecil spammer (Re: Architectural design of a halting problem solution) |
| Message-ID | <rngob0$ach$1@dont-email.me> |
| In reply to | #24639 |
On 29/10/2020 19:55, Mike Terry wrote: > On 29/10/2020 18:20, Manfred wrote: >> On 10/29/2020 4:17 PM, Mike Terry wrote: >>> On 29/10/2020 14:48, Joe Pfeiffer wrote: >>>> Mostowski Collapse <janburse@fastmail.fm> writes: >>>> >>>>> For gods sacke stop cross posting on 4 newsgroups. >>>>> >>>>> Especially comp.lang.prolog doesn't make much sense. >>>>> >>>>> RAM/RASP is probably best housed on comp.theory. >>>> >>>> Many people have asked this, and have made no impact on him. The best >>>> you can do is not interact with him on newsgroups where his >>>> crackpottery >>>> is off-topic (sadly, to the best of my knoweldge there is no >>>> alt.crackpot newsgroup, as that is the only one where he would >>>> really be >>>> on-topic). >>>> >>> >>> There IS an alt.crackpot newsgroup! :) Of course PO will not post >>> there. >>> >>> Anyway, the obvious solution to all this is that if someone doesn't >>> want to be bothered by PO crackpottery in a particular newsgroup, they >>> should just filter PO's posts from those groups. I find that "ignore >>> subthread" works best, as it also ignores any replies to PO. >>> >>> Mike. >>> >> >> The problem is that some repliers use poor newsreaders that break thread >> ID consistency, and their replies manage to get through the "ignore >> subthread" killfile directive. >> So, the advise still holds that those repliers should better remove the >> language groups from their replies, unless they aim at landing into the >> killfile themselves. > > Interesting - I'm not familiar with that problem. Perhaps you give me a > couple of recent examples of such responses, and the newsgroup where > you're seeing them? (msgid values would be enough) > > On the sci.math newsgroup I use ignore subthread fairly extensively and > it pretty much eliminates posts by the well-known trolls/crackpots. > Sometimes I think "why am I seeing this post about TrollPoster who's in > my filter?". But when I look closer I see it's not down to poor > newsreaders - typically it is either that the post is merely /about/ > TrollPoster and not actually a reply to her, or it is a reply to a > TrollPoster post from such a long time ago that it's not recorded in my > local newsreader. (Neither of these is down to posters using poor > newsreaders.) > The cause of this is not a problem with newsreaders - it is a problem with Olcott. Roughly speaking (assuming I understand it myself), it goes like this. First, he makes a cross-posting to several off-topic groups. Then someone tries to be helpful by replying to him with these extra groups removed, leaving only comp.theory (this is normally the correct way to handle bad cross-posting). But when Olcott replies again, he adds the off-topic groups once more. As far as anyone (or any newsreader) viewing these other groups is concerned, that reply from Olcott has come from nowwhere - it is not a reply to anything in the group, and it therefore counts as a new thread.
[toc] | [prev] | [next] | [standalone]
Page 7 of 8 — ← Prev page 1 2 3 4 5 6 [7] 8 Next page →
Back to top | Article view | comp.theory
csiph-web