From: Richard Stallman <rms@gnu.org>
To: Zachary Kanfer <zkanfer@gmail.com>
Cc: lekktu@gmail.com, emacs-devel@gnu.org
Subject: Re: Proposal to change naming format to allow package-prefix/function-name
Date: Mon, 30 Dec 2019 19:45:34 -0500 [thread overview]
Message-ID: <E1im5fC-0005NJ-9n@fencepost.gnu.org> (raw)
In-Reply-To: <CAFXT+ROE6LYaCU+0mCf4jMzXCQT5K_-xXnZD279W+EmYmWBERQ@mail.gmail.com> (message from Zachary Kanfer on Mon, 30 Dec 2019 16:50:57 -0500)
[[[ To any NSA and FBI agents reading my email: please consider ]]]
[[[ whether defending the US Constitution against all enemies, ]]]
[[[ foreign or domestic, requires you to follow Snowden's example. ]]]
In Common Lisp, name spaces do not behave cleanly. The reason is that
a symbol's name space has to be recognized when it is read, for the
sake of symbols compared with eq. This is too early to make good choices.
To get clean behavior for name spaces, it is necessary to be able to
choose a symbol's name space based on the execution context when code
is run. Some languages do that, and name spaces are simple and clear
in those languages.
Unless we can find a way to do this right in Lisp -- and I don't see
how that could be -- name spaces will offer no advantage over name
prefixes that are part of the name.
I have no strong opinions about using / or : in symbol names.
--
Dr Richard Stallman
Chief GNUisance of the GNU Project (https://gnu.org)
Founder, Free Software Foundation (https://fsf.org)
Internet Hall-of-Famer (https://internethalloffame.org)
next prev parent reply other threads:[~2019-12-31 0:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-30 7:02 Proposal to change naming format to allow package-prefix/function-name Zachary Kanfer
2019-12-30 12:03 ` Juanma Barranquero
2019-12-30 13:12 ` Elias Mårtenson
2019-12-30 21:50 ` Zachary Kanfer
2019-12-31 0:45 ` Richard Stallman [this message]
2020-01-02 18:32 ` Sam Steingold
2019-12-31 0:06 ` Adam Porter
2019-12-31 10:14 ` Lars Ingebrigtsen
2019-12-31 10:54 ` Ihor Radchenko
2019-12-31 12:06 ` Clemens Radermacher
2019-12-31 14:48 ` Teemu Likonen
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=E1im5fC-0005NJ-9n@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=lekktu@gmail.com \
--cc=zkanfer@gmail.com \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).