From: Neil Jerram <neil@ossau.homelinux.net>
To: guile-user@gnu.org
Subject: Re: Using . in module names
Date: Fri, 3 Jun 2016 09:44:51 +0100 [thread overview]
Message-ID: <57514383.3080501@ossau.homelinux.net> (raw)
In-Reply-To: <3813b138-93f1-a451-82fc-58d57c977274@cbaines.net>
On 03/06/16 08:57, Christopher Baines wrote:
> From reading the documentation, I would expect this to work, as . is
> valid in symbols? But from trying this out, it does not seem to (the
> module cannot be loaded).
>
> Does anyone have information about this?
>
I think you should provide the complete example of what isn't working.
It's not clear to me if you mean
(define-module (.) ...)
or
(define-module (.something) ...)
or
(define-module (something . else) ...)
etc.
Regards,
Neil
next prev parent reply other threads:[~2016-06-03 8:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-03 7:57 Using . in module names Christopher Baines
2016-06-03 8:44 ` Neil Jerram [this message]
2016-06-03 11:54 ` Taylan Ulrich Bayırlı/Kammer
2016-06-03 12:03 ` Marko Rauhamaa
2016-06-03 12:17 ` Taylan Ulrich Bayırlı/Kammer
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=57514383.3080501@ossau.homelinux.net \
--to=neil@ossau.homelinux.net \
--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).