Thread: std::ifstream, flags

Ok, so this is what I did:
1) include <fstream>
2) create std::ifstream called "file"
3) call file.open(filename, ios::in | ios::binary | ios::nocreate)

So it says that ios is an invalid namespace or something.

4) change ios::whatever to std::ios::whatever

It gets rid of all the errors except for a new one that says that std::ios::nocreate doesn't exist.

5) include <fstream.h> and change std::ios::whatever to ios::whatever

It gets rid of all the errors.

Later, I tried to call file.seekg(position, ios::end). It gives me an error and says that ios::end doesn't exist. I tack on std::, and it works.

So my question is, is there any problem with mixing <fstream>'s stuff with <fstream.h>'s stuff?

Dunno, I sorta have a thing against doing that But still, is there any incompatibility or anything if I mix the <fstream> stuff with the <fstream.h> stuff?

Originally posted by Hunter2
Dunno, I sorta have a thing against doing that But still, is there any incompatibility or anything if I mix the <fstream> stuff with the <fstream.h> stuff?

yes some things are incompatible, a better way is like this

Code:

#include <fstream>

using std::ifstream;

int main( )
{
   ifstream fileOut( "test.txt" );
   fileOut.close( );
   return 0;
}

To answer your question very specifically, 'nocreate' is a Microsoft implementation. Borland, for one, doesn't recognize it and I would be surprised if other compilers did either.

This is why using 'std::' corrected all but one of your errors using <fstream>. As you found, though, 'nocreate' is non-standard requiring <fstream.h> be included - again, specific to the MSVC++ compiler.

I don't have a serious problem with MSVC++, and don't intend to get into any debates with those who do have problems with it, or Microsoft, for that matter. That discussion doesn't belong on this Board anyway.

Just recognize that there will be compatibility issues when you try to mix standard and non-standard headers.

-Skipper

Ok, thanks. But is there any standard equivalent of nocreate? Or is there any other way to make sure that the file exists?

Code:

#include <fstream>

using std::ifstream;
using std::cout;

int main( )
{
   ifstream fileOut( "test.txt" );
   fileOut.close( );

   if( !fileOut )
      cout << "unable to open file\n";

   return 0;
}

You mean it won't create a file even if I don't use ios::nocreate? And fileOut will be NULL? Or could I use if(!fileOut.isOpen())?

P.S. I'm trying to open it in binary mode, not text mode.

P.P.S. Why do you call fileOut.close()?

If it cannot open the file for whatever reason, this normally works. I am not sure why exactly, I think it works using the failbit in the ifstream object, but I'm sure the is_open function will get you pretty much the same results.

This code works fine (one of the few times i test what I post )

Code:

   ifstream fileOut( "test.exe", ios::binary | ios::nocreate );

   if( !fileOut )
      cout << "unable to open file\n";

   fileOut.close( );

And I always close the file, force of habit really but its a good practice to use and means you can use the fstream object to open a different file if needed.

Code:

int main( )
{
   ifstream fileOut( "test.txt" );  //create fileOut, open test.txt
   fileOut.close( );  //close test.txt

   if( !fileOut )  //if the file is closed,
      cout << "unable to open file\n";  //say "unable to open file"

   return 0;
}

That's what I meant.

I think it works using the failbit in the ifstream object

I doubt it. Check this out:

If the file is not found, then the ios::failbit is set only if the ios::nocreate mode was used.

And looky!

ifstream fileOut( "test.exe", ios::binary | ios::nocreate );

If you only included <fstream>, ios::nocreate couldn't have worked. You must have included <fstream.h> too! And then fileOut would be either mixing standard/nonstandard or just using nonstandard. And later, if you want to call seekg and use the ios::end flag, there is only a std::ios::end flag, no ios::end flag. Thus, you would be mixing standard and non-standard no matter what Thus, since I need to use ios::end, I have opted against using ios::nocreate in order to keep things standard.