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


Groups > comp.lang.c > #388535

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

Path csiph.com!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail
From Tim Rentsch <tr.17687@z991.linuxsc.com>
Newsgroups comp.lang.c
Subject Re: relearning C: why does an in-place change to a char* segfault?
Date Fri, 27 Sep 2024 17:33:56 -0700
Organization A noiseless patient Spider
Lines 8
Message-ID <868qvc62h7.fsf@linuxsc.com> (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>
MIME-Version 1.0
Content-Type text/plain; charset=us-ascii
Injection-Date Sat, 28 Sep 2024 02:33:56 +0200 (CEST)
Injection-Info dont-email.me; posting-host="8f5b490802ead3c9705b43cb022c8c76"; logging-data="983048"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1972UTeGlIfaSMOvzhocBKmSm4fPssjt98="
User-Agent Gnus/5.11 (Gnus v5.11) Emacs/22.4 (gnu/linux)
Cancel-Lock sha1:Uab2+/Df9MttomojICWLfEBXi4k= sha1:ozOTjGIkcxHzoJKAi9wBLWwD1xU=
Xref csiph.com comp.lang.c:388535

Show key headers only | View raw


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.

Back to comp.lang.c | Previous | NextNext in thread | Find similar


Thread

Re: relearning C: why does an in-place change to a char* segfault? Tim Rentsch <tr.17687@z991.linuxsc.com> - 2024-09-27 17:33 -0700
  Re: relearning C: why does an in-place change to a char* segfault? Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2024-09-27 20:34 -0700
    Re: relearning C: why does an in-place change to a char* segfault? Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2024-09-28 07:22 +0200
      Re: relearning C: why does an in-place change to a char* segfault? Phillip Frabott <nntp@fulltermprivacy.com> - 2024-09-28 17:57 +0000
        Re: relearning C: why does an in-place change to a char* segfault? Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2024-09-28 13:42 -0700
          Re: relearning C: why does an in-place change to a char* segfault? Phillip Frabott <nntp@fulltermprivacy.com> - 2024-09-28 22:05 +0000
            Re: relearning C: why does an in-place change to a char* segfault? Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2024-09-28 15:17 -0700

csiph-web