John Bossom wrote:
the XALAN_CLASSIC_IOSTREAMS only controls which headers are included. (i.e. <blah.h> vs <blah>)
The application of the namespace "std" is still controlled by a single macro, XALAN_NO_STD_NAMESPACE whether it be IO classes or STL container classes.
... <long quoting snipped> ...
Can you just use the STLPort IOStreams, instead of the OS's IOStreams? STLPort IOStreams is quite robust, in my experience. That would put everything into the std namespace.
Alternatively, you can compile STLPort so everything is in the global namespace, as I recall. That would put everything into the global namespace.
As a last resort, you could define a macro "std" that resolves to nothing. Long ago I did this with STLPort (ver 3.something, as I recall), and it worked. It might be worth a try.
Don McClimans
