From: Alan Mackenzie <acm@muc.de>
To: Nick Andryshak <nandryshak@gmail.com>
Cc: tsdh@gnu.org, emacs-devel@gnu.org
Subject: Re: string> missing?
Date: Wed, 3 Jun 2015 19:13:22 +0000 [thread overview]
Message-ID: <20150603191322.GB18285@acm.fritz.box> (raw)
In-Reply-To: <oirpp5civmg.fsf@gmail.com>
On Wed, Jun 03, 2015 at 12:50:47PM -0400, Nick Andryshak wrote:
> >> > That's just the tip of the iceberg. We have quite a few of other
> >> > similar situations in Emacs Lisp.
> >> I don't think adding in a few small functions to satisfy some
> >> inconsistencies makes the rest of that iceberg very menacing.
> > I see no reason to be "consistent" here. There's no requirement to
> > have in Emacs all possible inequality functions, just for consistency.
> > Now, if there are good reasons to add specifically this function,
> > let's hear them. "Consistency" isn't such a reason, because then we'd
> > need to add gobs of other functions for similar "consistency" reasons.
> What good reasons are there specifically to keep the '>' function? What
> does '(> A B)' do that '(< B A)' doesn't?
For convenience. `>' is used a LOT. It would be a positive pain to be
without it.
On the other hand, `string>' would be used very seldomly. So seldomly,
that it probably wouldn't be worth the space it would fill up. But if
anybody disagrees, he is able to add `string>' to his .emacs, or his own
packages.
> - Nick
--
Alan Mackenzie (Nuremberg, Germany).
next prev parent reply other threads:[~2015-06-03 19:13 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 [this message]
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
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=20150603191322.GB18285@acm.fritz.box \
--to=acm@muc.de \
--cc=emacs-devel@gnu.org \
--cc=nandryshak@gmail.com \
--cc=tsdh@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.