Compilation strategy

[Paulo Pinto]

Am 16.12.2012 16:50, schrieb H. S. Teoh:
> On Sun, Dec 16, 2012 at 02:22:04PM +0100, Paulo Pinto wrote:
>> Am 16.12.2012 13:13, schrieb Blub:
>>>> On Sat, 2012-12-15 at 16:55 +0000, Russel Winder wrote:
>>>>> A quick straw poll.  Do people prefer to have all sources compiled
>>>>> in a single compiler call, or (more like C++) separate compilation
>>>>> of each object followed by a link call.
>>>
>>> Separate compilation imposes continuous re-processing of files.
>>
>> Since when?
>>
>> The main idea about modules is exactly to only process files when
>> they are compiled, once.
>>
>> Don't mix modules with C and C++ translation units.
> [...]
>
> Importing the same file from many different places requires the compiler
> to reparse it each time, if those places are compiled during separate
> compiler runs.
>
>
> T
>

If modules are used correctly, a .di should be created with the public 
interface and everything else is already in binary format, thus the 
compiler is not really parsing everything all the time.

Actually, having a strong background in languages with modules, I don't
like having just .d files being given all the time to the compiler, as I
know there are better ways.

--
Paulo