> > The crude, but effective, hack above extends the range of "c" so that
> > it doesn't overflow in this case -- however, not all platforms may
> > support the int64_t type yet.
>
> What about just using 'unsigned int' instead of 'int64_t'?
To successfully print a value greater than 1 billion, c needs to
contain 10 billion. that won't fit in an unsigned 32 bit value.
>
> > It might make more sense, however, to rework the macros to use
> > sprintf() or snprintf() instead.
>
> Well...yeah...but you still have to worry about cross-platform support
> (unless we have our own snprintf() in nmh).
There are portable open-source snprintf implementations out there, so
this shouldn't be an obstacle.
- Bill
