Splitting templated C++ classes into .hpp/.cpp files–is it possible?

by

It is not possible to write the implementation of a template class in a separate cpp file and compile. All the ways to do so, if anyone claims, are workarounds to mimic the usage of separate cpp file but practically if you intend to write a template class library and distribute it with header and lib files to hide the implementation, it is simply not possible.

To know why, let us look at the compilation process. The header files are never compiled. They are only preprocessed. The preprocessed code is then clubbed with the cpp file which is actually compiled. Now if the compiler has to generate the appropriate memory layout for the object it needs to know the data type of the template class.

Actually it must be understood that template class is not a class at all but a template for a class the declaration and definition of which is generated by the compiler at compile time after getting the information of the data type from the argument. As long as the memory layout cannot be created, the instructions for the method definition cannot be generated. Remember the first argument of the class method is the ‘this’ operator. All class methods are converted into individual methods with name mangling and the first parameter as the object which it operates on. The ‘this’ argument is which actually tells about size of the object which incase of template class is unavailable for the compiler unless the user instantiates the object with a valid type argument. In this case if you put the method definitions in a separate cpp file and try to compile it the object file itself will not be generated with the class information. The compilation will not fail, it would generate the object file but it won’t generate any code for the template class in the object file. This is the reason why the linker is unable to find the symbols in the object files and the build fails.

Now what is the alternative to hide important implementation details? As we all know the main objective behind separating interface from implementation is hiding implementation details in binary form. This is where you must separate the data structures and algorithms. Your template classes must represent only data structures not the algorithms. This enables you to hide more valuable implementation details in separate non-templatized class libraries, the classes inside which would work on the template classes or just use them to hold data. The template class would actually contain less code to assign, get and set data. Rest of the work would be done by the algorithm classes.

I hope this discussion would be helpful.

More Related Contents:

  1. Is it possible to pass a class as an argument of a function in C++
  2. Why do I get “unresolved external symbol” errors when using templates? [duplicate]
  3. templates: parent class member variables not visible in inherited class
  4. Undefined reference error for template method [duplicate]
  5. C++ class header files organization
  6. c++ template and header files [duplicate]
  7. How does the linker handle identical template instantiations across translation units?
  8. static variables in an inlined function
  9. C++ template, linking error [duplicate]
  10. Class template with template class friend, what’s really going on here?
  11. How to create a template function within a class? (C++)
  12. C++ templates declare in .h, define in .hpp
  13. Template type deduction in C++ for Class vs Function?
  14. Can someone explain this template code that gives me the size of an array? [duplicate]
  15. C++ template constructor
  16. CRTP to avoid dynamic polymorphism
  17. Most vexing parse confusion
  18. gcc: undefined reference to
  19. C++17 class template partial deduction
  20. How can I declare a member vector of the same class?
  21. *.h or *.hpp for your class definitions
  22. C++ preprocessor: avoid code repetition of member variable list
  23. Template class with template container
  24. How to access private data members outside the class without making “friend”s? [duplicate]
  25. Variadic deduction guide not taken by g++, taken by clang++ – who is correct?
  26. C++ overloaded function as template argument
  27. library is linked but reference is undefined
  28. Why the initializer of std::function has to be CopyConstructible?
  29. Default values in templates with template arguments ( C++ )
  30. Obtain container type from (its) iterator type in C++ (STL)

Leave a Comment