unofficial mirror of bug-guile@gnu.org 
 help / color / mirror / Atom feed
From: lloda <lloda@sarc.name>
To: Jan <tona_kosmicznego_smiecia@interia.pl>
Cc: 35315@debbugs.gnu.org
Subject: bug#35315: It's not a bug, sorry
Date: Tue, 23 Apr 2019 00:33:08 +0200	[thread overview]
Message-ID: <DD272180-CCF1-47D6-91DC-7B6122044EBE@sarc.name> (raw)
In-Reply-To: <suissjwgmwurrwpnxlfv@qpzn>

[-- Attachment #1: Type: text/plain, Size: 814 bytes --]


> On 22 Apr 2019, at 23:45, Jan <tona_kosmicznego_smiecia@interia.pl> wrote:
> 
> I've found out it's not a bug, I just didn't  add (define-module (my-modules displays)) - the name of the folder to my module. Sorry for that.
> 
> Have a nice day!
> 
> 
> --
> Jan
> 


Tbh I've always find this requirement a bit annoying. Clearly in an inline definition the full name must be given, but if the module is found through the path, which is the most common case, all you get from the module declaration is a chance to make a mistake.

I guess I'd like for it to be a nameless variant (define-module) that would work only in module-files, or even no declaration at all, just calling (use-modules (a b c)), then if a/b/c.scm is found, would make the contents of c.scm into a module (a b c). I dunno.


[-- Attachment #2: Type: text/html, Size: 1861 bytes --]

      reply	other threads:[~2019-04-22 22:33 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-18 22:56 bug#35315: [guile 2.9.1] Loading a module from subfolder fails Jan
2019-04-22 21:45 ` bug#35315: It's not a bug, sorry Jan
2019-04-22 22:33   ` lloda [this message]

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=DD272180-CCF1-47D6-91DC-7B6122044EBE@sarc.name \
    --to=lloda@sarc.name \
    --cc=35315@debbugs.gnu.org \
    --cc=tona_kosmicznego_smiecia@interia.pl \
    /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).