Groups | Search | Server Info | Login | Register

Groups > comp.lang.c > #388536

Re: relearning C: why does an in-place change to a char* segfault?

Show all headers | View raw

Tim Rentsch <tr.17687@z991.linuxsc.com> writes:
> Keith Thompson <Keith.S.Thompson+u@gmail.com> writes:
>>> The more C is changed to resemble C++ the worse it becomes.  It
>>> isn't surprising that you like it.
>>
>> I presume that was intended as a personal insult.
>
> It wasn't.

Then you need to work on knowing when you've insulted someone.

For context, since the parent article is from a month and a half
ago, I was discussing a proposal to change a future C standard to
refer to "constants" as "literals".  I mentioned that I think it's
a good idea.

In response, you wrote the above.  The implication is that you
expect me to like ideas that make C worse.  At the time, I took
that as a clear insult.  Thinking about it now, I can only take
your word that it wasn't your intent, but I still don't see how it
could be anything other than a clear insult.

I've considered asking for an explanation, but I don't feel the
need to discuss this further.

-- 
Keith Thompson (The_Other_Keith) Keith.S.Thompson+u@gmail.com
void Void(void) { Void(); } /* The recursive call of the void */

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

Thread

Re: relearning C: why does an in-place change to a char* segfault? Tim Rentsch <tr.17687@z991.linuxsc.com> - 2024-09-27 17:33 -0700
  Re: relearning C: why does an in-place change to a char* segfault? Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2024-09-27 20:34 -0700
    Re: relearning C: why does an in-place change to a char* segfault? Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2024-09-28 07:22 +0200
      Re: relearning C: why does an in-place change to a char* segfault? Phillip Frabott <nntp@fulltermprivacy.com> - 2024-09-28 17:57 +0000
        Re: relearning C: why does an in-place change to a char* segfault? Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2024-09-28 13:42 -0700
          Re: relearning C: why does an in-place change to a char* segfault? Phillip Frabott <nntp@fulltermprivacy.com> - 2024-09-28 22:05 +0000
            Re: relearning C: why does an in-place change to a char* segfault? Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2024-09-28 15:17 -0700

csiph-web