Namespace for a module defined by its import path

[Jeff Thompson via Digitalmars-d]

On Wednesday, 26 October 2016 at 01:15:02 UTC, Mike Parker wrote:
> On Tuesday, 25 October 2016 at 22:25:51 UTC, Jeff Thompson 
> wrote:
>> On Tuesday, 25 October 2016 at 19:54:42 UTC, Jonathan Marler 
>> wrote:
>>> On Tuesday, 25 October 2016 at 06:47:14 UTC, Jeff Thompson 
>>> wrote:
>>>> [...]
>>>
>>> Sorry if I didn't understand something, couldn't you do this?
>>>
>>> /commit_b3bf5c7725c98ee3e49dfc4e47318162f138fe94/version/lib.d
>>> /commit_df0741a84c8a967ea08674090afdff4e9a58d23e/version/lib.d
>>
>> If I do that, can lib.d avoid the following module statement?
>> module 
>> commit_b3bf5c7725c98ee3e49dfc4e47318162f138fe94.version.lib
>
> dmd -I/commit_b3bf5c7725c98ee3e49dfc4e47318162f138fe94/version/ 
> main.d
> dmd 
> -I//commit_df0741a84c8a967ea08674090afdff4e9a58d23e/version/ 
> main.d

This will force the application to use either one version or the 
other. As I said, it's a large application. I different parts of 
the same application to be able to import the version they need.