Hi guys,
I'm still a tad annoyed by our compile times, and was wondering - has a
footypes.hxx header approach been tried in the past. This would add a
near complete set of forward declarations of classes, templates, etc.
necessary to use that library.
I suspect (at the moment)
Some compilers can pull header-parse-caching tricks, but in order for that to
work nicely
- all compilation modules need to import other files in the same order
- the list of macro definitions and other parameters passed into the compiler
must be the same for all the compilation
modules
Hi Noel,
On Tue, 2011-09-27 at 11:03 +0200, Noel Grandin wrote:
Some compilers can pull header-parse-caching tricks, but in order for
that to work nicely
Sure - we have lots of (IIRC unused) precompiled_ header stuff - that
of course tends to work in the opposite direction: include as
On 09/27/2011 01:24 PM, Noel Grandin wrote:
(1) Nice pragma trick for making this problem show up at compile time:
http://stackoverflow.com/questions/74326/how-should-i-detect-unnecessary-include-files-in-a-large-c-project/109890#109890
This would flag double includes that are there for good
On 09/27/2011 10:55 AM, Michael Meeks wrote:
I'm still a tad annoyed by our compile times, and was wondering - has a
footypes.hxx header approach been tried in the past. This would add a
near complete set of forward declarations of classes, templates, etc.
necessary to use that library.
