[Ffmpeg-devel] [PATCH] Partial port of ffmpeg to MS Visual C - and a note on the inttypes.h issue

Måns Rullgård mans
Thu Feb 8 11:24:13 CET 2007


Baptiste Coudurier said:
> Hi
>
> Yuri Vilmanis wrote:
>> [...]
>>
>> If you take a look at the C99 standard, you'll find under the library
>> summary (Annex B) that inttypes.h (Section B.7) is for "Format
>> conversion of integer types" and defines macros for integer type
>> conversions. stdint.h (Section B.7) is for "Integer types", and includes
>> all the type definitions for extended integers, including all types of
>> the form uintN_t and intN_t.
>>
>> [...]
>>
>> "4 For each type described herein that the implementation provides,218)
>> <stdint.h> shall declare that typedef name and define the associated
>> macros. Conversely, for each type described herein that the
>> implementation does not provide, <stdint.h> shall not declare that
>> typedef name nor shall it define the associated macros. An
>> implementation shall provide those types described as ??required??, but
>> need not provide any of the others (described as ??optional??)."
>
> [...]
>
>> [...]
>>
>> "3 These types are optional. However, if an implementation provides
>> integer types with widths of 8, 16, 32, or 64 bits, no padding bits, and
>> (for the signed types) that have a two?s complement representation, it
>> shall define the corresponding typedef names."
>>
>
> Does that would mean we are using an optional feature ? If that is the
> case IMHO we should reintroduce emulate inttypes.

We're not using any of the optional types, these being intptr_t, uintptr_t,
and specific size types with sizes other than 8, 16, 32 or 64 bits.

-- 
M?ns Rullg?rd
mans at mansr.com




More information about the ffmpeg-devel mailing list