From: Mathieu Lirzin <mthl@gnu.org>
To: rain1@openmailbox.org
Cc: guile-devel@gnu.org
Subject: Re: rename from q to queue
Date: Tue, 12 Apr 2016 11:41:42 +0200 [thread overview]
Message-ID: <8737qrjh9l.fsf@gnu.org> (raw)
In-Reply-To: <11ca009a333f511d7510d4bc8671e409@openmailbox.org> (rain1@openmailbox.org's message of "Mon, 11 Apr 2016 17:29:40 +0000")
Hello,
rain1@openmailbox.org writes:
> The following library uses a pun writing 'q' instead of 'queue':
> <http://www.gnu.org/software/guile/manual/html_node/Queues.html>
>
> I propose renaming the module from (ice-9 q) to (ice-9 queue) and
> spelling queue throughout in the usual scheme style of using full
> words.
>
> Attached is a patch that does this. If there is a positive consensus
> on the rename I am happy to apply the change to all the documentation
> and tests too.
As stated on IRC I think it is an improvement to have a meaningful name
for this module.
However as pointed in other replies, It is not possible to implement it
this way because (ice-9 q) is a public API.
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.
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?
--
Mathieu Lirzin
next prev parent reply other threads:[~2016-04-12 9:41 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 [this message]
2016-04-14 14:15 ` Ludovic Courtès
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=8737qrjh9l.fsf@gnu.org \
--to=mthl@gnu.org \
--cc=guile-devel@gnu.org \
--cc=rain1@openmailbox.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).