On Fri, Feb 27, 2009 at 5:07 PM, Walter Bright <[email protected]> wrote: > Eldar Insafutdinov wrote: >> >> in our case resources we are initializing are unrelated to the >> modules we are importing. and semantically the code is placed in >> modules as it should be. > > True, often there isn't an actual dependency on the order, but the compiler > can't tell that.
I was going to say "can't it?" but then remembered separate compilation. Sigh. I think the separate compilation paradigm, at least as designed for C and C++, has to go the way of the dodo for lots of cool things to be made possible. The thread on .D about not being able to non-virtualize methods in the face of separate compilation is another example.
