Groups | Search | Server Info | Login | Register
Groups > comp.lang.c > #396717
| Path | csiph.com!eternal-september.org!feeder.eternal-september.org!nntp.eternal-september.org!.POSTED!not-for-mail |
|---|---|
| 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 | Sun, 01 Mar 2026 19:42:38 -0800 |
| Organization | None to speak of |
| Lines | 35 |
| Message-ID | <87zf4q99sh.fsf@example.invalid> (permalink) |
| References | <IoGcndcJ1Zm83zb7nZ2dnZfqnPWdnZ2d@brightview.co.uk> <v8fhhl$232oi$1@dont-email.me> <v8fn2u$243nb$1@dont-email.me> <87jzh0gdru.fsf@nosuchdomain.example.com> <v8gte2$2ceis$2@dont-email.me> <20240801174256.890@kylheku.com> <v8i9o8$2oof8$1@dont-email.me> <v8j808$2us0r$1@dont-email.me> <864j7oszhu.fsf@linuxsc.com> <87o75vg9ot.fsf@nosuchdomain.example.com> <86ikw1o0h8.fsf@linuxsc.com> <8734n5fjtq.fsf@nosuchdomain.example.com> <868qvc62h7.fsf@linuxsc.com> <87a5fssb70.fsf@nosuchdomain.example.com> <86tsuzeze4.fsf@linuxsc.com> |
| MIME-Version | 1.0 |
| Content-Type | text/plain |
| Injection-Date | Mon, 02 Mar 2026 03:42:39 +0000 (UTC) |
| Injection-Info | dont-email.me; posting-host="904fdc8ce99c4265d8d70c325ce3d825"; logging-data="847899"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1/h1wOoMB5hlFRyD7jv7/0/" |
| User-Agent | Gnus/5.13 (Gnus v5.13) |
| Cancel-Lock | sha1:OrL59esMzBKR0eLa8UMwBwcAxwk= sha1:/1Nw1e2+uDa+GDy5gcAomUrpFeI= |
| Xref | csiph.com comp.lang.c:396717 |
Show key headers only | View raw
Tim Rentsch <tr.17687@z991.linuxsc.com> writes:
> Keith Thompson <Keith.S.Thompson+u@gmail.com> writes:
>> 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.
>
> I see no reason to feel an obligation to know whether someone
> might feel insulted by something I say. Feeling insulted is a
> subjective reaction, not an objective truth. If someone said
> to me "it isn't surprising that you dislike C++" I might agree
> (or not) with them, but I don't feel insulted by it; all they
> are doing is giving their subjective reaction to my behavior.
>
> On the contrary, it seems presumptuous of you to judge that it
> was my intention to insult you. In cases where I'm not sure
> about what someone meant by something, I try to ask them what
> they meant rather than jump to a conclusion. Admittedly, I
> don't always succeed, but I do try to follow that policy.
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. Please note that
I have not asked whether that's your intent. I find it extremely
annoying, for reasons I don't intend to explain further. I again
encourage you to knock it off.
--
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
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