Creation of a Build tool on top of the D compiler

[kris]

BCS wrote:
> Reply to kris,
> 
>> BCS wrote:
>>
>>> what If I have a 200+ module project that take ten minutes to compile
>>> (lots of templates say) a build only what's needed strategy is still
>>> needed. having bud walk the whole tree and still only build what is
>>> needed is still useful. I don't think /that/ functionality should go
>>> into the compiler.
>>>
>> Yes, I agree. The compiler should still handle the basic requirement
>> though. After all, currently loads /and/ parses every single one of
>> those 200+ modules regardless (if they're imported in any fashion)
>>
> 
> If all imports are private then compiling module N only requiters 
> parsing only the modules that N imports. Also lex/parse/syntax isn't all 
> that compiling requiers.
> 
> 

I think perhaps we're talking at cross-purposes? <g>