[Ffmpeg-devel] [PATCH] Correct inttypes.h emulation for VisualStudio
Sun Dec 3 22:44:28 CET 2006
Uoti Urpala wrote:
> On Sun, 2006-12-03 at 23:55 +0300, Alexander Chemeris wrote:
> > As it is said in this article (chapter "64-Bit Programming in UNIX and
> > Windows"):
> > Unix and Windows use different headers for explicitly sized
> data types. And
> > even name this types different.
> int64_t etc are not "Unix" types, they're standard C types. So it's not
> a difference between Unix and Windows, but a difference between C and
> Microsoft's so-called "C" compilers which do not quite support C.
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?
What is it good for beefing on M$? Do you want them to change their
compilers? Do you think they will (because you are beefing)?
It is so childish and annoying to over and over again playing this ancient
Do you think all car designers still every day are beefing on the English
for having the steering wheel on the right (the wrong) side? How much
cheaper and easy could these cars be designed and built, if they all had the
wheel on the left (or if you want: all on the right) side?
I know that it is hard to cope with all this differencies of different
platforms, but ffmpeg did a very good job. And we are not talking about
ffmpeg to be compilable under MSVC. We are talking about lavc/lavf being
usable with MSVC.
Please bring yourselves to accept the world as it is, with all its faults
(many of them from M$).
ffmpeg is really rally great, but putting energy in beefing on M$ is so
childish and dropping all your windows users for sake of "but we support C99
and M$" is even more.
More information about the ffmpeg-devel