Click here to Skip to main content
11,927,600 members (59,157 online)
Click here to Skip to main content
Add your own
alternative version

Tagged as


29 bookmarked

Templates in C++ - Pros and Cons

, 3 Dec 2011 CPOL
Rate this:
Please Sign up or sign in to vote.
Advantages and drawbacks of using templates in C++ projects

Introduction to C++ Templates - Pros and Cons

Once upon a time, I decided to collect and organize all the advantages and drawbacks you may experience when using templates in C++.


C++ templates enable you to define a family of functions or classes that can operate on different types of information.

  • Use templates in situations that result in duplication of the same code for multiple types.
    For example, you can use function templates to create a set of functions that apply the same algorithm to different data types.
  • You can also use class templates to develop a set of typesafe classes.
  • Templates are sometimes a better solution than C macros and void pointers,
    and they are especially useful when working with collections (one of the main uses for templates in MFC) and smart pointers (from MSDN).
  • A. Stepanov (the creator of STL) notes that some things that seem trivial using templates (such as equality operator, for example) are very difficult to implement with conventional OO techniques such as inheritance and polymorphism.
  • Because their parameters are known at compile time, template classes are more typesafe, and could be preferred over run-time resolved code structures (such as abstract classes). There are some modern techniques that can dramatically reduce code bloat when using templates. Note that these techniques are very complex either.
  • Often, the main reason to use templates in combination with STL – it can drastically reduce development time.


  • Historically, some compilers exhibited poor support for templates. So, the use of templates could decrease code portability.
  • Many compilers lack clear instructions when they detect a template definition error. This can increase the effort of developing templates, and has prompted the development of Concepts for possible inclusion in a future C++ standard.
  • Since the compiler generates additional code for each template type, indiscriminate use of templates can lead to code bloat, resulting in larger executables. For example, used in Adobe products "… GIL (Generic Image Library) implements type generators.
    One of these generators generates all image types that are combinations of given sets of color spaces and channels.
    This code defines any image t to be one of 4×3×2×2 = 48 possible image types. It can have any of the four listed color spaces, any of the three listed channel depths, it can be interleaved or planar and its pixels can be adjacent or non-adjacent in memory.
    The above code generates 48 × 48 = 2304 instantiations. Without any special handling, the code bloat will be out of control."
    See Efficient Run-Time Dispatching in Generic Programming with Minimal Code Bloat, 2004.
  • Because a template by its nature exposes its implementation, injudicious use in large systems can lead to longer build times.
  • It can be difficult to debug code that is developed using templates. Since the compiler replaces the templates, it becomes difficult for the debugger to locate the code at runtime.
  • Templates are in the headers, which require a complete rebuild of all project pieces when changes are made.
  • No information hiding. All code is exposed in the header file. No one library can solely contain the code (from Wikipedia).
  • Though STL itself is a collection of template classes, templates are not used to write conventional libraries.
    The libraries of templates are header-only: the library code is included in and compiled with the user's code.
    Though, this makes installation and usage of the libraries relatively easy.

In The C++ Programming Language (3rd Edition), B.Stroustrup presents over 20 factors to take into account when programming templates.
Many of them have to do with ensuring that your code is reliable for all input classes, and maintainable.
B. Stroustrup recognizes these pitfalls:

  • The ease with which unmaintainable "spaghetti code" can be generated
  • Automatically generated source code can become overwhelmingly huge
  • Compile-time processing of templates can be extremely time consuming
  • Debugging is not intuitive for most programmers
  • Context dependencies can be difficult to diagnose and even harder to correct (from comments here)

And here is B. Stroustrup's more recent view on templates usage:

  • Prefer a template over derived classes when run-time efficiency is at a premium
  • Prefer derived classes over a template if adding new variants without recompilation is important
  • Prefer a template over derived classes when no common base can be defined
  • Prefer a template over derived classes when built-in types and structures with compatibility constraints are important

See Joint strike fighter air vehicle C++ coding standards, December 2005.

In sharp contrast to the claim that templates cause code bloat, it so happens that templates can be used to save code space.
C++ compiler is not allowed to generate code for an unused template function. This implies that if a program uses only 3 of a template class’ 7 member functions, only those three functions will occupy space in memory. The equivalent optimization for non-template classes is not common (the standard doesn’t require it) and extremely hard to achieve for virtual functions.

See Abstraction and the C++ machine model, B. Stroustrup, 2004.



  • 29.10.2011 - Initial submission of article
  • 03.12.2011 - Article updated


This article, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)


About the Author

Sergey Chepurin
Russian Federation Russian Federation
No Biography provided

You may also be interested in...

Comments and Discussions

QuestionTemplates are of the devil Pin
bearvarine5-May-15 11:51
memberbearvarine5-May-15 11:51 
AnswerRe: Templates are of the devil Pin
Sergey Chepurin10-Jun-15 10:29
memberSergey Chepurin10-Jun-15 10:29 
GeneralMy vote of 5 - Very important article Pin
Michael N. Haephrati13-Jul-14 7:59
professionalMichael N. Haephrati13-Jul-14 7:59 
QuestionNice Pin
Manikandan106-Jun-14 21:38
professionalManikandan106-Jun-14 21:38 
QuestionMessage Automatically Removed Pin
3-Sep-13 2:11
memberMember 102203673-Sep-13 2:11 
SuggestionMessage Automatically Removed Pin
3-Sep-13 2:07
memberMember 102203673-Sep-13 2:07 
QuestionNo information hiding. Pin
Shakti Misra16-Nov-11 0:15
memberShakti Misra16-Nov-11 0:15 
AnswerRe: No information hiding. Pin
steveb17-Aug-13 5:12
membersteveb17-Aug-13 5:12 
AnswerMessage Automatically Removed Pin
3-Sep-13 2:12
memberMember 102203673-Sep-13 2:12 
QuestionTemplates Pin
geoyar3-Nov-11 15:38
membergeoyar3-Nov-11 15:38 
AnswerRe: Templates Pin
Sergey Chepurin3-Nov-11 21:48
memberSergey Chepurin3-Nov-11 21:48 
GeneralRe: Templates Pin
geoyar4-Nov-11 16:11
membergeoyar4-Nov-11 16:11 
GeneralRe: Templates Pin
Sergey Chepurin4-Nov-11 21:58
memberSergey Chepurin4-Nov-11 21:58 
QuestionLong compilation times Pin
Lorenzo Gatti2-Nov-11 7:45
memberLorenzo Gatti2-Nov-11 7:45 
AnswerRe: Long compilation times Pin
Sergey Chepurin2-Nov-11 23:33
memberSergey Chepurin2-Nov-11 23:33 
QuestionA couple of comments... Pin
_J0N0_29-Oct-11 18:51
member_J0N0_29-Oct-11 18:51 
AnswerRe: A couple of comments... Pin
Sergey Chepurin30-Oct-11 0:41
memberSergey Chepurin30-Oct-11 0:41 

General General    News News    Suggestion Suggestion    Question Question    Bug Bug    Answer Answer    Joke Joke    Praise Praise    Rant Rant    Admin Admin   

Use Ctrl+Left/Right to switch messages, Ctrl+Up/Down to switch threads, Ctrl+Shift+Left/Right to switch pages.

| Advertise | Privacy | Terms of Use | Mobile
Web01 | 2.8.151126.1 | Last Updated 3 Dec 2011
Article Copyright 2011 by Sergey Chepurin
Everything else Copyright © CodeProject, 1999-2015
Layout: fixed | fluid