From: "Stephen J. Turnbull" <stephen@xemacs.org>
To: Stefan Monnier <monnier@IRO.UMontreal.CA>
Cc: Eli Zaretskii <eliz@gnu.org>, Nicolas Petton <nicolas@petton.fr>,
emacs-devel@gnu.org
Subject: Re: map.el and naming
Date: Wed, 04 Mar 2015 11:07:53 +0900 [thread overview]
Message-ID: <87wq2xa51i.fsf@uwakimon.sk.tsukuba.ac.jp> (raw)
In-Reply-To: <jwvr3t69gyv.fsf-monnier+emacs@gnu.org>
Stefan Monnier writes:
> > Please, let's not go there.
>
> You must have missed the "Think of" part of my answer. OO is not
> just a bunch of programming language semantics, but is also a way
> to think about and design programs.
I don't see how "Think of" makes a difference. We're not talking
about designing programs here, we're talking about designing
languages, specifically Emacs Lisp. The question is how much
object-orientation of Emacs Lisp primitive types can we implement in
Lisp, and the answer AFAICS is "no more than we already have".
In any case, my main point was that I don't see why seq.el and map.el,
with their pseudo-namespace prefixes, are a good idea for Emacs Lisp.
Sure, if there are useful new operations, add them; if they can be
polymorphic with mnemonic names, better yet. But AFAICS most of the
interesting polymorphism is already available through functions like
nth. There's a reason why setnth doesn't exist, you know. And
mnemonic synonyms (first, rest, ...) are common already. (Similarly,
there's a reason why rest isn't polymorphic over arrays and strings.)
A wholesale cleanup isn't going to be possible without the kind of
effort required to change the underlying Lisp engine to a Scheme or
Common Lisp implementation. So AFAICS these pseudo-namespaces are not
going to improve the language.
next prev parent reply other threads:[~2015-03-04 2:07 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-28 12:24 map.el and naming Nicolas Petton
2015-02-28 13:32 ` Bozhidar Batsov
2015-03-03 15:58 ` bburns.km
2015-03-04 7:51 ` Nicolas Petton
2015-03-04 9:38 ` Nic Ferrier
2015-02-28 13:49 ` Eli Zaretskii
2015-02-28 16:21 ` Artur Malabarba
2015-03-02 5:31 ` Stefan Monnier
2015-03-02 7:38 ` Nicolas Petton
2015-03-02 13:20 ` Eli Zaretskii
2015-03-02 13:26 ` Nicolas Petton
2015-03-02 13:55 ` Eli Zaretskii
2015-03-02 14:33 ` Artur Malabarba
2015-03-02 14:49 ` Eli Zaretskii
2015-03-02 15:08 ` Artur Malabarba
2015-03-02 15:24 ` Stephen J. Turnbull
2015-03-02 16:53 ` Stefan Monnier
2015-03-03 3:14 ` Stephen J. Turnbull
2015-03-03 16:36 ` Stefan Monnier
2015-03-04 2:07 ` Stephen J. Turnbull [this message]
2015-03-02 5:29 ` Stefan Monnier
2015-03-02 13:59 ` Nicolas Petton
2015-04-11 0:52 ` Nicolas Petton
2015-04-11 13:53 ` Stefan Monnier
2015-04-11 14:07 ` Nicolas Petton
2015-04-11 13:55 ` Stefan Monnier
2015-04-11 14:11 ` Nicolas Petton
2015-04-11 14:24 ` John Yates
2015-04-11 14:32 ` Dmitry Gutov
2015-04-11 19:54 ` Artur Malabarba
2015-04-12 3:32 ` Stefan Monnier
2015-04-11 14:21 ` Artur Malabarba
2015-04-12 3:25 ` Stefan Monnier
2015-04-11 14:20 ` John Yates
2015-04-11 21:44 ` John Mastro
2015-04-12 3:34 ` Stefan Monnier
2015-04-12 7:12 ` Daniel Colascione
2015-04-12 11:48 ` Stefan Monnier
2015-04-12 11:59 ` Nicolas Petton
2015-04-12 12:53 ` Stefan Monnier
2015-04-12 13:38 ` Stephen J. Turnbull
2015-04-12 14:22 ` Yuri Khan
2015-04-12 14:52 ` Nicolas Petton
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=87wq2xa51i.fsf@uwakimon.sk.tsukuba.ac.jp \
--to=stephen@xemacs.org \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=monnier@IRO.UMontreal.CA \
--cc=nicolas@petton.fr \
/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.