From: Taylan Ulrich Bayirli/Kammer <taylanbayirli@gmail.com>
To: Panicz Maciej Godek <godek.maciek@gmail.com>
Cc: "guile-user@gnu.org" <guile-user@gnu.org>
Subject: Re: Weird module behaviour
Date: Thu, 25 Sep 2014 19:57:36 +0200 [thread overview]
Message-ID: <874mvvmvlb.fsf@taylan.uni.cx> (raw)
In-Reply-To: <CAMFYt2Z=GQ7dSW3U8PONvLyS93MZBeOrBgVaW4ergptbY4p4cA@mail.gmail.com> (Panicz Maciej Godek's message of "Thu, 25 Sep 2014 16:57:04 +0200")
Panicz Maciej Godek <godek.maciek@gmail.com> writes:
> No wonder, since there's not a single mention in the documentation,
> which is perceived as the document that makes things official.
Oh snap. :-)
The stable-2.0 branch has it documented. I also checked and it's even
in 2.0.5 which Debian stable has so the feature should be fine to use in
production code already.
Taylan
next prev parent reply other threads:[~2014-09-25 17:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-25 14:04 Weird module behaviour Panicz Maciej Godek
2014-09-25 14:25 ` Taylan Ulrich Bayirli/Kammer
2014-09-25 14:57 ` Panicz Maciej Godek
2014-09-25 17:57 ` Taylan Ulrich Bayirli/Kammer [this message]
2014-09-25 16:31 ` Barry Schwartz
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=874mvvmvlb.fsf@taylan.uni.cx \
--to=taylanbayirli@gmail.com \
--cc=godek.maciek@gmail.com \
--cc=guile-user@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).