From: Drew Adams <drew.adams@oracle.com>
To: Nicolas Richard <theonewiththeevillook@yahoo.fr>
Cc: 19932@debbugs.gnu.org
Subject: bug#19932: 25.0.50; doc string of `elisp--eval-last-sexp'
Date: Wed, 25 Feb 2015 09:05:14 -0800 (PST) [thread overview]
Message-ID: <19414826-ceac-4808-b1a6-892e0f56020a@default> (raw)
In-Reply-To: <54EDFD09.50200@yahoo.fr>
> > Of course. And "private" means nothing in the context of Emacs Lisp.
>
> It means whatever we want it to mean when we use the word. I think we
> all (more or less) understand what it means in the current context,
> don't we ?
Nope. You won't find it anywhere in the Emacs or Elisp doc, I'll bet.
Or even in the source code (unless perhaps in some C code somewhere,
as a comment).
Use of the term here, by Dmitry, is new in the context of Emacs, AFAIK.
I'll bet that even if you search bug reports and emacs-devel threads you
won't find that term used.
(And "internal" (also nebulous/dubious in the context of Emacs) is not
the same as "private".)
"Private", for software, is typically about encapsulation/visibility
and modules. You could make a case that a notion of such privacy
(importing, exporting etc.) exists in Common Lisp, wrt its packages.
But no such module system exists for Elisp.
If/when we add a module system to Elisp, then we can perhaps speak of
things being "private". And even then the notion would no doubt be
relative, as it is in, say, Common Lisp.
prev parent reply other threads:[~2015-02-25 17:05 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-23 21:20 bug#19932: 25.0.50; doc string of `elisp--eval-last-sexp' Drew Adams
2015-02-24 21:01 ` Dmitry Gutov
2015-02-24 21:26 ` Drew Adams
2015-02-25 4:06 ` Stefan Monnier
2015-02-25 10:52 ` Nicolas Richard
2015-02-25 11:17 ` Dmitry Gutov
2015-02-25 12:12 ` Nicolas Richard
2015-02-25 12:44 ` Dmitry Gutov
2015-02-25 15:18 ` Nicolas Richard
2015-02-25 16:39 ` Drew Adams
2015-02-25 16:36 ` Drew Adams
2015-02-25 16:39 ` Dmitry Gutov
2015-02-25 16:45 ` Drew Adams
2015-02-25 16:49 ` Nicolas Richard
2015-02-25 17:05 ` Drew Adams [this message]
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=19414826-ceac-4808-b1a6-892e0f56020a@default \
--to=drew.adams@oracle.com \
--cc=19932@debbugs.gnu.org \
--cc=theonewiththeevillook@yahoo.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.