From: Eli Zaretskii <eliz@gnu.org>
To: "Mattias Engdegård" <mattiase@acm.org>
Cc: 42296@debbugs.gnu.org
Subject: bug#42296: 27.0.91; Correct manual entry for 'concat' w.r.t. allocation [PATCH]
Date: Sat, 11 Jul 2020 14:52:25 +0300 [thread overview]
Message-ID: <83o8omnu9y.fsf@gnu.org> (raw)
In-Reply-To: <87CAAEDE-4AE2-4224-A3E3-6597E6449B1D@acm.org> (message from Mattias Engdegård on Sat, 11 Jul 2020 13:15:39 +0200)
> From: Mattias Engdegård <mattiase@acm.org>
> Date: Sat, 11 Jul 2020 13:15:39 +0200
> Cc: 42296@debbugs.gnu.org
>
> In particular, the returned value should not be altered, because doing
> so may inadvertently change another string, alter a constant string in
> the program, or even raise an error.
Too definitive to my palate, sorry.
You may wish reading the recent long discussions of what is/should be
and what isn't/shouldn't be immutable. Turns out some of us are very
sensitive to "should not" being used where "we recommend you not" or
"make sure you know what you are doing" is what actually is the truth.
Once again, we are not talking to kindergarten kids.
next prev parent reply other threads:[~2020-07-11 11:52 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-09 15:54 bug#42296: 27.0.91; Correct manual entry for 'concat' w.r.t. allocation [PATCH] Mattias Engdegård
2020-07-09 17:31 ` Eli Zaretskii
2020-07-09 17:56 ` Mattias Engdegård
2020-07-09 18:51 ` Eli Zaretskii
2020-07-09 19:17 ` Mattias Engdegård
2020-07-09 19:24 ` Eli Zaretskii
2020-07-10 17:04 ` Mattias Engdegård
2020-07-10 18:08 ` Eli Zaretskii
2020-07-11 11:15 ` Mattias Engdegård
2020-07-11 11:52 ` Eli Zaretskii [this message]
2020-07-11 12:51 ` Mattias Engdegård
2020-07-11 13:07 ` Eli Zaretskii
2020-07-11 13:16 ` Mattias Engdegård
2020-07-11 13:37 ` Eli Zaretskii
2020-07-11 13:47 ` Mattias Engdegård
2020-07-11 16:17 ` Drew Adams
2020-07-12 3:03 ` Richard Stallman
2020-07-09 19:20 ` Eli Zaretskii
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83o8omnu9y.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=42296@debbugs.gnu.org \
--cc=mattiase@acm.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).