[Ffmpeg-devel] Re: [PATCH] Partial port of ffmpeg to MS Visual C - and a note on the inttypes.h issue
Thu Feb 8 14:55:53 CET 2007
M?ns Rullg?rd wrote:
>> On the upside, as inttypes.h is required to include stdint.h, client
>> code including only inttypes.h still works as it should - hence why
>> its not a big deal to the gcc devs. On the other hand, just cos it
>> works don't mean it meets the standard; the standard clearly specifies
>> that these typedefs belong in stdint.h, which does not exist in gcc
>> (and gcc would tell you so if you tried to #include <stdint.h>).
> What are you rambling about? My gcc+glibc system has stdint.h, and
> has had for as long as can remember. Perhaps you should have another
> look at your own system.
There is a side issue of little relevance. What we're concerned with
here is a hosted implementation of C, and that includes compiler and
library, so you're right in talking about the combination of gcc and
glibc. When talking about a freestanding implementation, there's no
library, but there still are a few headers, including stdint.h, so you
could argue that those would belong to the compiler, and not the library.
But as ffmpeg relies on a hosted implementation the point is rather moot.
More information about the ffmpeg-devel