[Ffmpeg-devel] [PATCH] Correct inttypes.h emulation for VisualStudio

Michael Niedermayer michaelni
Mon Dec 4 11:57:04 CET 2006


On Mon, Dec 04, 2006 at 11:42:22AM +0100, Axel Holzinger wrote:
> > As long as you think that people who disagree with you on technical
> > matters are actively engaging in 'hate', you are in for an emotionally
> > painful engineering career.
> I'm not convinced that it's a technical matter, at least IMHO not for those
> who don't care about the M$ users of lavc/lavf. I fully respect the FFMpeg
> team's decision to make gcc to their tool of choice, 

we dont, any C99 compiler is ok, and if you did respect what you think is our
decission you would stop trolling 

> but I don't see a
> technical reason to not offer a workaround (especially when somebody already
> offered a patch and most likely will be willing to change it until it fits
> for FFMpeg), that makes it possible to use the libs under windows. What is
> the technical reason to prohibit self definition of the integer types in
> case they aren't there?

there is no reason against "definition of the integer types in case they
aren't there" but there is a reason against duplicating this code in every
c program (just google for "code duplication" or something like that)

> And again I know that it's a M$ shortcoming (MSVC not supporting C99). But
> why does every windows FFMpeg user have to build his own inttypes.h instead
> of accepting a pragmatic patch? 

noone EVER proposed that, what was proposed was that _one_ person build a
inttypes.h for msvc and makes that available so everyone who builds any
C program depending on inttypes.h on MSVC can just download that and be

> What is the technical reason?

code duplication (inttypes.h duplicated in every C99 program) with the
resulting increased amount of bugs, maintaince, space, net bandwidth, ...

Michael     GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB

In the past you could go to a library and read, borrow or copy any book
Today you'd get arrested for mere telling someone where the library is

More information about the ffmpeg-devel mailing list