Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

Why can templates only be implemented in the header file?

Quote from The C++ standard library: a tutorial and handbook:

The only portable way of using templates at the moment is to implement them in header files by using inline functions.

Why is this?

(Clarification: header files are not the only portable solution. But they are the most convenient portable solution.)

like image 876
MainID Avatar asked Jan 30 '09 10:01

MainID


People also ask

Why are templates implemented in the header file?

To have all the information available, current compilers tend to require that a template must be fully defined whenever it is used. That includes all of its member functions and all template functions called from those. Consequently, template writers tend to place template definition in header files.

How are C++ templates implemented?

A class template is instantiated by passing a given set of types to it as template arguments. The C++ Standard Library contains many class templates, in particular the containers adapted from the Standard Template Library, such as vector .

What is template why we need template in C++?

Templates in c++ is defined as a blueprint or formula for creating a generic class or a function. To simply put, you can create a single function or single class to work with different data types using templates. C++ template is also known as generic functions or classes which is a very powerful feature in C++.

Why don't we use header files in Java?

You don't need header files because the Java compiler compiles class definitions into a binary form that retains all the type information through to link time. By removing all this baggage, Java becomes remarkably context-free.


1 Answers

Caveat: It is not necessary to put the implementation in the header file, see the alternative solution at the end of this answer.

Anyway, the reason your code is failing is that, when instantiating a template, the compiler creates a new class with the given template argument. For example:

template<typename T> struct Foo {     T bar;     void doSomething(T param) {/* do stuff using T */} };  // somewhere in a .cpp Foo<int> f;  

When reading this line, the compiler will create a new class (let's call it FooInt), which is equivalent to the following:

struct FooInt {     int bar;     void doSomething(int param) {/* do stuff using int */} } 

Consequently, the compiler needs to have access to the implementation of the methods, to instantiate them with the template argument (in this case int). If these implementations were not in the header, they wouldn't be accessible, and therefore the compiler wouldn't be able to instantiate the template.

A common solution to this is to write the template declaration in a header file, then implement the class in an implementation file (for example .tpp), and include this implementation file at the end of the header.

Foo.h

template <typename T> struct Foo {     void doSomething(T param); };  #include "Foo.tpp" 

Foo.tpp

template <typename T> void Foo<T>::doSomething(T param) {     //implementation } 

This way, implementation is still separated from declaration, but is accessible to the compiler.

Alternative solution

Another solution is to keep the implementation separated, and explicitly instantiate all the template instances you'll need:

Foo.h

// no implementation template <typename T> struct Foo { ... }; 

Foo.cpp

// implementation of Foo's methods  // explicit instantiations template class Foo<int>; template class Foo<float>; // You will only be able to use Foo with int or float 

If my explanation isn't clear enough, you can have a look at the C++ Super-FAQ on this subject.

like image 97
Luc Touraille Avatar answered Oct 22 '22 17:10

Luc Touraille