From: Thibaut Verron <thibaut.verron@gmail.com>
To: emacs-devel@gnu.org
Subject: Re: string> missing?
Date: Wed, 3 Jun 2015 21:36:05 +0000 (UTC) [thread overview]
Message-ID: <loom.20150603T232536-391@post.gmane.org> (raw)
In-Reply-To: oiroakwio21.fsf@gmail.com
Nick Andryshak <nandryshak <at> gmail.com> writes:
> Having one comparison operator without the other is simply confusing to
> developers. If I'm writing code where '<' exists and works, I believe
> it's reasonable for me to assume that '>' will also. Apply this same
> logic to string< and string>.
>
I did run into a similar issue not long ago, when I had to test for emacs
version in my .emacs. It took me a few minutes to find out that no,
version> doesn't exist. It left me with a bitter taste of waste, like some
simplicity that was given up for no apparent reason.
But I could see a possible reason for this missing function: version> and
version< are not as symmetrical as they would seem, and writing code "for
all emacs versions more recent than this one" is almost certainly going to
break something in the future.
What is understandable for version> seems to be nonsense for string>
though. In this case, the functions are symmetrical, why have one and not
the other?
And about the additional string<= and string>=, I'd say these are even
more useful, because testing strings for equality in emacs lisp is already
tricky enough! And, it is possible to test if a string is less than or
equal to another faster than the combination of both tests.
Thibaut
next prev parent reply other threads:[~2015-06-03 21:36 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-03 9:05 string> missing? Nicolas Petton
2015-06-03 14:51 ` Eli Zaretskii
2015-06-03 15:03 ` Nicolas Petton
2015-06-03 15:26 ` Tassilo Horn
2015-06-03 15:46 ` Nick Andryshak
2015-06-03 15:55 ` Eli Zaretskii
2015-06-03 16:10 ` Nick Andryshak
2015-06-03 16:42 ` Eli Zaretskii
2015-06-03 16:50 ` Nick Andryshak
2015-06-03 18:10 ` Andreas Schwab
2015-06-03 19:13 ` Alan Mackenzie
2015-06-03 19:13 ` Eli Zaretskii
2015-06-03 19:34 ` Nick Andryshak
2015-06-03 19:53 ` Eli Zaretskii
2015-06-03 20:11 ` Nick Andryshak
2015-06-03 20:37 ` Jay Belanger
2015-06-03 20:53 ` Nick Andryshak
2015-06-03 21:35 ` Jay Belanger
2015-06-03 21:36 ` Thibaut Verron [this message]
2015-06-03 22:25 ` Stefan Monnier
2015-06-04 5:30 ` Thibaut Verron
2015-06-04 7:44 ` Nicolas Richard
2015-06-04 8:08 ` Thibaut Verron
2015-06-04 15:33 ` Stefan Monnier
2015-06-03 22:28 ` Stefan Monnier
2015-06-04 2:50 ` Eli Zaretskii
2015-06-04 6:43 ` Tassilo Horn
2015-06-04 7:02 ` Bozhidar Batsov
2015-06-04 7:53 ` Gnus & Mail-Followup-To (was: string> missing?) Nicolas Richard
2015-06-04 9:04 ` Gnus & Mail-Followup-To Tassilo Horn
2015-06-04 12:50 ` Nicolas Richard
2015-06-05 17:07 ` Tassilo Horn
2015-06-06 8:48 ` Nicolas Richard
2015-06-04 4:20 ` string> missing? Thierry Volpiatto
2015-06-04 15:52 ` Nicolas Petton
2015-06-03 21:24 ` Richard Stallman
2015-06-04 15:07 ` Eli Zaretskii
2015-06-05 17:56 ` Richard Stallman
2015-06-05 19:04 ` Eli Zaretskii
2015-06-05 20:40 ` Tassilo Horn
2015-06-05 21:35 ` Ivan Shmakov
2015-06-05 21:53 ` Tassilo Horn
2015-06-05 22:04 ` Tassilo Horn
2015-06-06 6:40 ` Eli Zaretskii
2015-06-06 8:53 ` Tassilo Horn
2015-06-07 0:28 ` Richard Stallman
2015-06-06 1:52 ` Richard Stallman
2015-06-06 7:57 ` Eli Zaretskii
2015-06-07 0:28 ` Richard Stallman
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=loom.20150603T232536-391@post.gmane.org \
--to=thibaut.verron@gmail.com \
--cc=emacs-devel@gnu.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.