It can give an estimate of “how many lines of code” end up being parsed by the compiler, when all the header files have been included. I suggest you read the original post about it. A more recent post from Niklas at how they are approaching the header file problem now is very interesting too; though I’m not convinced it scales beyond “a handful of people” team sizes.
Anyway. I just made some small improvements to Header Hero while using it on our codebase:
I added a new field at the bottom of the main UI where a “precompiled header” file can be indicated. Everything included into that header file will be not counted into “lines of code parsed” lists that the UI shows in the report.
What goes into the precompiled header itself is shown at the bottom of the report window:
Small UI tweaks
Added quick links to “list of largest files” and “list of most included files” (hubs) at top of build report. Initially I did not even know the UI had the “hubs” list, since it was so far away on the scrollbar :)
Switched the “Includes” tab to have file lists with columns (listing include count / line count), and added a “go to previous file” button for navigation.
That’s it! Get them on bitbucket here.