On 2001.07.01 14:36 Eugene Kuznetsov wrote:
> I believe that generally it is a third-party programmer responsibility to
> make a check for stdint.h. In this particular case I'll replace the
> construction. Do we have any more problematic places in headers?
I don't know that I agree with that - if they are using int64_t themselves
in their code, they'll know that they need to include stdint.h, but if they
are including a header that defines a structure they have a reasonable
expectation that said header will do the right thing automagically.
I still think it would be a good idea to use #include <avifile/...> to
avoid namespace pollution and to make sure we are grabbing the right
includes.
Note that I work as a tech support engineer, so my perspective is problem
avoidance.
--
Manuel A. McLure KE6TAW | ...for in Ulthar, according to an ancient
<[EMAIL PROTECTED]> | and significant law, no man may kill a cat.
<http://www.mclure.org> | -- H.P. Lovecraft
_______________________________________________
Avifile mailing list
[EMAIL PROTECTED]
http://prak.org/mailman/listinfo/avifile
