[FFmpeg-devel] [FFmpeg-cvslog] lavf: more correct printf format specifiers

Clément Bœsch u at pkh.me
Wed Mar 12 13:50:00 CET 2014

On Wed, Mar 12, 2014 at 12:42:31PM +0000, Derek Buitenhuis wrote:
> On 3/12/2014 12:33 PM, Nicolas George wrote:
> > $ gcc -E -dM -x c /dev/null | grep __UINT32_TYPE__
> > #define __UINT32_TYPE__ unsigned int
> Sorry, to clarify, int is only 32-bits on Windows64, so unsigned int is not strictly
> == to uint32_t on all platforms.

AFAIK only long has a different meaning between windows and the rest of
the world.

> As for James' earlier assertion, abusing platform-specific knowledge
> of what uint32_t is typedef'd as is a horrible idea, and all relevant
> specifications do indeed tell you to use PRIi32.

> I fail to see the point of Clement's complaint, as the result was indeed
> more correct.

I was just wondering what was going on since it was the only entry where
the format string were swapped.

Clément B.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 490 bytes
Desc: not available
URL: <http://ffmpeg.org/pipermail/ffmpeg-devel/attachments/20140312/169fd695/attachment.asc>

More information about the ffmpeg-devel mailing list