Passing STL container to temlate function

[Active8]

vector<double> signal;
vector<double>: :iterator iter;

in_file.load_ve ctor(signal);
in_file.load_ve ctor(signal.beg in());

those calls give the compiler error:
"could not deduce template argument for 'T'"

the infile object is a non-template class with a template function
in it

class Files
{
...
template <class T>
load_vector(vec tor<T>& sig);
...
};

template <class T>
int Files::load_vec tor(vector<T>& sig)
{
return 0;
}

What can I do about this?

TIA
--
Best Regards,
Mike

[Alf P. Steinbach]

* Active8:

vector<double> signal;
vector<double>: :iterator iter;

in_file.load_ve ctor(signal);
in_file.load_ve ctor(signal.beg in());

those calls give the compiler error:
"could not deduce template argument for 'T'"

the infile object is a non-template class with a template function
in it

class Files
{
...
template <class T>
load_vector(vec tor<T>& sig);
...
};

template <class T>
int Files::load_vec tor(vector<T>& sig)
{
return 0;
}

What can I do about this?

To do: be more precise (most of the information you've provided is
irrelevant, and the word "those" is incorrect; with the irrelevant
information removed and that word corrected you have your solution).

--
A: Because it messes up the order in which people normally read text.
Q: Why is it such a bad thing?
A: Top-posting.
Q: What is the most annoying thing on usenet and in e-mail?

[Active8]

On Wed, 23 Feb 2005 09:39:15 GMT, Alf P. Steinbach wrote:

* Active8:

vector<double> signal;
vector<double>: :iterator iter;

in_file.load_ve ctor(signal);
in_file.load_ve ctor(signal.beg in());

those calls give the compiler error:
"could not deduce template argument for 'T'"

the infile object is a non-template class with a template function
in it

class Files
{
...
template <class T>
load_vector(vec tor<T>& sig);
...
};

template <class T>
int Files::load_vec tor(vector<T>& sig)
{
return 0;
}

What can I do about this?
To do: be more precise (most of the information you've provided is
irrelevant,

Other than the compiler (VC++) what info *would* you consider
"relevant"? The code I posted is all the code (except compiler
supplied headers) pertaining to the template function that won't
compile. I included the call that I used when I tried passing an
iterator.
and the word "those" is incorrect;
no it isn't.
with the irrelevant
information removed and that word corrected you have your solution).

calls give the compiler error:
"could not deduce template argument for 'T'"

Doesn't help. AFAICT, the syntax is right and it should work like
any other code written the same way like this code from an online
ref.

template <class T>
T GetMax (T a, T b) {
return (a>b?a:b);
}

int main () {
int i=5, j=6, k;
long l=10, m=5, n;
k=GetMax(i,j);
n=GetMax(l,m);
cout << k << endl;
cout << n << endl;
return 0;
}

That ref also shows this calling convention:

in_file.load_ve ctor<double>(si gnal);

which generates this error:

"type 'double' unexpected"

--
Best Regards,
Mike

[Alf P. Steinbach]

* Active8:

On Wed, 23 Feb 2005 09:39:15 GMT, Alf P. Steinbach wrote:

* Active8:

vector<double> signal;
vector<double>: :iterator iter;

in_file.load_ve ctor(signal);
in_file.load_ve ctor(signal.beg in());

those calls give the compiler error:
"could not deduce template argument for 'T'"

the infile object is a non-template class with a template function
in it

class Files
{
...
template <class T>
load_vector(vec tor<T>& sig);
...
};

template <class T>
int Files::load_vec tor(vector<T>& sig)
{
return 0;
}

What can I do about this?
To do: be more precise (most of the information you've provided is
irrelevant,

Other than the compiler (VC++) what info *would* you consider
"relevant"?

The signature of the function called, the call, the error message,
and possibly also the compiler (in this case it isn't compiler-specific
but you couldn't know that), for best effort the sig+call packaged as
a small program that one can copy, paste and compile.

The code I posted is all the code (except compiler
supplied headers) pertaining to the template function that won't
compile. I included the call that I used when I tried passing an
iterator.

and the word "those" is incorrect;

no it isn't.

Well, it is. ;-)

Consider the signature of your function again.

Hint 1: in there you'll see the word "vector". Hint 2: one of your
calls doesn't pass a "vector". Hint 3: the other one does.

--
A: Because it messes up the order in which people normally read text.
Q: Why is it such a bad thing?
A: Top-posting.
Q: What is the most annoying thing on usenet and in e-mail?

[Active8]

Oh yeah. Thanks Alf.
--
Best Regards,
Mike

[Active8]

On Wed, 23 Feb 2005 23:47:17 GMT, Alf P. Steinbach wrote:

Consider the signature of your function again.

Hint 1: in there you'll see the word "vector". Hint 2: one of your
calls doesn't pass a "vector". Hint 3: the other one does.

I finally found that, duh!

I'll post a small complete module next time, but notice that I was
correct in asuming that what I posted was enough :)
--
Best Regards,
Mike