Re: Future of C

From	Keith Thompson <kst-u@mib.org>
Newsgroups	comp.lang.c
Subject	Re: Future of C
Date	2018-04-09 08:52 -0700
Organization	None to speak of
Message-ID	<lnwoxgnzr5.fsf@kst-u.example.com> (permalink)
References	(16 earlier) <kfnh8oxlkfn.fsf@x-alumni2.alumni.caltech.edu> <lnin9dtsuo.fsf@kst-u.example.com> <kfnfu4aimsb.fsf@x-alumni2.alumni.caltech.edu> <lnlge2qz11.fsf@kst-u.example.com> <kfn4lkke9l9.fsf@x-alumni2.alumni.caltech.edu>

Show all headers | View raw

Tim Rentsch <txr@alumni.caltech.edu> writes:
> Keith Thompson <kst-u@mib.org> writes:
>> Tim Rentsch <txr@alumni.caltech.edu> writes:
>> [...]
>>> Apparently you have a fundamental misunderstanding of what is
>>> meant by defining behavior.
>>
>> Apparently my understanding differs from yours.  Not the same thing.
>
> I'm sorry if you found my statement derogatory or offensive.  I
> didn't mean it to be;  it was meant only as a statement of my
> perception, not as a statement of fact.
>
> You may think I have a fundamental misunderstanding of what is
> meant by undefined behavior (or some other aspect of the C
> standard, for that matter).  If you do I hope you will say so,
> and say so directly.  I am interested to hear your perceptions,
> even if I don't always share those perceptions.
>
> After giving the one statement you quoted, my posting went on to
> say two things.  First it gave a detailed explanation of what I
> think the Standard says about defining behavior, and why.  Second
> it reviewed your previous comments with a point-by-point response
> (and in one case rebuttal) for everything you said.  You chose
> not to respond to any of those comments.  Would you mind if I ask
> why you didn't?  I put a fair amount of effort both into
> organizing my thoughts and into putting those thoughts into
> writing, an honest and sincere effort to explain and convey my
> reasoning.  I have responded to your comments.  If you just
> ignore mine, what conclusion do you think I should reach?

I don't clearly remember the rest of your article, just because
it's been a while since I read it.  I didn't respond to it partly
because I didn't have much to say about it, partly because I didn't
expect any response to lead to anything useful, and partly because
I was annoyed by what I perceived as an insult.

-- 
Keith Thompson (The_Other_Keith) kst-u@mib.org  <http://www.ghoti.net/~kst>
Working, but not speaking, for JetHead Development, Inc.
"We must do something.  This is something.  Therefore, we must do this."
    -- Antony Jay and Jonathan Lynn, "Yes Minister"

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

Thread

Re: Future of C Tim Rentsch <txr@alumni.caltech.edu> - 2018-03-30 07:14 -0700
  Re: Future of C David Brown <david.brown@hesbynett.no> - 2018-03-30 17:23 +0200
    Re: Future of C Steven Petruzzellis <frelwizzen@gmail.com> - 2018-03-31 02:41 -0700
  Re: Future of C Keith Thompson <kst-u@mib.org> - 2018-03-30 09:45 -0700
    Re: Future of C Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2018-04-02 01:42 -0700
      Re: Future of C Steven Petruzzellis <frelwizzen@gmail.com> - 2018-04-02 04:53 -0700
      Re: Future of C supercat@casperkitty.com - 2018-04-02 06:02 -0700
        Re: Future of C Steven Petruzzellis <frelwizzen@gmail.com> - 2018-04-02 06:57 -0700
        Re: Future of C Keith Thompson <kst-u@mib.org> - 2018-04-02 09:12 -0700
          Re: Future of C "Chris M. Thomasson" <invalid_chris_thomasson@invalid.invalid> - 2018-04-02 13:30 -0700
            Re: Future of C Steven Petruzzellis <frelwizzen@gmail.com> - 2018-04-03 00:59 -0700
          Re: Future of C David Brown <david.brown@hesbynett.no> - 2018-04-02 22:33 +0200
            Re: Future of C Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2018-04-03 01:40 -0700
              Re: Future of C David Brown <david.brown@hesbynett.no> - 2018-04-03 12:47 +0200
          Re: Future of C supercat@casperkitty.com - 2018-04-03 09:51 -0700
            Re: Future of C Keith Thompson <kst-u@mib.org> - 2018-04-03 11:23 -0700
              Re: Future of C supercat@casperkitty.com - 2018-04-03 11:37 -0700
                Re: Future of C Keith Thompson <kst-u@mib.org> - 2018-04-03 11:46 -0700
                Re: Future of C supercat@casperkitty.com - 2018-04-03 12:26 -0700
                Re: Future of C Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2018-04-04 01:17 -0700
                Re: Future of C supercat@casperkitty.com - 2018-04-04 09:45 -0700
      Re: Future of C Keith Thompson <kst-u@mib.org> - 2018-04-02 09:10 -0700
        Re: Future of C Steven Petruzzellis <frelwizzen@gmail.com> - 2018-04-02 09:33 -0700
        Re: Future of C Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2018-04-03 01:35 -0700
          Re: Future of C David Brown <david.brown@hesbynett.no> - 2018-04-03 12:50 +0200
            Re: Future of C Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2018-04-03 04:01 -0700
          Re: Future of C Keith Thompson <kst-u@mib.org> - 2018-04-03 09:12 -0700
    Re: Future of C Tim Rentsch <txr@alumni.caltech.edu> - 2018-04-04 16:17 -0700
      Re: Future of C Keith Thompson <kst-u@mib.org> - 2018-04-04 17:26 -0700
        Re: Future of C Tim Rentsch <txr@alumni.caltech.edu> - 2018-04-09 07:30 -0700
          Re: Future of C Keith Thompson <kst-u@mib.org> - 2018-04-09 08:52 -0700
            Re: Future of C Tim Rentsch <txr@alumni.caltech.edu> - 2018-04-11 08:21 -0700
              Re: Future of C Keith Thompson <kst-u@mib.org> - 2018-04-11 09:28 -0700
      Re: Future of C supercat@casperkitty.com - 2018-04-05 11:00 -0700

csiph-web