True, as always portability issues hinder development at times. It's just a decision that has to be made. One possible, but undesired way is to make an STL-compliant version of Xerces and a non-STL version (the current version).
This would be a major headache of course and I personally wouldn't do it. we've been working quite fine without it thus far ... it is however an option. ..:: Keno ::.. > > I said portable/reliable. Last I'd heard, C++ namespaces are not > available/trustworthy on some parsers. You have to decide whether you're > willing to abandon users who can't/won't upgrade. > > (Same problem the Java folks face when we want to use features introduced > in Java 1.2 and later. I'd _love_ to stop worrying about Java 1.1.8. > Unfortunately, while the development community has mostly upgraded, some > folks apparently have customers which haven't.) --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
