Re: 64 bit integers in Expat 2.0?

Well... not that the Windows API should stand as a stunning example of
clarity, but I believe they have two entries for a lot of functions (I
believe they nest, but not sure as I don't spend much time writing
non-portable code for specific OSes)... one for Unicode and one for
non-Unicode.

Maybe you combine two ideas...  have function names provide the return type
and optionally only include one set of names or the other depending on some
build flag.  That way old code doesn't break, new code can use the new
functions, and eventually you could mark the old function names as
deprecated.  Since the problem you face is technically only in one
direction, you could remove the old function names in favour of new function
names, and optionally include a macro to "rename" the new functions so they
still appear present for old code.

And maybe I'm just babbling... being that I have never used those particular
API functions anyway...  ;-)


On 11/29/05, Karl Waclawek <[email protected]> wrote:
>
> Yes, that might be an option as well.
> It just doesn't feel "right" for me to add four new alternative API
> members
> when the original ones aren't used that often. API bloat?
>