|
From: | Dmitry Gutov |
Subject: | Re: trunk r117396: Do not allow out-of-range character position in Fcompare_strings. |
Date: | Wed, 25 Jun 2014 19:19:59 +0300 |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0 |
On 06/25/2014 06:57 PM, Dmitry Antipov wrote:
May be I just misunderstood the development/release process as a whole, but what "it's too late" means for the trunk?
Too late to changes APIs that have been in use for a long time, I suppose.
We don't have the behavior for aref, but we do have it for nth and gethash and people frequently rely on this behavior.Hm...lists are mutable - you can concatenate A and B (with setcdr) and get changed A but not the copy of A + B. On the other side, I always consider strings and vectors as "less mutable", which implies more strict checking (as with aref and aset).
To avoid rehashing the same argument, here's the previous discussion: http://lists.gnu.org/archive/html/emacs-devel/2012-07/msg00313.html
I can check other external packages as well. Emacspeak?
You can look here, too: https://github.com/search?l=emacs-lisp&q=compare-strings&ref=cmdform&type=Code
[Prev in Thread] | Current Thread | [Next in Thread] |