>> But now I see new ones, further down in Xerces.cpp - I guess I'll >> give it up for the moment.
> Ah, let me know what these are. Your strategy of putting #undef's in > Xerces.cpp is the correct one.
No, there aren't any more errors. Somehow I had managed to insert some erratic linebreaks into xerces.cpp which broke it.
So - if you adapt 2.4.0 to the current Xerces-C API and fix the _p_void issue, I'd be happy ...
Martin
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
