[Ffmpeg-devel] [PATCH] Correct inttypes.h emulation for VisualStudio
Sun Dec 3 23:10:20 CET 2006
On Sun, Dec 03, 2006 at 11:05:15PM +0100, Reimar D?ffinger wrote:
> On Sun, Dec 03, 2006 at 01:55:01PM -0800, Mike Melanson wrote:
> > Axel Holzinger wrote:
> > >Does this make any difference?
> > >
> > >Are you interested in over and over again beefing on M$? Or are you
> > >interested in ffmpeg being a marvellous portable library that pleases
> > >millions of users, yes also a lot of users that run it on M$ platforms?
> > Nice false dichotomy there. Not biting, though.
> > Simply put, engineering is about trade-offs, not perfect solutions.
> > We've chosen the set of trade-offs for FFmpeg that we're comfortable
> > with. That involves not directly support Microsoft operating systems.
> Hm. Well, that's probably a point, too. Though even more important IMO
> is that problems should be fixed where the bug is, not anywhere else.
yes, or in case that this is impossible the bug should be worked around
in such a way as to keep the workaround smallest and if possible closest
to the buggy part
here we have standard C vs MSVC, the bug is in MSVC which isnt going to
be fixed it seems
changing all standard C programs which use inttyles.h is not a solution
which is small and neither close to the bug
simply writing a inttypes.h for MSVC and making that available somewhere
with a windows-GUI installer or such would probably be the most sane
solution and would fix the inttypes-MSVC issue for all programs not just
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