Hi Mafi, Thanks very much for the prompt reply. Thanks for the various links. BTW, are you an employee within digitalmars?
>class C {} >interface I { void print(); } >abstract class D: C,I {} >void main() {} I need class D to be solid class doing both inherits from C but allow me to provide code and for interface I. BTW, does it matter if the compilation process goes this way? The order of the code appearing in different file. >abstract class D: C,I {} >class C {} >interface I { void print(); } I am aware about dmd -Ipath option. And yes, import works like include which means (yucks!) I believe it would use the behavior of import in java. I like to maintain different class/interface/function into different file, the dmd process seem to be too particular to compile the file in a specific order unlike javac all I need to make sure those other class/interfaces i needed are within the directory or -classpath options. That is also why I posted the import question in item 5. Google Go seems to not care about this, if I am not wrong. I believe the compiler and linker should be smart to resolved this using some internal mapping. Any new programming language should frees the developer to focus more on their business logic than to maintain library and dependency. Btw, any benchmark done officially comparing google go/java/D? I do run cygwin and D on a windows vista platform. Matthew on...@yahoo.com