SAX/C++: First interface draft

[Jeff Greif]

I think this problem usually can be managed by choice of include path,
assuming you have source code for the SAX library.  If the include directory
for the ObjectSpace headers is found before the include directory for
MSCVC++ standard library when you compile both the SAX library and
application code, the problem with broken parts of the MSVC++ library
version of iostream should be avoided.  But this approach does not work if
you want to use someone else's binary of the library.

Jeff

----- Original Message -----
From: Steinar Bang <sb at metis.no>
To: <xml-dev at ic.ac.uk>
Sent: Monday, December 06, 1999 1:09 AM
Subject: Re: SAX/C++: First interface draft


> I have a practical problem with using std::istream on the MSVC++
> platform.  Since the Standard C++ Library as delivered with MSVC++ 5
> and 6 is broken, we're using Standards<ToolKit> from ObjectSpace to
> provide us with the parts of the Standard C++ Library we're using.
>
> And Objectspace Standards<ToolKit> is not compatible with the Standard
> C++ Library iostreams of MSVC++.



xml-dev: A list for W3C XML Developers. To post, mailto:xml-dev at ic.ac.uk
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/ and on CD-ROM/ISBN 981-02-3594-1
To unsubscribe, mailto:majordomo at ic.ac.uk the following message;
unsubscribe xml-dev
To subscribe to the digests, mailto:majordomo at ic.ac.uk the following message;
subscribe xml-dev-digest
List coordinator, Henry Rzepa (mailto:rzepa at ic.ac.uk)