[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Returning argument string (regexp-quote)
From: |
Eli Zaretskii |
Subject: |
Re: Returning argument string (regexp-quote) |
Date: |
Tue, 24 Sep 2019 19:20:09 +0300 |
> Feedback-ID: address@hidden
> From: Mattias Engdegård <address@hidden>
> Date: Tue, 24 Sep 2019 13:28:15 +0200
>
> More generally, do we need to preserve allocation for functions not
> specifically documented to return new strings? I can imagine there being code
> that depend on it by accident, but string mutation is rare.
I think the benefits from such general changes are barely tangible,
whereas the risk of breaking someone's (perhaps even ours) code are
real. So I don't think we should do that, not in general.
- Returning argument string (regexp-quote), Mattias Engdegård, 2019/09/24
- Re: Returning argument string (regexp-quote), Andreas Schwab, 2019/09/24
- Re: Returning argument string (regexp-quote),
Eli Zaretskii <=
- Re: Returning argument string (regexp-quote), Mattias Engdegård, 2019/09/24
- Re: Returning argument string (regexp-quote), Paul Eggert, 2019/09/24
- Re: Returning argument string (regexp-quote), Eli Zaretskii, 2019/09/24
- Re: Returning argument string (regexp-quote), Mattias Engdegård, 2019/09/25
- Re: Returning argument string (regexp-quote), Eli Zaretskii, 2019/09/25
- Compilation failure on macOS 10.15 Catalina, Zach Pearson, 2019/09/25
- Re: Compilation failure on macOS 10.15 Catalina, mituharu, 2019/09/25
- Re: Compilation failure on macOS 10.15 Catalina, Zach Pearson, 2019/09/25
- Re: Compilation failure on macOS 10.15 Catalina, mituharu, 2019/09/25
- Re: Compilation failure on macOS 10.15 Catalina, Zach Pearson, 2019/09/25