CODEWITHSUNDEEP
c++file-handlingfilestreams
Arun
Arun

Reputation: 3408

c++ filestream problems when opening file in read write mode

Consider the following code snippet:

const char * filePath = "C:/blah.mtt";
fstream fs(filePath, ios::in | ios::out | ios::binary);
if (fs.fail())
   std::cout << "Failed to open the file!\n";

the fs.fail() check succeeds always. Does it mean that I can't open a file in both read write mode at the same time?

Creating an empty file first and then running the above code, fs.fail() is false always. What is the rational for such a behavior by the fstream class?

Note: I do have requisite permissions for creating the file. I am trying this on windows 10 using VS2015

Upvotes: 2

Views: 981

Answers (2)

Neijwiert
Neijwiert

Reputation: 1025

the fs.fail() check succeeds always. Does it mean that I can't open a file in both read write mode at the same time?

Refer to @Lightness Races in Orbit's answer for a better explanation.

Creating an empty file first and then running the above code, fs.fail() is false always. What is the rational for such a behavior by the fstream class?

If you look at the constructor definition of fstream you can see that mode defines the way you open it. It has other options like app to append to an existing file. If you open up a file using the following code:

fstream fs(filePath, ios::in | ios::out | ios::binary);

You are saying create a new file if it doesn't exist. Which fails if you pre-created it. You should add the app, ate or truncflag if you want it to open successfully. This depends on what exactly you want to do. However, do note that in between the steps of creating and then opening it doesn't guarantee that the file is still there. You should try to do it in one swoop and let exception handling do its work, since you can never go around the errors anyway.

Upvotes: 1

Lightness Races in Orbit
Lightness Races in Orbit

Reputation: 385194

Does it mean that I can't open a file in both read write mode at the same time?

No, you can do this, but the question is whether you can create a file by doing so.

Generally you'll need to add the trunc flag (ironically one of the options for how to handle an existing file), or remove the in flag (see here).

Yes, this is a bit of a pain, but it comes from how the original POSIX APIs work. Blame them!

Creating an empty file first and then running the above code, fs.fail() is false always. What is the rational for such a behavior by the fstream class?

You can always open a file that exists (well, subject to permissions). That behaviour makes sense.

Upvotes: 4

Related Questions