I ve read that iostream is a derived class of fstream ,so including the "fstream" header is all sufficient to perform console i/p and o/p(ie cin and cout) .this worked fine as long as I used Turbo C++ compiler but now I ve switched to Bloodshed Dev C++ compiler and it gives an error that cin is not recognized....it works fine only if I include both "iostream" and "fstream" in my program ....please help
sugantha 0 Newbie Poster
Recommended Answers
Jump to PostSome C++ compilers do not require IO imports to include cin/cout. The same is true with some C compilers and printf etc.
Jump to PostWell, according to this:
http://www.cppreference.com/cppio/index.html
cin, cout are defined in iostream.
And this will also help ypu understand what is going on.
http://www.cplusplus.com/ref/iostream/I hope it …
All 6 Replies
alpha_foobar 5 Junior Poster
Some C++ compilers do not require IO imports to include cin/cout. The same is true with some C compilers and printf etc.
Micko 2 Junior Poster
Well, according to this:
http://www.cppreference.com/cppio/index.html
cin, cout are defined in iostream.
And this will also help ypu understand what is going on.
http://www.cplusplus.com/ref/iostream/
I hope it helps!
sugantha 0 Newbie Poster
I think you did'nt read my question clearly...I asked if iostream is a derived class of fstream then it has to inherit all its properties...so cin and cout SHOULD work fine....it does so with the Borland compiler but not with Dec-C++ compiler ...why??
Salem 5,265 Posting Sage
Does your borland compiler also work if you include iostream (only) to get cin and cout ?
sugantha 0 Newbie Poster
yes...it works fine
Salem 5,265 Posting Sage
OK, so use that then from now on and don't assume that a particular implementation choice about the inheritance of various objects will be true in other implementations.
My guess is you "got away with" using fstream for cout previously, but this "trick" no longer works on your new compiler.
Which is why you should learn from high quality sources of documentation (like the C++ standard), rather than relying on your reverse engineered observations of a particularly old compiler.
Using multiple compilers even when you don't have to is also a good way of flushing out any assumptions you might be making.
I'm presently using 3 different compilers with pretty strict error checking. It's been a long while since I last used just one compiler for a whole project.
Be a part of the DaniWeb community
We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.