I've been talking with friends and some completely agree that templates in C++ should be used, others disagree entirely.
Some of the good things are:
- They are more safe to use (type safety).
- They are a good way of doing generalizations for APIs.
What other good things can you tell me about C++ templates?
What bad things can you tell me about C++ templates?
Edit: One of the reasons I'm asking this is that I am studying for an exam and at the moment I am covering the topic of C++ templates. So I am trying to understand a bit more on them.
What are the disadvantages of templates?
A disadvantage: template errors are only detected by the compiler when the template is instantiated. Sometimes, errors in the methods of templates are only detected when the member method is instantiated, regardless if the rest of the template is instantiated.
What are disadvantages of using templates in C++?
There are three primary drawbacks to the use of templates. First, many compilers historically have very poor support for templates, so the use of templates can make code somewhat less portable. Second, almost all compilers produce confusing, unhelpful error messages when errors are detected in template code.
Templates are a very powerful mechanism which can simplify many things. However to use them properly requires much time and experience - in order to decide when their usage is appropriate.
For me the most important advantages are:
- reducing the repetition of code (generic containers, algorithms)
- reducing the repetition of code advanced (MPL and Fusion)
- static polymorphism (=performance) and other compile time calculations
- policy based design (flexibility, reusability, easier changes, etc)
- increasing safety at no cost (i.e. dimension analysis via Boost Units, static assertions, concept checks)
- functional programming (Phoenix), lazy evaluation, expression templates (we can create Domain-specific embedded languages in C++, we have great Proto library, we have Blitz++)
- other less spectacular tools and tricks used in everyday life:
- STL and the algorithms (what's the difference between
for and for_each) - bind, lambda (or Phoenix) ( write clearer code, simplify things)
- Boost Function (makes writing callbacks easier)
- tuples (how to genericly hash a tuple? Use Fusion for example...)
- TBB (
parallel_for and other STL like algorithms and containers)
- Can you imagine C++ without templates? Yes I can, in the early times you couldn't use them because of compiler limitations.
- Would you write in C++ without templates? No, as I would lose many of the advantages mentioned above.
Downsides:
- Compilation time (for example throw in Sprit, Phoenix, MPL and some Fusion and you can go for a coffee)
- People who can use and understand templates are not that common (and these people are useful)
- People who think that they can use and understand templates are quite common (and these people are dangerous, as they can make a hell out of your code. However most of them after some education/mentoring will join the group mentioned in the previous point)
- template
export support (lack of) - error messages could be less cryptic (after some learning you can find what you need, but still...)
I highly recommend the following books:
- C++ Templates: The Complete Guide by David Vandevoorde and Nicolai Josuttis (thorough introduction to the subject of templates)
- Modern C++ Design. Generic Programming and Design Patterns Applied by Andrei Alexandrescu (what is the less known way of using templates to simplify your code, make development easier and result in code robust to changes)
- C++ Template Metaprogramming by David Abrahms and Aleksey Gutov (again - different way of using the templates)
- More C++ Idioms from Wikibooks presents some nice ideas.
Menu
825
