unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Dmitry Gutov <dgutov@yandex.ru>
To: Dmitry Antipov <dmantipov@yandex.ru>,
	 Stefan Monnier <monnier@iro.umontreal.ca>
Cc: emacs-devel@gnu.org
Subject: Re: trunk r117396: Do not allow out-of-range character position in Fcompare_strings.
Date: Wed, 25 Jun 2014 19:19:59 +0300	[thread overview]
Message-ID: <53AAF6AF.5070907@yandex.ru> (raw)
In-Reply-To: <53AAF174.40002@yandex.ru>

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



      reply	other threads:[~2014-06-25 16:19 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E1WzkZx-0001rH-5h@vcs.savannah.gnu.org>
2014-06-25 13:22 ` trunk r117396: Do not allow out-of-range character position in Fcompare_strings Dmitry
2014-06-25 13:46   ` Dmitry Antipov
2014-06-25 15:17     ` Stefan Monnier
2014-06-25 15:57       ` Dmitry Antipov
2014-06-25 16:19         ` Dmitry Gutov [this message]

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=53AAF6AF.5070907@yandex.ru \
    --to=dgutov@yandex.ru \
    --cc=dmantipov@yandex.ru \
    --cc=emacs-devel@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    /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).