On Friday, 4 May 2012 at 21:11:22 UTC, H. S. Teoh wrote:
Exactly. And while we're at it, *really* strip unnecessary
stuff from
.di files, like function bodies, template bodies, etc.. That
stuff is
required by the compiler, not the user, so stick that in the
object
files and let the compiler deal with it. The .di file should be
ONLY
what's needed for the user to understand how to use the library.
T
You contradict yourself.
The purpose of di files *is* to provide the compiler the required
info to use the binary object/library. If you want human readable
docs we already have DDoc (and other 3rd party tools) for that.
If you don't like the default HTML output (I can't fathom why)
you can easily define appropriate macros for other output types
such as TeX (and PDF via external converter), text based, etc..
