Re: VC6 + Dinkumware fixes OK for basic STL usage?
P.J. Plauger wrote:
I haven't been to your site for a while, and hadn't seen this V-express
edition. But on the web site I don't see anything about using it with VC6
(though it's late and maybe I am missing it).
No, we kinda forgot to mention that part.
Is this V-express all in header files that I can just include ahead of the
existing standard library,
It's not all headers, but yes you do just include our headers ahead of
the existing ones, and link our binaries ahead of the existing ones.
That's the way we always package our libraries.
>>What about static/dynamic linking, or
doesn't it matter? FWIW I use static linking and have several projects
that I am maintaining in VC6, and this sounds great.
IIRC we only ship dynamically linked libraries, though you can indeed
build static libraries from the source.
PJ:
Thanks for the info.
Surely, the VC6 piece is important, you should mention it. One of the
criticisms always leveled at VC6 is the C++ library (though with the
patches it has always worked for my simple needs).
I assume that you can get the binaries for each of the compilers VC6,
VC7.1, VC8 ? (I don't care about VC7, not many do.)
But what is in these binaries? When I got the VC6 patches, I noted a
warning on the site that there could be a problem with dynamic linking
because MSVCP60.DLL contained the unpatched versions. Since I use static
linking, I didn't worry about it, assuming that there were not
corresponding static libraries in the static linking case. Was this wrong?
If binaries for static linking of V-express are required, why do you not
provide them? And if I have to build them myself, where is the source to
build them from? In the VC distributions I see source for MFC and CRT,
but not for the C++ library.
I guess I am a bit confused about these binaries :).
David Wilkinson