From: Eli Zaretskii <eliz@gnu.org>
To: Nick Andryshak <nandryshak@gmail.com>
Cc: nicolas@petton.fr, emacs-devel@gnu.org, tsdh@gnu.org
Subject: Re: string> missing?
Date: Wed, 03 Jun 2015 19:42:14 +0300 [thread overview]
Message-ID: <83pp5crbfd.fsf@gnu.org> (raw)
In-Reply-To: <oirr3psixh1.fsf@gmail.com>
> From: Nick Andryshak <nandryshak@gmail.com>
> Cc: tsdh@gnu.org, nicolas@petton.fr, emacs-devel@gnu.org
> Date: Wed, 03 Jun 2015 12:10:50 -0400
>
> >> Why would a language have '<' without '>'?
> >
> > Because it's enough?
>
> Should 'enough' be considered an acceptable standard?
Yes.
> Quote, atom, eq, cons, car, cdr, and cond are 'enough', right?
No.
> > 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.
> I understand where you're coming from with this argument, but I
> don't really buy it.
Then don't. It's OK to disagree about something, nothing wrong about
that. Fortunately, you can have this function for you, if you need
it, with a simple one-liner.
next prev parent reply other threads:[~2015-06-03 16:42 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 [this message]
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
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=83pp5crbfd.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=nandryshak@gmail.com \
--cc=nicolas@petton.fr \
--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.