unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: oscarfv@telefonica.net (Óscar Fuentes)
Cc: 23902@debbugs.gnu.org
Subject: bug#23902: 25.1.50; Strange warning on string-collate-equalp's docstring
Date: Wed, 06 Jul 2016 17:34:02 +0300	[thread overview]
Message-ID: <831t36omxx.fsf@gnu.org> (raw)
In-Reply-To: <87vb0jeo56.fsf@telefonica.net> (oscarfv@telefonica.net)

> From: oscarfv@telefonica.net (Óscar Fuentes)
> Date: Wed, 06 Jul 2016 00:05:57 +0200
> 
> The mentioned docstring ends with
> 
>      Do _not_ use this function to compare file names for equality, only
>      for sorting them.
> 
> which makes no sense to me. First of all, what's so special about file
> names to mention them here?

As with any such notes in doc strings, we warn about popular mistakes
that people make frequently.  Trying to compare file names using this
function is such a mistake.  Any string that is actually a kind of
handle to a system object, for which the system itself uses binary
comparison, will do as an example of such a mistake, but doing that
with file names is a common enough example to warrant mentioning.

> And then, how one is supposed to use an
> equality predicate for sorting? (We have string-collate-lessp for that)

A sorting algorithm can have its own ideas what to do when
string-collate-lessp returns zero.  In any case, the important part
here is not to use this function for file-name comparison.





  reply	other threads:[~2016-07-06 14:34 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-05 22:05 bug#23902: 25.1.50; Strange warning on string-collate-equalp's docstring Óscar Fuentes
2016-07-06 14:34 ` Eli Zaretskii [this message]
2016-07-06 15:08   ` Michael Heerdegen
2016-07-06 15:28     ` Eli Zaretskii
2016-07-06 15:46       ` Óscar Fuentes
2016-07-06 16:26         ` Eli Zaretskii
2016-07-06 17:44           ` Óscar Fuentes
2016-07-06 18:32             ` Eli Zaretskii
2016-07-09 17:06           ` Glenn Morris
2016-07-09 17:21             ` Eli Zaretskii
2016-07-09 21:36               ` Óscar Fuentes
2016-07-10  2:40                 ` Eli Zaretskii
2016-07-10  3:06                   ` Michael Heerdegen
2016-07-10 14:40                     ` Eli Zaretskii
2016-07-06 15:55       ` Michael Heerdegen
2016-07-06 16:30         ` Eli Zaretskii
2016-07-06 16:44           ` Michael Heerdegen
2016-07-06 17:18             ` Eli Zaretskii
2016-07-06 22:49               ` Michael Heerdegen
2016-07-07  2:38                 ` Eli Zaretskii
2016-07-07 21:52                   ` Michael Heerdegen
2016-07-08 10:11                     ` Eli Zaretskii
2016-07-08 20:59                       ` Michael Heerdegen
2016-07-09  6:52                         ` Eli Zaretskii
2016-07-09 17:06                           ` Richard Stallman
2016-07-09 22:59                             ` Michael Heerdegen
2016-07-06 15:48   ` Glenn Morris
2016-07-06 16:27     ` 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=831t36omxx.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=23902@debbugs.gnu.org \
    --cc=oscarfv@telefonica.net \
    /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).