std::string IO

[ajbharani]

#include<iostream>
int main()
{
 std::string szName;
 std::cin >> szName;
 std::cout << szName << std::endl;
 return 0;
}

This code, while compilation gives the following error.

--------------------Configuration: BasicString - Win32 Debug--------------------
Compiling...
Test.cpp
d:\bharani\programming\c++\basicstring\test.cpp(6) : error C2679: binary '>>' : no operator defined which takes a right-hand operand of type 'class std::basic_string<char,struct std::char_traits<char>,class std::allocator<char> >' (or there is no ac
ceptable conversion)
d:\bharani\programming\c++\basicstring\test.cpp(7) : error C2679: binary '<<' : no operator defined which takes a right-hand operand of type 'class std::basic_string<char,struct std::char_traits<char>,class std::allocator<char> >' (or there is no ac
ceptable conversion)
Error executing cl.exe.
Test.obj - 2 error(s), 0 warning(s)

What may be the problem?

Thanks.

[Philip Nicoletti]

Yiu need to:

#include <string>

[ajbharani]

Thanks. So is the intellisence independant of the headers we have included?

[Paul McKenzie]

Thanks. So is the intellisence independant of the headers we have included?

Intellisense is not C++.

If you're going to use std::string, then you must include the <string> header. Don't solely rely on third-party tools such as Intellisense to determine proper C++ coding.

Regards,

Paul McKenzie

[Zaccheus]

To be fair that's a rather silly error message. "std::string not defined" would have been more intuitive.

[Paul McKenzie]

To be fair that's a rather silly error message. "std::string not defined" would have been more intuitive.

I think that std::string is forward declared within the stream headers, so it is difficult for the compiler to emit such an error.

Regards,

Paul McKenzie

[Zaccheus]

Ah yes, and such an operator could have been declared using just such a forward declaration, good point.