Xerces defines XMLSize_t (to size_t, generally), and uses it in some
places. It also uses just a raw size_t in other places.
Since we seem to have been surviving fine with a plain size_t, I'd
like to suggest that we eliminate XMLSize_t in favor of size_t
everywhere in Xerces 3.0. This would eliminate a bit of required
configuration.
Any discussion?
-jdb
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
