all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: Michael Heerdegen <michael_heerdegen@web.de>,
	Lars Ingebrigtsen <larsi@gnus.org>
Cc: 42323@debbugs.gnu.org
Subject: bug#42323: 26.3; Doc string of `seq-map'
Date: Wed, 9 Dec 2020 12:00:57 -0800 (PST)	[thread overview]
Message-ID: <9c2837ca-af6a-4a38-92a3-5f6ad7e739cc@default> (raw)
In-Reply-To: <87tusuye8u.fsf@web.de>

FWIW, the notion of separation of interface from
implementation is not so clear for Lisp, and even
less so for Free Software Lisp.

Something implemented in "core" Emacs but in Lisp
is no more "the real thing" than the same thing
re-implemented by some user.  People can and do
reuse or modify "implementation" code.  And user
code sometimes does depend on how something is
"implemented".

In a way, take to an extreme, you could consider
the Lisp code distributed as part of GNU Emacs as
a "suggestion" to users.  (The C code as well,
but Lisp is particularly susceptible to, and even
invites, hacking, opportunistically or otherwise.)





  reply	other threads:[~2020-12-09 20:00 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-11 16:01 bug#42323: 26.3; Doc string of `seq-map' Drew Adams
2020-12-09 13:41 ` Lars Ingebrigtsen
2020-12-09 16:11   ` Michael Heerdegen
2020-12-09 16:44     ` Lars Ingebrigtsen
2020-12-09 19:24       ` Michael Heerdegen
2020-12-09 20:00         ` Drew Adams [this message]
2020-12-09 20:19         ` Lars Ingebrigtsen
2021-09-25 15:25   ` Stefan Kangas
2021-09-25 16:10     ` bug#42323: [External] : " Drew Adams
2021-09-25 16:21       ` Eli Zaretskii
2021-09-25 16:43         ` Stefan Kangas
2021-09-25 16:28       ` Stefan Kangas

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=9c2837ca-af6a-4a38-92a3-5f6ad7e739cc@default \
    --to=drew.adams@oracle.com \
    --cc=42323@debbugs.gnu.org \
    --cc=larsi@gnus.org \
    --cc=michael_heerdegen@web.de \
    /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.