dmd -c behaviour doesn't take account of packages.

[Jacob Carlborg]

On 2012-02-24 00:06, Bernard Helyer wrote:
> On Thursday, 23 February 2012 at 21:28:17 UTC, H. S. Teoh wrote:
>> On Thu, Feb 23, 2012 at 01:42:44PM +0100, Jacob Carlborg wrote:
>>> On 2012-02-23 00:03, Jonathan M Davis wrote:
>>> >On Wednesday, February 22, 2012 23:50:53 Bernard Helyer wrote:
>>> >>Except DMD is faster by a factor of 10 when passing it all >>at once.
>>> >
>>> >Then maybe there _should_ be a flag to tell it to >use/generate the
>>> >appropriate directory structure. You already typically give >it an
>>> >output directory. It wouldn't be all that hard for it to then
>>> >generate and use the correct directories in that directory. >That
>>> >still bugs me a little, because that's more of a build tool's >job,
>>> >but it wouldn't be hard to do, would fix the file conflicts >across
>>> >modules, and would let you keep that extra speed.
>>> >
>>> >- Jonathan M Davis
>>>
>>> I don't see a point in putting the object files in different
>>> directories when the compiler can output the object files with fully
>>> qualified module names.
>> [...]
>>
>> Because ambiguity can arise. Like
>>
>> my/module/A.d -> my_module_A.o
>> my_module_A.d -> my_module_A.o (conflict)
>> my_module/A.d -> my_module_A.o (conflict)
>> my/module_A.d -> my_module_A.o (conflict)
>>
>> Granted, this is a really contrived example, but unexpected coincidences
>> like that do happen.
>>
>>
>> T
>
> Did you not read what Jacob posted?
>
> my.module.A.o
> my_module_A.o
> my_module.A.o
> my.module_A.o
>
> No conflicts.
>
>

Exactly.

-- 
/Jacob Carlborg