|
Page 2 of 2
Solution
You add some code to the program in an effort find out what is happening but the result is only that you get very confused.
If you add this line in the main() function, you get a compiler error:
std::cout << data.at(0) << std::endl;
The compiler error message gives you a hint:
request for member ‘at’ in ‘data’, which is of non-class type ‘std::vector<std::basic_string<char> > (std::istream_iterator<std::basic_string<char> >, std::istream_iterator<std::basic_string<char> > (*)())’
The cause of the problem is that the compiler thinks it is facing a function prototype!
However, you want to create a vector, which is a variable definition. Clearly you are not interpreting the syntax in the same way.
How does the compiler see a function prototype?
Look again at this line:
vector<string> data( istream_iterator<string>(cin), istream_iterator<string>());
First of all, we have the return type (vector<string>). After, we see the function name (data).
The rest is more difficult to see.
istream_iterator<string>(cin)
is seen as
istream_iterator<string> cin
by the compiler. The compiler saw a parameter because the parentheses are superfluous.
Nevertheless, how does the compiler see the last argument?
It sees it as a pointer to a function which does not take any argument and returns istream_iterator<string>.
So the line can be read and interpreted as a function prototype!
To fix the problem, there are a few options: You may add parentheses around argument like this:
vector<string> data(( istream_iterator<string>(cin)), (istream_iterator<string>()));
You may use the copy initialization:
vector<string> data = vector<string>( istream_iterator<string>(cin), istream_iterator<string>());
And if your compiler supports C++0x, you may use initializers list:
vector<string> data{ istream_iterator<string>(cin), istream_iterator<string>()};
Pattern
One way to avoid this problem happening is to always use copy initialization:
vector<string> data = vector<string>( istream_iterator<string>(cin), istream_iterator<string>());
Using this, you are sure it won't look like a function prototype.
Another rule to follow is to write code that uses the vector (like the at() method) after the declaration so you get a compiler error that will help you spot ambiguities.
More Puzzles
Sharpen Your Coding Skills Self-Descriptive Arrays
Put on your thinking cap for another set of conundrums that will exercise your coding skills. This time Melvin Frammis introduces his junior partner Bugsy Cottman to some classic number puzzles that c [ ... ]
|
Javascript JavaScript Puzzle - The Too Tidy Assignment
There is a rule about not optimizing code too soon. Perhaps we should add to that the rule that being too tidy is often a mistake. Here we have a JavaScript example where things go wrong because of an [ ... ]
|
Sharpen Your Coding Skills The Best Sub-Array Problem
At first glance this puzzle seems trivial, all you have to do is find a sub-array, in an array of numbers, that sums to the largest value. It sounds almost too easy to need a solution, let alone [ ... ]
| | Other Articles |
<ASIN:0132673266>
<ASIN:059600298X>
<ASIN:0321334876>
<ASIN:156592116X>
|