Re: Rationale behind the module paths in definition of the module

2015-01-10 Thread Alpha Omega
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 08/01/15 14:46, Taylan Ulrich Bayırlı/Kammer wrote: > Amirouche Boubekki writes: > >> I find this surprising too. IMO, it's not useful to declare the >> file a module at all. > > You can have single-name-component modules '(foo)' in > correspon

Re: Rationale behind the module paths in definition of the module

2015-01-08 Thread Alpha Omega
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 2015-01-08 10:17, l...@gnu.org wrote: When a program contains: (use-modules (foo bar)) Guile searches for a file named foo/bar.scm (or foo/bar) in its search path. The search path is defined by the user, using the GUILE_LOAD_PATH environ

Rationale behind the module paths in definition of the module

2015-01-08 Thread Alpha Omega
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi, I am wondering, what is the advantage of having both the definition of the module and the invocation depending on the module path? One would think that the path in invocation [i mean `(use-modules (a path to module))' macro invocation], w