Alright, if we have found a reason to keep XMLSize_t, as it appears that we have due to the behavior of the Windows libraries, then I would propose the opposite solution. Eliminate direct references to regular size_t so that there is only one kind of size_t in the code.
Comments? --Matt -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Friday, June 10, 2005 9:02 AM To: [email protected] Subject: Re: Need for XMLSize_t? > > Yes, I'm aware of what size_t and ptrdiff_t are, but that's not my > > real > > concern. I'm worried we are removing an existing typedef that > > users might > > have in their code, which means they will face modifying their > > code. Also, > > we might be changing the semantics of our code and their code without > > understanding the consequences. > > Yes, removing a typedef that will force changes in code is a valid > concern. I guess we have to weight that against the fact that we're > continuing to perpetuate an additional type, for which a standard > type already exists, and which may cause a need for additional casts, > etc, in using our code. I always hate doing something that breaks source-code compatibility, especially with a typedef. > As far as the semantics thing goes, I don't think there's a problem > as far as sizing, but I could be wrong ;) >From what I see on Windows, at least, XMLSize_t ends up being a typedef for unsigned long, rather than size_t, and that's why I was concerned. Thanks! Dave --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] ___________________________________________________________________ The information contained in this message and any attachment may be proprietary, confidential, and privileged or subject to the work product doctrine and thus protected from disclosure. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify me immediately by replying to this message and deleting it and all copies and backups thereof. Thank you. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
