From: Mark H Weaver <mhw@netris.org>
To: ludo@gnu.org (Ludovic Courtès)
Cc: 17418@debbugs.gnu.org
Subject: bug#17418: #:select gives access to private variables
Date: Tue, 03 Jun 2014 19:08:54 -0400 [thread overview]
Message-ID: <87ioohvbeh.fsf@yeeloong.lan> (raw)
In-Reply-To: <87vbsj4ttv.fsf@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\= \=\?utf-8\?Q\?s\?\= message of "Mon, 02 Jun 2014 10:08:28 +0200")
ludo@gnu.org (Ludovic Courtès) writes:
> Mark H Weaver <mhw@netris.org> skribis:
>
>> Perhaps we should consider making #:select issue a warning when it
>> imports private bindings,
>
> Yes, sounds like a good idea.
Sounds good. Specifically, I guess we should deprecate this way of
using #:select.
If you do this, can you adjust system/repl/coop-server.scm to avoid it?
It imports the following private bindings:
start-repl* run-server* add-open-socket! close-socket!
>> and also adding a mechanism to import private bindings without a
>> warning.
>
> I’m unsure about this. Normally we don’t want to allow that, because
> that defeats the purpose of modules.
Fair enough. Having mulled it over, I tend to agree that we should not
try to make this more convenient.
> OTOH, in practice we occasionally need this ability; I typically use
> @@ for that, but it’s not as nice as a real import.
I think asking people to use @@ is reasonable here.
Thanks,
Mark
next prev parent reply other threads:[~2014-06-03 23:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-06 8:48 bug#17418: #:select gives access to private variables Ludovic Courtès
2014-06-02 1:06 ` Mark H Weaver
2014-06-02 8:08 ` Ludovic Courtès
2014-06-03 23:08 ` Mark H Weaver [this message]
2014-06-03 23:11 ` Mark H Weaver
2016-06-21 14:03 ` Andy Wingo
2016-06-21 14:52 ` Ludovic Courtès
2016-06-21 15:17 ` Andy Wingo
2016-06-21 16:06 ` Ludovic Courtès
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/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87ioohvbeh.fsf@yeeloong.lan \
--to=mhw@netris.org \
--cc=17418@debbugs.gnu.org \
--cc=ludo@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.
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).