Ray,
I use Xerces-C on Solaris, HPUX, and AIX, and have had no problems with
the memory. I'm currently using Xerces 1.3.1, because that's the API our
code was written against. Since it looks like 1.5 will soon be out, I will
have
to look at moving to 1.4 - I don't like bleading edge stuff - I prefer
stability.
Solaris shared libs (the default for UNIX) do not have the issues that
Windows does, at least as far as mixing runtimes. Just always use the
shared libs. In fact, unless you need special transcoding, just use the
prebuilt shared libs that are available.
That way, if you mix in a static lib, it's no problem at all. You just link
it in,
and everything continues to work. Static and shared libs can be mixed and
matched almost anywhere on Solaris. You do need to use special switches
to tell the linker what you want to do, but it's easy.
So maybe you are seeing another cause of the problem? If Solaris breaks in
the same way as Windows, I'd suspect that there is a code problem, rather
than the same problem on both platforms in regards to libraries.
Let me know if I can help at all,
--Carl
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
