I am using a library that consists almost entirely of templated classes and functions in header files, like this:
// foo.h template<class T> class Foo { Foo(){} void computeXYZ() { /* heavy code */ } }; template<class T> void processFoo(const Foo<T>& foo) { /* more heavy code */ } Now this is bad because compile times are unbearable whenever I include one of those header files (and actually I include many of them in each of my compilation units).
Since as a template parameter I only use one or two types anyway I am planning to create, for each library header file, a file that contains only declarations, without the heavy code, like this:
// NEW: fwd-foo.h template<class T> class Foo { Foo(); void computeXYZ(); }; template<class T> void processFoo(const Foo<T>& foo); And then one file that creates all the instantiations that I’ll need. That file can be compiled separately once and for all:
// NEW: foo.cpp #include 'foo.h' template class Foo<int>; template class Foo<double>; template void processFoo(const Foo<int>& foo); template void processFoo(const Foo<double>& foo); Now I can just include fwd-foo.h in my code and have short compile times. I’ll link against foo.o at the end.
The downside, of course, is that I have to create these new fwd-foo.h and foo.cpp files myself. And of course it’s a maintenance problem: When a new library version is released I have to adapt them to that new version. Are there any other downsides?
And my main question is:
Is there any chance I can create these new files, especially fwd-foo.h, automatically from the original foo.h? I have to do this for many library header files (maybe 20 or so), and an automatic solution would be best especially in case a new library version is released and I have to do this again with the new version. Are any tools available for this task?
EDIT:
Additional question: How can the newly supported extern keyword help me in this case?
We use lzz which splits out a single file into a separate header and translation unit. By default, it would normally put the template definitions into the header too, however, you can specify that you don’t want this to happen.
To show you how you might use it consider the following:
Take the above file and copy it to ‘t.lzz’ file. Place any #include directives into separate $hdr and $src blocks as necessary:
Now finally, run lzz over the file specifying that it places the template definitions into the source file. You can either do this using a $pragma in the source file, or you can use the command line option ‘-ts’:
This will result in the following files being generated:
And:
You can then run these through some grep/sed commands to remove the LZZ helper macros.