> 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.
We should be careful to understand the implications of this before we do it. For example, in the Windows 64-bit model, size_t is 64 bits, but unsigned long is 32-bits. How will that affect users' code, and will it unnecessarily bloat the size of the DOM instances on some platforms? But I do agree that its use is pretty much limited to the DOM, and I don't quite understand the purpose of it, or all of the preprocessor macro definitions (_SIZE_T, SIZE_MAX, etc.) that go along with it. Thanks! Dave --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
