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


Groups > comp.lang.c > #154441

Re: Transforming "C" into a Turing equivalent language 007 [Turing equivalent x86 computations]

From Keith Thompson <Keith.S.Thompson+u@gmail.com>
Newsgroups comp.theory, comp.lang.c, comp.ai.philosophy
Subject Re: Transforming "C" into a Turing equivalent language 007 [Turing equivalent x86 computations]
Date 2020-09-03 10:49 -0700
Organization None to speak of
Message-ID <87imcuzr5s.fsf@nosuchdomain.example.com> (permalink)
References <I5mdnZ4oyLTc983CnZ2dnUU7-a3NnZ2d@giganews.com> <87mu27z8eo.fsf@nosuchdomain.example.com> <LfmdnRTy2Locn8zCnZ2dnUU7-QtQAAAA@giganews.com>

Cross-posted to 3 groups.

Show all headers | View raw


olcott <NoOne@NoWhere.com> writes:
> On 9/3/2020 1:22 AM, Keith Thompson wrote:
[...]
>> Since you don't even mention C++, please don't cross-post this to
>> comp.lang.c++.
[...]
> Since "C" is the basis for "C++" my work applies to "C++".
> Since some people on the C++ forum are responding that indicates
> interest. Because there is very little interest I only post my brand
> new material to C++ and not its corresponding dialogue.

C and C++ are two different languages (yes, I know they're related),
and they have two different newsgroups for very good reasons.

When someone posts a followup to a cross-posted article, I'm not
sure you can tell where they responded from.  If you cross-post to
comp.theory and comp.lang.c++ and someone posts a followup while
reading comp.theory, the followup will show up in both with the
same headers.

If you're not talking about C++, please don't post to comp.lang.c++.

(I don't expect you to listen to reason.  If I don't respond further,
don't assume I agree with you.)

-- 
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 */

Back to comp.lang.c | Previous | NextPrevious in thread | Next in thread | Find similar


Thread

Transforming "C" into a Turing equivalent language 007 [Turing equivalent x86 computations] olcott <NoOne@NoWhere.com> - 2020-09-02 23:00 -0500
  Re: Transforming "C" into a Turing equivalent language 007 [Turing equivalent x86 computations] Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2020-09-02 23:22 -0700
    Re: Transforming "C" into a Turing equivalent language 007 [Turing equivalent x86 computations] olcott <NoOne@NoWhere.com> - 2020-09-03 09:49 -0500
      Re: Transforming "C" into a Turing equivalent language 007 [Turing equivalent x86 computations] Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2020-09-03 10:49 -0700
        Re: Transforming "C" into a Turing equivalent language 007 [Turing equivalent x86 computations] olcott <NoOne@NoWhere.com> - 2020-09-03 12:52 -0500
    Re: Transforming "C" into a Turing equivalent language 007 [Turing equivalent x86 computations] olcott <NoOne@NoWhere.com> - 2020-09-03 09:51 -0500

csiph-web