Re: Every sufficiently competent C programmer knows --- Semantic Property of Finite String

Liste des GroupesRevenir à theory 
Sujet : Re: Every sufficiently competent C programmer knows --- Semantic Property of Finite String
De : dbush.mobile (at) *nospam* gmail.com (dbush)
Groupes : comp.theory
Date : 14. Mar 2025, 01:32:05
Autres entêtes
Organisation : A noiseless patient Spider
Message-ID : <vqvte4$5ud7$1@dont-email.me>
References : 1 2 3 4 5 6 7 8 9 10 11 12 13 14
User-Agent : Mozilla Thunderbird
On 3/13/2025 8:21 PM, olcott wrote:
On 3/13/2025 3:48 PM, dbush wrote:
On 3/13/2025 4:46 PM, olcott wrote:
On 3/13/2025 4:27 AM, joes wrote:
Am Wed, 12 Mar 2025 21:41:34 -0500 schrieb olcott:
On 3/12/2025 7:56 PM, dbush wrote:
On 3/12/2025 8:41 PM, olcott wrote:
>
NOT WHEN IT IS STIPULATED THAT THE BEHAVIOR BEING MEASURED IS
>
The direct execution of DDD
>
is proven to be different than the behavior of DDD emulated by HHH
according to the semantics of the x86 language.
>
Which is weird, considering that a simulator should produce the same
behaviour.
>
>
DECIDERS ARE REQUIRED TO REPORT ON THE SEMANTIC OR SYNTACTIC PROPERTY OF
THEIR INPUT FINITE STRINGS.
And not if the input called a different simulator that didn't abort.
>
>
Replacing the code of HHH with an unconditional simulator and subsequently running HHH(DD) cannot possibly
reach its own final state no matter what HHH
does.
>
Replacing the code of HHH1 with an unconditional simulator and subsequently running HHH1(DD) does reach its
own final state.
>
If someone was not a liar they would say that
these are different computations.
>
>
Only because one changes the code that DD runs and one doesn't
 *Changing my quoted words is dishonest*
 
Not when you gave your official on-the-record permission to do so:
On 3/6/2025 8:22 AM, dbush wrote:
 > On 3/5/2025 11:06 PM, dbush wrote:
 >> Last chance:
 >>
 >> Give an example where X correctly emulated by Y is
 >> different from replacing the code of Y with an unconditional simulator
 >> and subsequently running Y(X).
 >>
 >> Failure to do so in your next reply (or within one hour of your next
 >> post in this newsgroup) will be taken as your on-the-record admission
 >> that they mean the same thing, and that additionally you officially
 >> approve of replacing the former with the latter in any of your quotes
 >> to make it clear exactly what you're talking about.
 >>
 >
 > Let The Record Show that Peter Olcott made the following post in this
 > newsgroup after the above quoted message:
 >
 > On 3/5/2025 11:41 PM, olcott wrote:
 >  > No matter WTF HHH is DD cannot possibly reach its "ret"
 >  > instruction and terminate normally when correctly emulated by HHH.
 >  > Either this is over your head or you are a liar. There is
 >  > no third choice.
 >
 > And has not responded to the quoted message above more than 8 hours
 > after he made the above post.
 >
 > He has therefore satisfied the requirements stated above for admission
 > of the given statement.  So:
 >
 > Let The Record Show:
 >
 > That Peter Olcott:
 >
 > Has admitted that the following statement (Statement 1):
 >
 > DD correctly simulated by HHH
 >
 > Is exactly equivalent to the following statement (Statement 2):
 >
 > Replacing the code of HHH with an unconditional simulator and
 > subsequently running HHH(DD)
 >
 > And has given his official permission to anyone responding to his
 > messages to replace Statement 1 with Statement 2 in any of his quoted
 > messages for the purposes of making it clear what he is claiming

Date Sujet#  Auteur
11 Mar 25 * Every sufficiently competent C programmer knows343olcott
11 Mar 25 +* Re: Every sufficiently competent C programmer knows25Richard Damon
11 Mar 25 i`* Re: Every sufficiently competent C programmer knows24olcott
11 Mar 25 i +- Re: Every sufficiently competent C programmer knows1dbush
11 Mar 25 i +* Re: Every sufficiently competent C programmer knows21Mikko
11 Mar 25 i i`* Re: Every sufficiently competent C programmer knows20olcott
11 Mar 25 i i +- Re: Every sufficiently competent C programmer knows1Richard Heathfield
11 Mar 25 i i +* Re: Every sufficiently competent C programmer knows4Mikko
11 Mar 25 i i i`* Re: Every sufficiently competent C programmer knows3olcott
11 Mar 25 i i i +- Re: Every sufficiently competent C programmer knows1Richard Damon
12 Mar 25 i i i `- Re: Every sufficiently competent C programmer knows1Mikko
11 Mar 25 i i +- Re: Every sufficiently competent C programmer knows1Richard Damon
16 Mar 25 i i `* Re: Every sufficiently competent C programmer knows13Mikko
16 Mar 25 i i  +* Re: Every sufficiently competent C programmer knows11Richard Heathfield
16 Mar 25 i i  i+* Re: Every sufficiently competent C programmer knows2Mikko
16 Mar 25 i i  ii`- Re: Every sufficiently competent C programmer knows1Richard Heathfield
16 Mar 25 i i  i`* Re: Every sufficiently competent C programmer knows8Keith Thompson
16 Mar 25 i i  i +* Every sufficiently competent C programmer knows --- original post appended at end6olcott
16 Mar 25 i i  i i+* Re: Every sufficiently competent C programmer knows --- original post appended at end4joes
17 Mar 25 i i  i ii`* Re: Every sufficiently competent C programmer knows --- Correct Emulation Specifies Behavior3olcott
17 Mar 25 i i  i ii +- Re: Every sufficiently competent C programmer knows --- Correct Emulation Specifies Behavior1joes
17 Mar 25 i i  i ii `- Re: Every sufficiently competent C programmer knows --- Correct Emulation Specifies Behavior1Richard Damon
17 Mar 25 i i  i i`- Re: Every sufficiently competent C programmer knows --- original post appended at end1Mikko
16 Mar 25 i i  i `- Re: Every sufficiently competent C programmer knows1Richard Heathfield
16 Mar 25 i i  `- Re: Every sufficiently competent C programmer knows1olcott
11 Mar 25 i `- Re: Every sufficiently competent C programmer knows1Richard Damon
11 Mar 25 +- Re: Every sufficiently competent C programmer knows1Richard Heathfield
11 Mar 25 +* Re: Every sufficiently competent C programmer knows16Fred. Zwarts
11 Mar 25 i+* Re: Every sufficiently competent C programmer knows12Richard Heathfield
11 Mar 25 ii`* Re: Every sufficiently competent C programmer knows11olcott
11 Mar 25 ii +* Re: Every sufficiently competent C programmer knows5Richard Heathfield
11 Mar 25 ii i`* Re: Every sufficiently competent C programmer knows4olcott
11 Mar 25 ii i `* Re: Every sufficiently competent C programmer knows3Richard Heathfield
11 Mar 25 ii i  `* Re: Every sufficiently competent C programmer knows2olcott
11 Mar 25 ii i   `- Re: Every sufficiently competent C programmer knows1Richard Heathfield
11 Mar 25 ii +* Re: Every sufficiently competent C programmer knows4Mikko
11 Mar 25 ii i+- Re: Every sufficiently competent C programmer knows1Richard Heathfield
11 Mar 25 ii i`* Re: Every sufficiently competent C programmer knows2olcott
12 Mar 25 ii i `- Re: Every sufficiently competent C programmer knows1Mikko
11 Mar 25 ii `- Re: Every sufficiently competent C programmer knows1Richard Damon
11 Mar 25 i`* Re: Every sufficiently competent C programmer knows3Mikko
11 Mar 25 i `* Re: Every sufficiently competent C programmer knows2olcott
11 Mar 25 i  `- Re: Every sufficiently competent C programmer knows1Mikko
11 Mar 25 `* Re: Every sufficiently competent C programmer knows300Mikko
11 Mar 25  `* Re: Every sufficiently competent C programmer knows299olcott
11 Mar 25   +* Re: Every sufficiently competent C programmer knows290Richard Heathfield
11 Mar 25   i+* Re: Every sufficiently competent C programmer knows5olcott
11 Mar 25   ii+- Re: Every sufficiently competent C programmer knows1Richard Heathfield
12 Mar 25   ii`* Re: Every sufficiently competent C programmer knows3Mikko
12 Mar 25   ii `* Re: Every sufficiently competent C programmer knows2Richard Heathfield
13 Mar 25   ii  `- Re: Every sufficiently competent C programmer knows1Mikko
11 Mar 25   i`* Re: Every sufficiently competent C programmer knows284Mike Terry
11 Mar 25   i +- Re: Every sufficiently competent C programmer knows1wij
11 Mar 25   i +* Re: Every sufficiently competent C programmer knows82Richard Heathfield
11 Mar 25   i i+* Re: Every sufficiently competent C programmer knows7wij
11 Mar 25   i ii+* Re: Every sufficiently competent C programmer knows5Richard Heathfield
11 Mar 25   i iii+- Re: Every sufficiently competent C programmer knows1wij
11 Mar 25   i iii`* Re: Every sufficiently competent C programmer knows3wij
11 Mar 25   i iii `* Re: Every sufficiently competent C programmer knows2Richard Heathfield
11 Mar 25   i iii  `- Re: Every sufficiently competent C programmer knows1dbush
12 Mar 25   i ii`- Re: Every sufficiently competent C programmer knows1Mikko
11 Mar 25   i i+* Re: Every sufficiently competent C programmer knows71Mike Terry
11 Mar 25   i ii+* Re: Every sufficiently competent C programmer knows3Richard Heathfield
12 Mar 25   i iii`* Re: Every sufficiently competent C programmer knows2Mike Terry
12 Mar 25   i iii `- Re: Every sufficiently competent C programmer knows1Richard Heathfield
12 Mar 25   i ii+* Re: Every sufficiently competent C programmer knows44Fred. Zwarts
12 Mar 25   i iii`* Re: Every sufficiently competent C programmer knows43Mike Terry
12 Mar 25   i iii `* Re: Every sufficiently competent C programmer knows --- posthumous reviewers42olcott
12 Mar 25   i iii  +* Re: Every sufficiently competent C programmer knows --- posthumous reviewers40Richard Damon
13 Mar 25   i iii  i`* Re: Every sufficiently competent C programmer knows --- posthumous reviewers39olcott
13 Mar 25   i iii  i +* Re: Every sufficiently competent C programmer knows --- posthumous reviewers3Richard Damon
13 Mar 25   i iii  i i`* Re: Every sufficiently competent C programmer knows --- posthumous reviewers2olcott
13 Mar 25   i iii  i i `- Re: Every sufficiently competent C programmer knows --- posthumous reviewers1Richard Damon
13 Mar 25   i iii  i +* Re: Every sufficiently competent C programmer knows --- posthumous reviewers34Mikko
13 Mar 25   i iii  i i`* Re: Every sufficiently competent C programmer knows --- posthumous reviewers33olcott
13 Mar 25   i iii  i i +* Re: Every sufficiently competent C programmer knows --- posthumous reviewers3joes
14 Mar 25   i iii  i i i`* Re: Every sufficiently competent C programmer knows --- posthumous reviewers2olcott
14 Mar 25   i iii  i i i `- Re: Every sufficiently competent C programmer knows --- posthumous reviewers1Richard Damon
14 Mar 25   i iii  i i +- Re: Every sufficiently competent C programmer knows --- posthumous reviewers1Richard Damon
14 Mar 25   i iii  i i +- Re: Every sufficiently competent C programmer knows --- posthumous reviewers1Fred. Zwarts
14 Mar 25   i iii  i i +* Re: Every sufficiently competent C programmer knows --- posthumous reviewers23Mikko
14 Mar 25   i iii  i i i`* Re: Every sufficiently competent C programmer knows --- posthumous reviewers22olcott
14 Mar 25   i iii  i i i +- Re: Every sufficiently competent C programmer knows --- posthumous reviewers1Richard Damon
15 Mar 25   i iii  i i i `* Re: Every sufficiently competent C programmer knows --- posthumous reviewers20Mikko
15 Mar 25   i iii  i i i  `* Re: Every sufficiently competent C programmer knows --- Paraphrase of Sipser's agreement19olcott
15 Mar 25   i iii  i i i   +* Re: Every sufficiently competent C programmer knows --- Paraphrase of Sipser's agreement6dbush
16 Mar 25   i iii  i i i   i`* Re: Every sufficiently competent C programmer knows --- Paraphrase of Sipser's agreement5olcott
16 Mar 25   i iii  i i i   i +* Re: Every sufficiently competent C programmer knows --- Paraphrase of Sipser's agreement3dbush
16 Mar 25   i iii  i i i   i i`* Re: Every sufficiently competent C programmer knows --- Paraphrase of Sipser's agreement2olcott
16 Mar 25   i iii  i i i   i i `- Re: Every sufficiently competent C programmer knows --- Paraphrase of Sipser's agreement1dbush
16 Mar 25   i iii  i i i   i `- Re: Every sufficiently competent C programmer knows --- Paraphrase of Sipser's agreement1Mikko
16 Mar 25   i iii  i i i   +- Re: Every sufficiently competent C programmer knows --- Paraphrase of Sipser's agreement1Mikko
16 Mar 25   i iii  i i i   +* Re: Every sufficiently competent C programmer knows --- Paraphrase of Sipser's agreement5Richard Damon
16 Mar 25   i iii  i i i   i`* Re: Every sufficiently competent C programmer knows --- Paraphrase of Sipser's agreement4olcott
16 Mar 25   i iii  i i i   i `* Re: Every sufficiently competent C programmer knows --- Paraphrase of Sipser's agreement3Richard Damon
17 Mar 25   i iii  i i i   i  `* Re: Every sufficiently competent C programmer knows --- Paraphrase of Sipser's agreement2olcott
17 Mar 25   i iii  i i i   i   `- Re: Every sufficiently competent C programmer knows --- Paraphrase of Sipser's agreement1Richard Damon
16 Mar 25   i iii  i i i   `* Re: Every sufficiently competent C programmer knows --- Paraphrase of Sipser's agreement6joes
16 Mar 25   i iii  i i i    `* Re: Every sufficiently competent C programmer knows --- Paraphrase of Sipser's agreement5olcott
16 Mar 25   i iii  i i i     `* Re: Every sufficiently competent C programmer knows --- Paraphrase of Sipser's agreement4dbush
16 Mar 25   i iii  i i i      `* Re: Every sufficiently competent C programmer knows --- Paraphrase of Sipser's agreement3olcott
15 Mar 25   i iii  i i `* Re: Every sufficiently competent C programmer knows --- posthumous reviewers4Mikko
13 Mar 25   i iii  i `- Re: Every sufficiently competent C programmer knows --- posthumous reviewers1Fred. Zwarts
13 Mar 25   i iii  `- Re: Every sufficiently competent C programmer knows --- posthumous reviewers1Fred. Zwarts
13 Mar 25   i ii`* Re: Every sufficiently competent C programmer knows23Ben Bacarisse
12 Mar 25   i i`* Re: Every sufficiently competent C programmer knows3Mikko
11 Mar 25   i +* Re: Every sufficiently competent C programmer knows --- Stupid Mistake?2olcott
11 Mar 25   i +* Re: Every sufficiently competent C programmer knows --- Counter-Factual ERROR4olcott
12 Mar 25   i +* Re: Every sufficiently competent C programmer knows --- Very Stupid Mistake101olcott
12 Mar 25   i `* Re: Every sufficiently competent C programmer knows --- Mike's very stupid mistake93olcott
11 Mar 25   +* Re: Every sufficiently competent C programmer knows3Mikko
11 Mar 25   `* Re: Every sufficiently competent C programmer knows5Fred. Zwarts

Haut de la page

Les messages affichés proviennent d'usenet.

NewsPortal