fopen with std::string

Thank you Daved, i get it now.

Tabstop:
"File I/O is buffered, and if you kill the program (which is the only way this program is going to stop) you may or may not get that buffer written out."

The same program works with fopen(). Does it mean that fopen() not buffered?

The same program works with fopen(). Does it mean that fopen() not buffered?

Reads and writes are buffered. fopen() is not a read or a write...

I meant the combination fopen() with fputs().

Like ofstream with <<.

Yes, fputs() is buffered. You can flush the buffer to the file by calling fflush(), or you can just close the file with fclose().

You can always flush the fstream stream manually as well (using std::flush or std::endl).

Originally Posted by Daved

>> The only thing to really remember is to use std::ios:binary when you are doing read and write if you want code that works on Windows

That doesn't make sense and I'm pretty sure it's not true. I'm not sure why you'd think that.

Try it out yourself then.

I've done reading and writing on Windows many times in text mode and it has worked just fine.

Were you specifically talking about the read and write functions?

Originally Posted by Daved

Were you specifically talking about the read and write functions?

Yes.

And what is it about Windows that make those functions only work in binary mode that doesn't happen on Linux or other platforms?

Originally Posted by Daved

And what is it about Windows that make those functions only work in binary mode that doesn't happen on Linux or other platforms?

I believe it is the view UNIX has, everything is a file, every file is binary (no such thing as text), thus you automatically get the fstream treated as binary.

Originally Posted by Tux0r

I believe it is the view UNIX has, everything is a file, every file is binary (no such thing as text), thus you automatically get the fstream treated as binary.

You are wrong.

The short answer is that you should use text mode if you are reading/writing text, and use binary mode if you are reading/writing binary data. This should be done regardless of what platform you use.

Now it just so happens that Unix systems don't do any character conversions in text mode, so it doesn't matter if use text or binary mode. It is best to just stick to the above principal though, and not rely on the platforms handling of text.

In this case, the poster is dealing with text, so the file should be opened in text mode.

Originally Posted by bithub

You are wrong.

*captain obvious removed*

Now it just so happens that Unix systems don't do any character conversions in text mode, so it doesn't matter if use text or binary mode. It is best to just stick to the above principal though, and not rely on the platforms handling of text.

In this case, the poster is dealing with text, so the file should be opened in text mode.

lol, you say I am wrong then you state what I just said?

Originally Posted by Tux0r

lol, you say I am wrong then you state what I just said?

You stated:

Originally Posted by Tux0r

The only thing to really remember is to use std::ios:binary when you are doing read and write if you want code that works on Windows

Granted, bithub did not quote that, but the principle (or perhaps rule of thumb) that bithub proposed is in contradiction to the one that you proposed.

The only thing to really remember is to use std::ios:binary when you are doing read and write if you want code that works on Windows

This is wrong. He is using text, he should not be using binary mode to read and write. My post was to clarify this.

every file is binary (no such thing as text),

This is wrong. Every file in unix is not binary. There are plenty of text files (look at everything in the /etc directory). Just because Unix does not perform text conversion does not mean there is "no such thing as text".

I fail to see how I stated what you said. You said "use binary". I said "use text". Those seem to be the opposite...

Originally Posted by bithub

This is wrong. He is using text, he should not be using binary mode to read and write. My post was to clarify this.

This is wrong. Every file in unix is not binary. There are plenty of text files (look at everything in the /etc directory). Just because Unix does not perform text conversion does not mean there is "no such thing as text".

I fail to see how I stated what you said. You said "use binary". I said "use text". Those seem to be the opposite...

I don't see why to argue about this but oh well. I was just giving OP an advice that is not directly related to the original question (remember to use std::ios::binary when using read and write if you want windows compatibility). And so:

>> Now it just so happens that Unix systems don't do any character conversions in text mode, so it doesn't matter if use text or binary mode. It is best to just stick to the above principal though, and not rely on the platforms handling of text.

is just restating what I said about it being vague on UNIX. I don't see why you said I was wrong and then came to the conclusion that I came to as well (marked bold).


also http://en.wikipedia.org/wiki/Binary_file#Manipulation