Hi all,
I've came across the following problem number of times.
Let's say I have project A and B, sharing code but having a
different tree structure.
$ find projectA
./projectA/internal/math/algo.d
./projectA/internal/math/lcp.d
./projectA/internal/math/optimize.d
./projectA/gui/main.d
$ find projectB
./projectB/app/render/gfx.d
./projectB/app/render/algo.d
./projectB/app/physics/math/algo.d
./projectB/app/physics/math/lcp.d
./projectB/app/physics/math/optimize.d
./projectB/main.d
The directory "math" is shared between projects. It actually is
an external/submodule. So it has a standalone existence as a
library, and might one day be used by projectC.
(In the context of this issue, I'm using separate compilation).
I'd like to be able to write, in projectA's main:
import internal.math.optimize;
This requires me to add, at the beginning of "optimize.d" file,
this module definition:
module internal.math.optimize;
However, this "optimize.d" file is shared between projects, now
it's becoming specific to projectA.
How am I supposed to share code between projects then?
Clearly, putting everyone back into the same "file namespace" by
adding every subdirectory of my project as import paths through
the command line is not going to scale.
After many projects spent thinking of this issue, I came to the
conclusion that being able to specify, on the command line, the
module name of the module currently being compiled, thus allowing
to override it to be inferred to the basename of the file, would
solve this problem.
As a side-problem related to this one, having to repeat the
"absolute" module path to all module declarations/importations is
tedious. What if I change the name of the package? Now I might
have to change hundreds of module declarations from "module
oldname.algo;" to "module newname.algo;".
Clearly, something must be wrong here (and I hope it's me!)
I'd be very happy if someone showed me how solve this problem,
this has bothered me for ages.
