Pavel Sanda schreef:
Steve Litt wrote:
The part where you remove .h includes from .cpp is dead bang easy if rather
slow. Not so with the .h includes inside other .h files. For each #include
removal from a .h file, you'd have to compile every .cpp that includes the
including .h.
my draft implied one compilation per one #include in our sources, no
combinations. the only tweaking part was that detection in .h files - one has
to distinguish whether the compilation fails because of header insuficiency in
.h or in consequent .cpp which includes it.
pavel
Yes, but if you include ten .h files, and each one includes ten other
.h files, then it is very difficult to find the least amount of includes
that are needed. And in the end, it might not even have any influence on
building times as one .h file is often included through some detours.
Vincent