Thread: Need hints on templates

Hi,

I usually separate template class definitions in 3 files, a .h for declaration, a .cpp for method definition and a .hpp for "template-dependent" method definitions. Standard procedure.

I understand its best to keep the .hpp file to a minimum (to avoid code bloating, long preprocess times, etc.). Bu I'm lazy so I usually just put everything in the .cpp file to start with, and then move the definitions to the .hpp every time there's a compilation error.

My question is this:
How am I going to know in advance what I have to put in the .hpp file?
I understand what a compilation unit is, and I understand why some definitions are needed at compile-time, but I can't seem to apply theory to actual cases.
Could someone break it down the simple way for me?

Secondary question:
What's an official terminology for those methods that need to be defined in the .hpp file. I don't like that "template-dependent" I used earlier

Originally Posted by laserlight

Your procedure sounds a little strange to me. If you are going to fix the compile errors by moving the class template's function definitions from the source file to an auxiliary header, then you might as well do without the source file and just put all the function definitions in the auxiliary header.

Sure, that works too.
I'm familiar with the method presented by Marshall Kline, too.
I'm just trying to understand what needs to go in the auxiliary header and what can be in the source file, if I want to do things that way.
Call it curiosity, I just want to understand C++ better instead of just "making it work".

Originally Posted by krappa

Sure, that works too.
I'm familiar with the method presented by Marshall Kline, too.
I'm just trying to understand what needs to go in the auxiliary header and what can be in the source file, if I want to do things that way.
Call it curiosity, I just want to understand C++ better instead of just "making it work".

If it's got a template in it, it needs to go in the auxiliary header. Template code is not generated unless it is instantiated (until that far-off day when "export" works, or we all start using Comeau), so any source that's just a bunch of template classes/functions/etc that doesn't actually use those classes/functions/etc won't actually generate any code.