From: taylanbayirli@gmail.com (Taylan Ulrich Bayırlı/Kammer)
To: Alpha Omega <cape.wrath@openmailbox.org>
Cc: guile-user@gnu.org
Subject: Re: Rationale behind the module paths in definition of the module
Date: Thu, 08 Jan 2015 12:48:32 +0100 [thread overview]
Message-ID: <87ioghtrvz.fsf@taylan.uni.cx> (raw)
In-Reply-To: <f266086f05c7836c39b7cbc04bb7ed56@openmailbox.org> (Alpha Omega's message of "Thu, 08 Jan 2015 11:21:53 +0000")
Alpha Omega <cape.wrath@openmailbox.org> writes:
> I am just curious about the decision to embed path info in the module
> file itself.
The '(foo bar baz)' is not path info, it's the name of the module. :-)
The filesystem path mimics the components of the module name.
Taylan
next prev parent reply other threads:[~2015-01-08 11:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-08 9:33 Rationale behind the module paths in definition of the module Alpha Omega
2015-01-08 10:17 ` Ludovic Courtès
2015-01-08 11:21 ` Alpha Omega
2015-01-08 11:48 ` Taylan Ulrich Bayırlı/Kammer [this message]
2015-01-08 13:36 ` Amirouche Boubekki
2015-01-08 14:46 ` Taylan Ulrich Bayırlı/Kammer
2015-01-10 10:50 ` Alpha Omega
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=87ioghtrvz.fsf@taylan.uni.cx \
--to=taylanbayirli@gmail.com \
--cc=cape.wrath@openmailbox.org \
--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).