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


Groups > comp.lang.c > #397139 > unrolled thread

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

Started byBonita Montero <Bonita.Montero@gmail.com>
First post2026-03-22 09:58 +0100
Last post2026-03-24 08:58 +0100
Articles 3 — 3 participants

Back to article view | Back to comp.lang.c

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.


Contents

  Re: relearning C: why does an in-place change to a char* segfault? Bonita Montero <Bonita.Montero@gmail.com> - 2026-03-22 09:58 +0100
    Re: relearning C: why does an in-place change to a char* segfault? Tim Rentsch <tr.17687@z991.linuxsc.com> - 2026-03-23 21:14 -0700
      Re: relearning C: why does an in-place change to a char* segfault? David Brown <david.brown@hesbynett.no> - 2026-03-24 08:58 +0100

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

FromBonita Montero <Bonita.Montero@gmail.com>
Date2026-03-22 09:58 +0100
SubjectRe: relearning C: why does an in-place change to a char* segfault?
Message-ID<10poav2$3563c$1@raubtier-asyl.eternal-september.org>
Am 14.08.2024 um 02:46 schrieb Tim Rentsch:

> 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.

There's no problem when you call them integer literals.
Except when you're pedantic as hell.

[toc] | [next] | [standalone]


#397169

FromTim Rentsch <tr.17687@z991.linuxsc.com>
Date2026-03-23 21:14 -0700
Message-ID<86ikal50et.fsf@linuxsc.com>
In reply to#397139
Bonita Montero <Bonita.Montero@gmail.com> writes:

> Am 14.08.2024 um 02:46 schrieb Tim Rentsch:
>
>> 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.
>
> There's no problem when you call them integer literals.
> Except when you're pedantic as hell.

Oh no!  An insult from a narcissist!  Whatever shall I do?

[toc] | [prev] | [next] | [standalone]


#397172

FromDavid Brown <david.brown@hesbynett.no>
Date2026-03-24 08:58 +0100
Message-ID<10ptg78$rit4$1@dont-email.me>
In reply to#397169
On 24/03/2026 05:14, Tim Rentsch wrote:
> Bonita Montero <Bonita.Montero@gmail.com> writes:
> 
>> Am 14.08.2024 um 02:46 schrieb Tim Rentsch:
>>
>>> 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.
>>
>> There's no problem when you call them integer literals.
>> Except when you're pedantic as hell.
> 
> Oh no!  An insult from a narcissist!  Whatever shall I do?

You could just ignore Bonita, as a lot of people do.  And you could stop 
necroposting.

But don't stop the pedantry about C and the C standards.  It is often 
irrelevant for practical coding, but there are plenty of situations 
where it is good to get the terminology exactly right.  Take "pedantic 
as hell" as a compliment.

[toc] | [prev] | [standalone]


Back to top | Article view | comp.lang.c


csiph-web