Re: iostream compatibility
Varghese Paul wrote:
I use many third party LIBs in my application out of that one uses old
nonstandard iostream and all others uses new STLport iostreams. The
application compiles in VS2008 and runs fine in x86 mode. I use VC6.0 to
compile the old LIB (which uses old iostream) and finally links this LIB
with the application using VS2008.
Oh. It surprises that this works at all, because normally output of C++
compilers are incompatible. Adding different implementations of the C++
standardlibrary adds another incompatibility.
Now I want to port this application to 64 bit (x64) where the old iostream
creates linker problems. Old iostream libraries LIBCIMT.LIB, LICIMTD.lib
etc are not x64 compatible.
Do I need to replace the old iostream with the new one?
Is the old and new iostreams are functionally compatible?
How I can replace the following functions
ostream::osfx()
ostream::opfx()
Take a look at std::ostream::sentry.
streambuf::allocate()
streambuf::doallocate()
streambuf::blen()
streambuf::base()
streambuf::ebuf()
streambuf::setb()
These all seem to be related to the underlying buffer. Similar things exist
for standard IOStreams, though the baseclass only provides methods for
access, not for creation of such a buffer. Instead, typically a derived
class would do that.
Is there any alternative to minimize my code changes?
Alternatively you could first remove the buffer tweaking completely and rely
on the internal buffering first. If that doesn't perform, you can still
tune it using standard functions.
Uli
--
Sator Laser GmbH
Gesch??ftsf??hrer: Thorsten F??cking, Amtsgericht Hamburg HR B62 932