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

Keith Thompson <Keith.S.Thompson+u@gmail.com> writes:

Tim Rentsch <tr.17687@z991.linuxsc.com> writes:
>

James Kuyper <jameskuyper@alumni.caltech.edu> writes:
>

Just as 1 is an integer literal whose value cannot be modified,
[...]

>
The C language doesn't have integer literals.  C has string
literals, and compound literals, and it has integer constants.
But C does not have integer literals.

>
Technically correct (but IMHO not really worth worrying about).

Anyone who flogs others posters for incorrectly using terminology
defined in the ISO C standard should set a good example by using
the ISO-C-defined terms correctly himself.

There is a proposal for C2y, authored by Jens Gustedt, to change the
term "constant" to "literal" for character, integer, and floating
constants.  (I think it's a good idea.)
>
<https://www.open-std.org/jtc1/sc22/wg14/www/docs/n3239.htm>

The more C is changed to resemble C++ the worse it becomes.  It
isn't surprising that you like it.