C/C++: cout/ostream/istream vs (f)printf/scanf

[neurocomp2003]

is there any advantages to using one text I/O method over another
I'm more accustom to the prinft/scanf but i seem to see ostream/istream within C++ coding style( prolly because of the OO)

but is there really a difference?

 

[dduardo]

Functionally they aren't very different. count ,ostream, istream are just geared more toward OO programming like you mentioned.

 

[Sir_Deenicus]

The main difference between the two is in the flexiblity which the iostream methods give you over the C standard functions. ostream is more extensible, allowing you to easily handle (overload) your user defined types while also ensuring type safety. Basically, you can do more complex things more elegantly with ostream.

 

[dduardo]

Sir_Deenicus, sure you can do all that, but for most people they don't use those capabilities so functionally to them it is basically the same.

 

[neurocomp2003]

you mean i can't overload the printf with a printf(Type& ) operator and use varg in the function?

 

[dduardo]

Yeah, you can do that, but you can also overload << and >>.

 

[neurocomp2003]

yeah i know you can overload the <<, >>

was just curious at what Sir_Deenicus was indicating about the
extensibility...i just don't like <<,>> because i find it easier to format text
with printf. rather than setprecession(...) etc.

 

[Hurkyl]

you mean i can't overload the printf with a printf(Type& ) operator and use varg in the function?

Not really. I assert it would be very difficult to create useful overloads printf so that it usually behaves similarly to that of the C library. The problem is that you'll have to overload it for every type combination that you'll ever expect to write.

Now, some libraries do provide mechanisms for introducing new types into printf's mechanism, and this should be doable. (But, of course, library specific)


One advantage that you should not ignore is this:

count << setprecision(5) << value << endl

is much clearer than

printf("%5f", value)

in fact, I suspect I have the printf version wrong; I have to hit the man pages any time I want to do something nontrivial with C-style i/o. At one time, it used to take quite a while to find the relevant entry, but I've had to do it often enough that I can usually remember at where and in what man page I need to look.

 

[neurocomp2003]

lol man pages...i hate linux/unix hehe...nah its %#.5f and I'm rather accustomed to using it especially doing things like %+-10.5f, +-10.5f I'm pretty sure you could probably right it into a string and send it into printf though, but I've seen some nice techniques if you know how to use varg vbegin.

 

[Sir_Deenicus]

Well I had in mind where you hand to handle complex file loading and had to use such things as vector templates and probably templates in general and have them interact seamlessly with your objects. There, the ostream library is superior. Also I do not see why you would overload the printf -which you cannot do as an operator anyway- that is not a very good idea at all and is in principle not necessary. Also printf does not protect agaisnt buffer overflows and does not give you much safety or flexibility over strings...The list goes on.

Printf is just a quick and dirty way to get stuff out into output or vice versa with scanf.