From: Andy Wingo <wingo@pobox.com>
To: ludo@gnu.org (Ludovic Courtès)
Cc: 17418-done@debbugs.gnu.org
Subject: bug#17418: #:select gives access to private variables
Date: Tue, 21 Jun 2016 17:17:20 +0200 [thread overview]
Message-ID: <87wpliwozj.fsf@pobox.com> (raw)
In-Reply-To: <87ziqe7fx2.fsf@gnu.org> ("Ludovic Courtès"'s message of "Tue, 21 Jun 2016 16:52:25 +0200")
On Tue 21 Jun 2016 16:52, ludo@gnu.org (Ludovic Courtès) writes:
> Andy Wingo <wingo@pobox.com> skribis:
>
>> On Wed 04 Jun 2014 01:11, Mark H Weaver <mhw@netris.org> writes:
>>
>>> Mark H Weaver <mhw@netris.org> writes:
>>>> 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!
>>>
>>> Also: prompting-meta-read
>>
>> Fixed in master.
>
> I would not close the bug if it remains in 2.0.x. Thoughts?
I think we can't break 2.0 in this regard; it's technically
incompatible. We could print a better deprecation warning but in this
case I think I did the right thing. WDYT?
A
next prev parent reply other threads:[~2016-06-21 15:17 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
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 [this message]
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=87wpliwozj.fsf@pobox.com \
--to=wingo@pobox.com \
--cc=17418-done@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).