On 8/3/05, Robert P. J. Day <[EMAIL PROTECTED]> wrote:
>
> (i apologize if i asked this before once upon a time, i'm sort of
> immersed in digging through some legacy code and it's all starting to
> merge together.)
It's OK. You're welcome.
> in this legacy code, one of the previous authors took it upon
> himself to redefine some of the basic integral types, such as int8,
> int16, int32 ... that sort of thing.
Sounds weird, indeed, but I suspect the code to be pre-POSIX (before 1989).
> there doesn't appear to be any benefit to these internally redefined
> types over the ones in the standard library, so i can't see why it
> would have been done.
The only reason I could think of is that the developer wanted to
introduce some kind of portability by masking underlying types (and
probably their size) transparently. Is this particular piece of code
part of a library? Do the headers contain some #ifdefs to allow
conditional compilation for certain systems?
Regards
\Steve
-
To unsubscribe from this list: send the line "unsubscribe linux-c-programming"
in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
