I know that when we are using template inside another template, we should write it like this:
vector
and if we wr
C++ is really incredibly hard to parse -- much more difficult than most other languages. It is a very consistent language, but so much work is done between tokenizing the input and understanding the grammatical analysis of the syntax, that things that seem like they should be simple for a compiler, often are NOT.
The historical ">>
" operator is an operator. It is "identified" as the source file is broken into tokens. Those tokens are then later "understood" in some context during grammatical analysis (long after tokenization is complete).
If you did grammatical analysis while you tokenized, then you have "helps" to assist in the distinction that ">>
" should be considered as two closures to a template declaration (or definition). Yet, this is historically not how historical C++ compilers work. (New compilers do more feedback between grammatical analysis and tokenization, including more "look-aheads" to help resolve these ambiguities.)
Yes, the new C++0x standard changes that, and forces compiler vendors to re-write their implementations to disambiguate ">>
" in your case. So, it will never be ambiguous going forward. However, older C++ compilers cannot handle that, so it may be considered "good practice" to keep your code compatible with the space between the '>
' characters for now.
Avoid this error by setting an appropriate C++ dialect. For example, with gcc 4.9 the following file does not compile with g++
:
#include <vector>
#include <utility>
int main()
{
using namespace std;
vector<pair<int, int>> v; // compile error!
return 0;
}
Let's get to the bottom of things:
#include <iostream>
int main()
{
std::cout << __cplusplus << std::endl;
return 0;
}
Compiled with just g++ test.cpp
this code prints 199711. Although gcc 4.9 was released in 2014 the default C++ dialect is C++98 with GNU extensions. C++98 requires us to write vector<pair<int, int> >
. If you like vector<pair<int, int>>
more compile with -std=c++11
or -std=gnu++11
.