Implications of template declaration & definition

From what I understand template classes and template functions (for the most part) must be declared and defined in the same header file. With that said:

1. Are there any other ways to achieve separate compilation of template files other than using particular compilers? If yes, what are those?

2. What, if any, are the drawbacks of having the declaration and definition in the same file?

3. 开发者_StackOverflow社区What is considered best-practice when it comes to template declaration & definition?

How To Organize Template Source Code

Basically, you have the following options:

• Make the template definition visible to compiler in the point of instantiation.
• Instantiate the types you need explicitly in a separate compile unit, so that linker can find it.
• Use keyword export (if available)

One of the drawbacks encountered by implementing templates in the .h files is that any time you make a small change to the implementation, all the code that uses the template must be recompiled. There's really no way around this aside from not using templates, or declaring & defining them in the CPP file where you use them.

You can implement templates in a seperate file, and then include that file from the .h file. Such as:

templ.h

template<class V> V foo(const V& rhs);
#include "templ.inc"

templ.inc

template<class V> V foo*const V& rhs)
{
// do something...
return val;
}

My personal preference is to implement templates right in the h file unless they become large, and then I'll break it up in to h and inc files.

1. Not really. The definition of the template must be available at compile time, since templates are instantiated depending on the template arguments you give them. This is why they must be placed in headers, so the compiler can have the code to write a new instantiation. You pretty much need a compiler with support for the export keyword.

2. People can see your code, if that's a drawback to you. It might also be less "neat" to some people, but I don't think that's an issue.

A further problem is the compile times every time you change the .h (especially if it is included in a lot of places)

1. Not really. There is the export keyword, but most compilers don't support this. The only mainstream one that I know of that does support this is the Comeau compiler.
2. If your template is part of a public API then you're exposing your code to the world. (most people don't consider this a problem, but some do. It depends on your business).
3. Put them both in the same header file.