Library standardization

[Koroskin Denis]

On Sat, 19 Apr 2008 15:48:51 +0400, Janice Caron <caron800 at googlemail.com>  
wrote:

> On 19/04/2008, e-t172 <e-t172 at akegroup.org> wrote:
>>  I have to agree on this one. As a side note, I definitely think we  
>> *need*
>> "real" header files (like .h files in C/C++), which separates the API  
>> and
>
> What if my functions may be inlined?
>
> What if my functions are template functions?
>
> What if my functions are capable of compile-time-function-execution?
>
> What if my functions generate strings for use in string mixins?
>

Then, yes, you should provide source code for these functions, too.
That's the Boost way. Most of the library staff is template-heavy and
stored in *.hpp files. That's their biggest advantage - you don't need
to compile Boost (well, most of it). And that's their biggest disadvantage  
-
it's not human readable.

> Besides which - I don't want to have to maintain two separate files!
> Those days are gone, and good riddance to them.

I used to code in C#, and in those days my best friend was Reflector. You
don't need any source code documentation with it, because it allows you
to easily navigate between classes, shows you all information for any  
class:
public/private methods/properties, implementation (if needed), base class,
interfaces, etc. Great one! A must-have, when developing for dotNET.

We should have similar one for D! Imagine, you point it to Tango root  
folder
a get a complete objects hierarchy! Damn, I should definately look into
starting such project.