I'm way too out of the loop these days to be of much help on that front. I've always spent my time creating my own general purpose code (and now have a hugely better set than the STL) so I was always glad of the excuse not to have to use it in Xerces at the time, though it was really a legitimate concern back in those cave days. I'm not sure what the situation is now with support (and consistent support) of all the STL stuff on all those platforms.
We also were concerned that Xerces would be used on very small, embedded systems as well, not just small to large iron. I'm not sure what the situation is for such systems, though these days the small boards in such systems can have plenty of memory and power so it may not really be of concern. ------------------------------------- Dean Roddey Chairman/CTO, Charmed Quark Systems [EMAIL PROTECTED] www.charmedquark.com -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Saturday, February 12, 2005 10:42 AM To: xerces-c-dev@xml.apache.org Subject: Re: The Road to 3.0 Hi Gareth, > I should have read this mail before replying! It was certainly > the > case in the past the some of the platforms that xerces supported did > not have decent STL support. Has this now changed? Dean knew all the > issues if I recall correctly and does sometimes lurk on the list. Are > you out there Dean? Well, some of the very oldest compilers would still be problematic, but they are much rarer now. I worked on an internal IBM build of Xalan-C on about 14 different compiler/platform/word-size combinations and all we needed were a few minor source code tweaks (some of which weren't related to the collection classes) and some updates to the compiler options for the new compilers. That said, pulling in the template collection classes from the standard library will make the code less portable. Plus, it would break Xerces-C pluggable memory management, which probably make it a non-starter. Dave --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
