Bob Friesenhahn <[EMAIL PROTECTED]> writes:
> What about defines like WORDS_BIGENDIAN? These certainly must appear
> in a configuration header file. It seems that the only protection is
> to surround them with #ifndefs. Even then, other packages may have
> conflicting usage.
I would say that as a library writer I should consider WORDS_BIGENDIAN
to be in the application name space and nothing I should define. And
I would tend to write the public header files such that endian-ness is
not relevant there. Or I would need to make that into
<LIBRARY>_WORDS_BIGENDIAN.
Why must WORDS_BIGENDIAN appear in a configuration header file? Sure,
it will appear in the config.h that configure generates for you when
building your library but you don't need to install it and you don't
need to offer it as a header for applications, do you?
/assar
