From: ludo@gnu.org (Ludovic Courtès)
To: guile-devel@gnu.org
Subject: Re: rename from q to queue
Date: Thu, 14 Apr 2016 16:15:52 +0200 [thread overview]
Message-ID: <87y48g8eef.fsf@gnu.org> (raw)
In-Reply-To: 8737qrjh9l.fsf@gnu.org
Mathieu Lirzin <mthl@gnu.org> skribis:
> One way to not break backward compatibility, would be to move (ice-9 q)
> code in (ice-9 queue) and make (ice-9 q) use it and re-export every
> variable with its old name.
Right.
> Finally we will need a way to give the information that (ice-9 q) module
> is deprectated to the users. I am not sure what is the best way to
> achieve this. Maybe with:
>
> (eval-when (expand load eval)
> (display "..." (current-warning-port)))
>
> What do others think?
We could do a quick hack to iterate over the exported bindings,
re-export them, and print a message.
However, I think it would be best to have a mechanism in the module
abstraction to /declare/ renames. That would allow both the compiler
and the run-time support to emit an appropriate warning.
This would require something like adding a special field to ‘module’
records, such that one can write, say:
(define-module (ice-9 q)
#:superseded-by (ice-9 queue))
With that in place, it will become much easier to discuss about ice-9
renames, IMO.
Thoughts?
Thanks,
Ludo’.
next prev parent reply other threads:[~2016-04-14 14:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-11 17:29 rename from q to queue rain1
2016-04-12 3:55 ` Christopher Allan Webber
2016-04-12 4:02 ` Nala Ginrut
2016-04-12 9:41 ` Mathieu Lirzin
2016-04-14 14:15 ` Ludovic Courtès [this message]
2016-04-14 19:35 ` Christopher Allan Webber
2016-04-15 8:10 ` 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=87y48g8eef.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guile-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.
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).