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

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