[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Rationale behind the module paths in definition of the module
From: |
Alpha Omega |
Subject: |
Rationale behind the module paths in definition of the module |
Date: |
Thu, 08 Jan 2015 09:33:43 +0000 |
User-agent: |
Roundcube Webmail/1.0.4 |
-----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],
would be enough. This way, I could differentiate between the modules
residing under different paths, but
having the same name.
However, hard-wiring a path , e.g, `(define-module (hard-wired path to
module))' prevents me from easily moving the
module code around (for example, during `make install').
-----BEGIN PGP SIGNATURE-----
Version: OpenPGP.js v0.5.1
Comment: http://openpgpjs.org
wsBcBAEBCAAQBQJUrk67CRC6Cm7u/wM3RwAAZo4H/0/A05fbuGV/vIAaLMNr
TzuOplLMFQ9eRJZqqwgizcwU/NB/V4IKNwN12Ge+WrgGDFRUkT3x4lqv5xW9
iUlVeC2Y/OWXvs8fzhDUGju7PY8kRYA+f8WkxpOApkJXE9GNfZkhNBeTcRrN
xdUZH32ufbfoknbQxEELgaAJaXmSiaaIcQY+J6wOdwlGAdg4tvuWfuGrJhLi
0YZlNeYv9Rg2m8izQ0llnVH34fVBORp+yfR3kpCPqaOOdUbSnJdlS0sx1XU/
uXtUidwDJvmoVD6ZVusLUjqgsoHKHGqCGtCohK2M3OA8Z8cKLdfUdpn1xGKs
uRFQFjpq2PrmhVCnR2O0LRU=
=JPXp
-----END PGP SIGNATURE-----
- Rationale behind the module paths in definition of the module,
Alpha Omega <=