6

Say I declare a template class A in a.h

#include <iostream>

template<bool b>
class A { 
public:
  void print(std::ostream& out);
};

And define the print method in a.cpp (with explicit instatiation for true and false) 

#include "a.h"

template<bool b>
void A<b>::print(std::ostream& out) {
  out << "A" << b;
}

template class A<true>;
template class A<false>;

An example main main program in main.cpp could be

#include "a.h"

int main() {
  A<true> a;
  a.print(std::cout);
}

The small project above compiles just fine.

Question: If I put the explicit instantiations above the definition of the print method (in a.cpp), the code doesn't compile anymore, with the usual undefined reference to A<true>::print(...) error.

#include "a.h"

template class A<true>;
template class A<false>;

template<bool b>
void A<b>::print(std::ostream& out) {
  out << "A" << b;
}

Why is this the case?

Edit: Makefile to compile

main : main.o a.o
    g++ main.o a.o -o main

main.o : main.cpp
    g++ -c main.cpp

a.o : a.cpp 
    g++ -c a.cpp
Dejan Jovanović
  • 2,085
  • 1
  • 16
  • 22
  • 1
    works on VS2012 as well. – billz Jan 04 '13 at 06:13
  • I did and I changed the order as Dejan mentioned – billz Jan 04 '13 at 06:34
  • 1
    @jogojapan -- +1. I've deleted my comment that said that it compiles with clang32 and gcc48. It was compiling fine with any compiler and with any order if contents of three files were cut and pasted into one file - like I did initially for my test. After Dejan posted Makefile, I was able to reproduce error with clang and gcc of any version. – Leonid Volnitsky Jan 04 '13 at 07:04
  • @LeonidVolnitsky Ok, cool! So I guess then it's only VS that doesn't implement this in the correct way? – jogojapan Jan 04 '13 at 07:13

2 Answers2

9

I don't think there is a good natural explanation for why this is so. Clearly, the compiler could see the definition of the member function even if it is provided after the explicit instantiation – because it is located in the same file.

However, compilers are not required to this; it is in fact explicitly forbidden by the Standard:

(§14.7.2/9) An explicit instantiation definition that names a class template specialization explicitly instantiates the class template specialization and is an explicit instantiation definition of only those members that have been defined at the point of instantiation.

I guess the reasons for this include the following:

  • There could be several distinct explicit specializations for some of the member functions later in the translation unit; it makes sense, also in the programmer's interest, to have an explicit rule about which of these will be instantiated;

  • When a template is implicitly instantiated, only specializations defined before the point of instantiation are taken into account; so the rule is the same for implicit and explicit instantiations.

jogojapan
  • 68,383
  • 11
  • 101
  • 131
1
template class A<true>;
template class A<false>;

The same reason why it is typically expected that template code is defined in the header itself. To perform explicit instantiation, you (the compiler) need to be able to see the entire definition of the template class, which isn't possible from your main.cpp.

However a.cpp has access to all of the definition of the class (here the print method) so explicit instantiation works there.

Karthik T
  • 31,456
  • 5
  • 68
  • 87