模板类中单个方法的模板专门化

总是考虑到下面的头部(包含我的模板类)包含在至少两个 .CPP文件中，这段代码可以正确编译:

template <class T>
class TClass
{
public:
void doSomething(std::vector<T> * v);
};


template <class T>
void TClass<T>::doSomething(std::vector<T> * v) {
// Do something with a vector of a generic T
}


template <>
inline void TClass<int>::doSomething(std::vector<int> * v) {
// Do something with a vector of int's
}

但请注意专门化方法中的内联。它需要避免一个连接器错误(在 VS2008是 LNK2005) ，由于方法被定义多次。我理解这一点是因为 AFAIK 一个完整的模板专门化与一个简单的方法定义是相同的。

那么，我如何移除 inline呢？代码不应该在每次使用时都被复制。我搜索了 Google，在 SO 中阅读了一些问题，并尝试了许多建议的解决方案，但没有一个成功构建(至少在 VS 2008中没有)。

谢谢！

69954 次浏览
小开
最佳答案

As with simple functions you can use declaration and implementation. Put in your header declaration:

template <>
void TClass<int>::doSomething(std::vector<int> * v);

and put implementation into one of your cpp-files:

template <>
void TClass<int>::doSomething(std::vector<int> * v) {
// Do somtehing with a vector of int's
}

Don't forget to remove inline (I forgot and thought this solution will not work :) ). Checked on VC++2005

小开

You need to move specialization definition to CPP file. Specialization of member function of template class is allowed even if function is not declared as template.

小开

There is no reason to remove the keyword inline.
It does not change the meaning of the code in anyway.

小开

If you want to remove the inline for whatever reason the solution of maxim1000 is perfectly valid.

In your comment, though, it seems you believe that the inline keyword means that the function with all his contents gets always inlined but AFAIK that is actually very much dependent on your compiler optimization.

Quoting from the C++ FAQ

There are several ways to designate that a function is inline, some of which involve the inline keyword, others do not. No matter how you designate a function as inline, it is a request that the compiler is allowed to ignore: the compiler might inline-expand some, all, or none of the places where you call a function designated as inline. (Don’t get discouraged if that seems hopelessly vague. The flexibility of the above is actually a huge advantage: it lets the compiler treat large functions differently from small ones, plus it lets the compiler generate code that is easy to debug if you select the right compiler options.)

So, unless you know that that function will actually bloat your executable or unless you want to remove it from the template definition header for other reasons, you can actually leave it where it is without any harm

小开

This is a little OT, but I thought I'd leave this here in case it helps someone else. I was googling about template specialization which led me here, and while @maxim1000's answer is correct and ultimately helped me figure my problems out, I didn't think it was abundantly clear.

My situation is a little different (but similar enough to leave this answer I think) than the OP's. Basically, I'm using a third party library with all different kinds of classes that define "status types". The heart of these types are simply enums, but the classes all inherit from a common (abstract) parent and provide different utility functions, such as operator overloading and a static toString(enum type) function. Each status enum is different from one another and unrelated. For example, one enum has the fields NORMAL, DEGRADED, INOPERABLE, another has AVAILBLE, PENDING, MISSING, etc. My software is in charge of managing different types of statuses for different components. It came about that I wanted to utilize the toString functions for these enum classes, but since they're abstract I couldn't instantiate them directly. I could have extended each class I wanted to use, but ultimately I decided to create a template class, where the typename would be whatever concrete status enum I cared about. Probably some debate can be had about that decision, but I felt like that was a lot less work than extending each abstract enum class with a custom one of my own and implementing the abstract functions. And of course in my code, I just wanted to be able to call static toString(enum type)2 and have it print the string representation of that enum. Since all the enums were entirely unrelated, they each had their own toString functions that (after some research I learned) had to be called using template specialization. That led me here. Below is an MCVE of what I had to do in order to make this work correctly. And actually my solution was a bit different than @maxim1000's.

This is a (greatly simplified) header file for the enums. In reality, each enum class was defined in it's own file. This file represents the header files that are supplied to me as part of the library I am using:

// file enums.h
#include <string>


class Enum1
{
public:
enum EnumerationItem
{
BEARS1,
BEARS2,
BEARS3
};


static std::string toString(EnumerationItem e)
{
// code for converting e to its string representation,
// omitted for brevity
}
};


class Enum2
{
public:
enum EnumerationItem
{
TIGERS1,
TIGERS2,
TIGERS3
};


static std::string toString(EnumerationItem e)
{
// code for converting e to its string representation,
// omitted for brevity
}
};

adding this line just to separate the next file into a different code block:

// file TemplateExample.h
#include <string>


template <typename T>
class TemplateExample
{
public:
TemplateExample(T t);
virtual ~TemplateExample();


// this is the function I was most concerned about. Unlike @maxim1000's
// answer where (s)he declared it outside the class with full template
// parameters, I was able to keep mine declared in the class just like
// this
std::string toString();


private:
T type_;
};


template <typename T>
TemplateExample<T>::TemplateExample(T t)
: type_(t)
{


}


template <typename T>
TemplateExample<T>::~TemplateExample()
{


}

next file

// file TemplateExample.cpp
#include <string>


#include "enums.h"
#include "TemplateExample.h"


// for each enum type, I specify a different toString method, and the
// correct one gets called when I call it on that type.
template <>
std::string TemplateExample<Enum1::EnumerationItem>::toString()
{
return Enum1::toString(type_);
}


template <>
std::string TemplateExample<Enum2::EnumerationItem>::toString()
{
return Enum2::toString(type_);
}

next file

// and finally, main.cpp
#include <iostream>
#include "TemplateExample.h"
#include "enums.h"


int main()
{
TemplateExample<Enum1::EnumerationItem> t1(Enum1::EnumerationItem::BEARS1);
TemplateExample<Enum2::EnumerationItem> t2(Enum2::EnumerationItem::TIGERS3);


std::cout << t1.toString() << std::endl;
std::cout << t2.toString() << std::endl;


return 0;
}

and this outputs:

BEARS1
TIGERS3

No clue if this is the ideal solution to solve my problem, but it worked for me. Now, no matter how many enumeration types I end up using, all I have to do is add a few lines for the toString method in the .cpp file, and I can use the libraries already-defined toString method without implementing it myself and without extending each enum class I want to use.

小开

I'd like to add that there is still a good reason to keep the inline keyword there if you intend to leave also the specialization in the header file.

"Intuitively, when you fully specialize something, it doesn't depend on a template parameter any more -- so unless you make the specialization inline, you need to put it in a .cpp file instead of a .h or you end up violating the one definition rule..."

Reference: https://stackoverflow.com/a/4445772/1294184


提交答案