Modules/packages correspondence to file system

Lars E. notavailable at notavailable.com
Tue Jul 18 11:52:15 PDT 2006


Why are tools like build (http://dsource.org/projects/build) even 
neccessary?

I think I read somewhere in the official D docs that the name of the 
module equals the name of the source file minus extension (unless 
otherwise specified) and the name of the package equals the name of the 
directory structure the module resides in.

Shouldn't that be enough for the compiler to automatically figure out 
dependencies itself (if you specified extra search paths if neccessary)?

Isn't that how the Java compiler works?

I noticed you can easily abstract packages/modules from the file system. 
That seems a bad idea. I know it allows for more flexibility but with 
that flexibility comes a great deal of complexity.

Simple things should stay simple .. imagine a world without makefiles 
(build provides this, but why not the language itself?)!



More information about the Digitalmars-d mailing list