Let's say I've prepared D libary. How to automaticly create *.d files (that will be only interfaces). If this can't be done automagicaly how to check if no mismatch appears between *.d used be project and *.d files destinated to be copied.

Second question. What should be default path to copy modules? /usr/include/dlang maybe?

BTW. For those linux users interested in D that are looking for good linux distro. ArchLinux - I'm making easy to use packages for this distro supporting D Lang. Currently DMD and DUI are ready. The reason I asked above questions is that I need to ensure I'll be doing my job as best as possible.

On Tue, 10 Aug 2004 15:20:37 +0200, Dawid wrote:

> Let's say I've prepared D libary. How to automaticly create *.d files (that will be only interfaces). If this can't be done automagicaly how to check if no mismatch appears between *.d used be project and *.d files destinated to be copied.
> 
> Second question. What should be default path to copy modules? /usr/include/dlang maybe?

Why not just put them in /usr/include?
I don't see a reason to separate them just because it's a different
language... C and C++ are there together.  It's not like the .d files and
.h files will conflict.

> 
> BTW. For those linux users interested in D that are looking for good linux distro. ArchLinux - I'm making easy to use packages for this distro supporting D Lang. Currently DMD and DUI are ready. The reason I asked above questions is that I need to ensure I'll be doing my job as best as possible.

teqDruid wrote:
>> Second question. What should be default path to copy modules? /usr/include/dlang maybe?
> 
> Why not just put them in /usr/include?
> I don't see a reason to separate them just because it's a different
> language... C and C++ are there together.  It's not like the .d files and

Right.
-- 
Dawid Ciężarkiewicz | arael
jid: arael@fov.pl