From: Sam Steingold <sds@gnu.org>
To: emacs-devel@gnu.org
Subject: Re: Proposal to change naming format to allow package-prefix/function-name
Date: Thu, 02 Jan 2020 13:32:39 -0500 [thread overview]
Message-ID: <m1imlt90ag.fsf@gnu.org> (raw)
In-Reply-To: E1im5fC-0005NJ-9n@fencepost.gnu.org
> * Richard Stallman <ezf@tah.bet> [2019-12-30 19:45:34 -0500]:
>
> 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.
Could you please elaborate?
If you are referring to the need to wrap `require` in `eval-when`, then
CLISP dealt with it by handling `require` specially in compiler, so that
--8<---------------cut here---------------start------------->8---
(require 'foo)
(foo:define-foo ...)
--8<---------------cut here---------------end--------------->8---
works just fine.
https://clisp.sourceforge.io/impnotes/require.html
> 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.
Again, could you please clarify what you mean here?
Thanks.
--
Sam Steingold (http://sds.podval.org/)
http://childpsy.net http://calmchildstories.com http://steingoldpsychology.com
https://camera.org https://jij.org http://islamexposedonline.com
I'm a Lisp variable -- bind me!
next prev parent reply other threads:[~2020-01-02 18:32 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
2020-01-02 18:32 ` Sam Steingold [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m1imlt90ag.fsf@gnu.org \
--to=sds@gnu.org \
--cc=emacs-devel@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.