"Adam Fineman" <aB**************@KcIoNmGpSuter.org> wrote in message
news:XX****************@news.uswest.net...
| For those of you who would say this without the '<g>':
|
http://parashift.com/c++-faq-lite/input-output.html
The only reason for me not liking iostreams is the bulkiness of it (at least
the compilers I've used: msvc, borland, intel, digital mars, gcc) compared
to the C equivalents. But this is just my opinion, and I know that with the
added object footprint comes excellent type-safety and all that good stuff.
I guess that I am just too accustomed to using the printf/scanf family. Also
I know that Bjarne states on his website
(
http://www.research.att.com/~bs/bs_faq.html#Hello-world) stating that it's
all in the implementation...I just haven't found a good C++ std lib that
does just that.
I've seen wars errupt over such controversial subject and I am not attemping
to start one, just stating my opinion. For beginners iostreams is almost a
must as it does most the the error checking for them. For seasoned
developers and small projects, being *one* with your code prevents any
errors at all omitting the need for the iostreams checking.
Oh, and another thing, the overloaded left and right shift operators bug me
that they are used for something other than bit shifting =)