Groups | Search | Server Info | Login | Register
Groups > comp.lang.c > #396727
| From | Keith Thompson <Keith.S.Thompson+u@gmail.com> |
|---|---|
| Newsgroups | comp.lang.c |
| Subject | Re: relearning C: why does an in-place change to a char* segfault? |
| Date | 2026-03-02 04:43 -0800 |
| Organization | None to speak of |
| Message-ID | <875x7ee71j.fsf@example.invalid> (permalink) |
| References | (12 earlier) <868qvc62h7.fsf@linuxsc.com> <87a5fssb70.fsf@nosuchdomain.example.com> <86tsuzeze4.fsf@linuxsc.com> <87zf4q99sh.fsf@example.invalid> <20260302102440.00004a5c@yahoo.com> |
Michael S <already5chosen@yahoo.com> writes:
> On Sun, 01 Mar 2026 19:42:38 -0800
> Keith Thompson <Keith.S.Thompson+u@gmail.com> wrote:
>> Tim Rentsch <tr.17687@z991.linuxsc.com> writes:
[...]
>> > I see no reason to feel an obligation to know whether someone
>> > might feel insulted by something I say.
[...]
>> That's three times today that you've replied to a post I made a
>> long time ago (about a year and a half in this case).
>>
>> I get the impression that you're stalking me.
>
> It is appreciation.
Do you speak for Tim?
[...]
--
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 | Find similar
Re: relearning C: why does an in-place change to a char* segfault? Tim Rentsch <tr.17687@z991.linuxsc.com> - 2026-03-01 18:30 -0800
Re: relearning C: why does an in-place change to a char* segfault? Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2026-03-01 19:42 -0800
Re: relearning C: why does an in-place change to a char* segfault? Michael S <already5chosen@yahoo.com> - 2026-03-02 10:24 +0200
Re: relearning C: why does an in-place change to a char* segfault? Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2026-03-02 04:43 -0800
csiph-web