Port to gcc-4.3 (template template issue)

[ndbecker2]

On upgrading from gcc-4.1.2 to gcc-4.3, this (stripped down) code is
now
rejected:

#include <vector>
#include <iostream>

template<typena me T, template <typename Aclass CONT=std::vecto r>
class Ring {

};
template<typena me Cont>
inline std::ostream& operator<<(std: :ostream& os, const Ring<Cont>& r)
{
os << '[';
os << ']';
return os;
}
g++ -c test1.cc
test1.cc:11: error: type/value mismatch at argument 2 in template
parameter
list for template<class T, template<class Aclass CONTclass Ring
test1.cc:11: error: expected a template of type template<class A>
class
CONT , got template<class _Tp, class _Allocclass std::vector

What is a reasonable way to fix this? The problem is that the 2nd
parameter
says

template<typena me Aclass CONT, which doesn't match std::vector
because it
has an optional 2nd parameter (class _Alloc).

I don't want to only match class CONT with those having a 2nd
parameter
(class _Alloc) - that is too restrictive.

[dizzy]

nd*******@gmail .com wrote:

On upgrading from gcc-4.1.2 to gcc-4.3, this (stripped down) code is
now
rejected:

#include <vector>
#include <iostream>

template<typena me T, template <typename Aclass CONT=std::vecto r>

^^^^^^^^^^^^^^^ ^^^^^^^^^^^^^^^ ^^^^^^^^
Invalid code.

g++ -c test1.cc
test1.cc:11: error: type/value mismatch at argument 2 in template
parameter
list for template<class T, template<class Aclass CONTclass Ring
test1.cc:11: error: expected a template of type template<class A>
class
CONT , got template<class _Tp, class _Allocclass std::vector

I am surprised to find out that gcc 4.1.2 allowed that (tested it on mine
with -pedantic -ansi and still allows it, bad gcc).

What is a reasonable way to fix this? The problem is that the 2nd
parameter
says

template<typena me Aclass CONT, which doesn't match std::vector
because it
has an optional 2nd parameter (class _Alloc).

I don't want to only match class CONT with those having a 2nd
parameter
(class _Alloc) - that is too restrictive.

The standard clearly specifies that your number and type of template
parameters of a template template parameter must match exactly with the
arguments given (including a default argument). The usual "workaround " is
to properly declare the template template parameter as taking the right
number of template parameters and if you want a default make it so for it,
that is in your case make it:

template<typena me T, template <typename A, typename = std::allocator< A
class CONT=std::vecto r>

C++0x does not remove this restriction (and actually extends it for variable
template parameters too) but I supose C++0x template aliasing feature can
help here (ie you make your code take template template parameter of a
single template parameter but you can create aliases that act like single
parameter templates for std::vector<T, allocator<T and pass that).
--
Dizzy

[ndbecker2]

On May 2, 7:55 am, dizzy <[e-mail] twrote:

ndbeck...@gmail .com wrote:

On upgrading from gcc-4.1.2 to gcc-4.3, this (stripped down) code is
now
rejected:

#include <vector>
#include <iostream>

template<typena me T, template <typename Aclass CONT=std::vecto r>

^^^^^^^^^^^^^^^ ^^^^^^^^^^^^^^^ ^^^^^^^^
Invalid code.

g++ -c test1.cc
test1.cc:11: error: type/value mismatch at argument 2 in template
parameter
list for template<class T, template<class Aclass CONTclass Ring
test1.cc:11: error: expected a template of type template<class A>
class
CONT , got template<class _Tp, class _Allocclass std::vector

I am surprised to find out that gcc 4.1.2 allowed that (tested it on mine
with -pedantic -ansi and still allows it, bad gcc).

What is a reasonable way to fix this? The problem is that the 2nd
parameter
says

template<typena me Aclass CONT, which doesn't match std::vector
because it
has an optional 2nd parameter (class _Alloc).

I don't want to only match class CONT with those having a 2nd
parameter
(class _Alloc) - that is too restrictive.

The standard clearly specifies that your number and type of template
parameters of a template template parameter must match exactly with the
arguments given (including a default argument). The usual "workaround " is
to properly declare the template template parameter as taking the right
number of template parameters and if you want a default make it so for it,
that is in your case make it:

template<typena me T, template <typename A, typename = std::allocator< A
class CONT=std::vecto r>

C++0x does not remove this restriction (and actually extends it for variable
template parameters too) but I supose C++0x template aliasing feature can
help here (ie you make your code take template template parameter of a
single template parameter but you can create aliases that act like single
parameter templates for std::vector<T, allocator<T and pass that).

--
Dizzy

Thank you so much for the excellent explanation!

It seems to me, though, that this makes template template much less
useful.