Library standardization

[Bill Baxter]

e-t172 wrote:
> Bill Baxter a écrit :
>> e-t172 wrote:
>>> Koroskin Denis a écrit :
>>>> Current situation is, someone writes code, probably nice one, and it 
>>>> is added
>>>> to main trunk. Problem is, interface is implementation driven, not 
>>>> otherwise.
>>>> It is not discussed. And thats bad. Tests first, then code, Kent 
>>>> Beck said.
>>>> Of course, implementation can affect interface, but only after trial.
>>>
>>> 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 his implementation. I see for advantages:
>>
>> I think the automatic .di generation is a better.  I just wish it 
>> generated human-readable output rather than stripping all indentation.
> 
> Automatic .di generation would be just great if it actually stripped 
> implementation (see my P.S.).

See Janice's comments.  .di files contain the implementation of 
templates and of functions that will be inlined.  These things must be 
in the header file to work.  They do not contain all implementation as 
you suggest.  Or at least they're not supposed to.

--bb