getline() don't want to work anymore...

Hi, I've got some problem with getline(), it doesn't want to work and I get some puzzling errors from the compiler... So I want to read on a file using "getline", a string and the file itself... So I have something like this, and it always worked before:

Code:

std::ifstream File;
std::string Temp;

File.open("somefile.ext", std::ios::in);
std::getline(File, Temp); //doesn't work...
getline(File, Temp); //doesn't work either...

I don't understand why, but I get errors telling me that "getline" couldn't be found, or that "std::getline" isn't part of "std::"... I have included in my file those headers:

Code:

#include "iostream"
#include "string.h"
#include "fstream"

And even if I try with/without "using namespace std;" it doesn't change a thing...
However in all my previous program I used getline this way and it always worked, but in this case I don't have a clue... Even if you point your cursor on "getline()" and see what are its prototypes, it seems to be of "std"... It writes some "std::basic_istream" things so I believe it should be working...

The string class, and it's getline function reside in <string>, not <string.h>.

Wha? It was just that! So simple! Now it works correctly! Thanks a lot!

... em, shouldn't the followint (

#include "iostream"
#include "string.h"
#include "fstream"

) be the following?

#include <iostream>
#include <string.h>
#include <fstream>

??

Originally Posted by twomers

... em, shouldn't the followint (

#include "iostream"
#include "string.h"
#include "fstream"

) be the following?

#include <iostream>
#include <string.h>
#include <fstream>

??

To match common practice, yes. It's harmless though. If the implementation-defined locations that the compiler searches for "..." don't contain the standard headers, the search is attempted again using <...>. At worst, it's a time sink.

I didn't know that there was a differnce between the "" and the <>... So standard headers should use these <> if they are located in our compiler's headers directory? But on the other hand, using <> on other-directories includes shouldn't fail.?

>I didn't know that there was a differnce between the "" and the <>...
Technically there isn't. Both search implementation defined locations that are unspecified. But it's accepted practice that standard headers go in <...> and everything else goes in "...".

I tend to use <> for anything (even 3rd party libraries) which have been configured in the IDE / makefile as additional include search paths.