Comments on: 14.6 — Partial template specialization

By: vikas

vikas — Thu, 19 Jan 2012 06:41:40 +0000

Hii Alex
s there any concept of WRAPPER CLASS in C++, if yes then please give any idia how to use it. If u hav prepared any tutorial then please mention ur link.

thank in advance

By: sandyleo26

sandyleo26 — Wed, 08 Jun 2011 17:40:29 +0000

Hi, c++ standard doesn’t allow partial specification for function template. Partial specification only available for class. So the PrintBufferString example is not a partial specification. It’s function template OVERLOAD which mimic the behavior of partial specification. Please correct this.

By: mccp13

mccp13 — Fri, 06 May 2011 11:42:42 +0000

please help, how would the Print function in Buffer class be implemented as template specialization for double.. would it be something like :

template
void Buffer::Print()
{
for( int nCount=0 ; nCount < nSize ; ++nCount )
std::cout << std::scientific << m_atBuffer[nCount] << std::endl;
}

By: Janis

Janis — Fri, 22 Oct 2010 15:29:41 +0000

Is “int” a misspelling here?

template
void PrintBufferString(Buffer &rcBuf)
{
    std::cout << rcBuf.GetBuffer() << std::endl;
}

By: george

george — Mon, 19 Jul 2010 07:32:41 +0000

Is this

m_tValue = new T(*tValue);

an implicit initialization for the value pointed by m_tValue? In other words, is it equivalent to:

m_tValue = new T;
*m_tValue=*tValue;

By: george

george — Sat, 17 Jul 2010 17:29:05 +0000

I don't understand why this function

void PrintBufferString(Buffer &rcBuf)

should take only a literal, and not an integer argument like this:

void PrintBufferString(Buffer &rcBuf)

? Is it because function templates can not take an expression parameter (in this case int)? But then

Buffer

is just a parameter type to the function, and should be OK.

By: C++ Tutorial and Online Ebook

C++ Tutorial and Online Ebook — Wed, 30 Jun 2010 01:13:40 +0000

[...] 14.6 Partial template specialization [...]

By: User

User — Mon, 18 May 2009 05:34:27 +0000

in the “Partial template specialization for pointers” section, the point of specializing a version for pointer type was to deal with the issue of shallow/deep copy on constructor call. However you could imagine the following (pointer to pointer):

int x = 7;
int *y = &x;
Storage cIntPtrPtrStorage(&y);

By: mohammad

mohammad — Sun, 19 Oct 2008 21:17:42 +0000

in the first code:

int& operator[](int nIndex)
{
    return m_atBuffer[nIndex];
}

shouldn’t the return value be T& instead of int& ?

[ Yes, definitely. Thanks for the catch. -Alex ]

By: Learn C++ - » 15.1 — Introduction to exceptions

Learn C++ - » 15.1 — Introduction to exceptions — Sun, 05 Oct 2008 19:04:19 +0000

[...] 14.6 — Partial template specialization [...]