[Ffmpeg-devel] [PATCH] Correct inttypes.h emulation for Visual Studio
Tue Dec 5 13:04:26 CET 2006
Steve Lhomme said:
> M?ns Rullg?rd wrote:
>> Steve Lhomme said:
>>> Diego Biurrun wrote:
>>>> Portable programming is not accumulating special cases for every
>>>> imaginable combination of CPU architecture, operating system and
>>>> development environment.
>>> It is actually the case every time I saw portable code in the hardware
>>> industry. What you're talking about can probably be called compatibility
>>> (with all the flavors of a single OS: UNIX). Doing "portable" code
>>> usually involves having an abstraction layer for all the different
>>> architectures you want to support. And it's often put in "port"
>>> directories (one for each architecture).
>> I don't know where you've seen that "portable" code, but I'm sure I wouldn't
>> want to work there. Where I work, the exact same code compiles and runs on
>> a dozen different architectures, each with their own compiler and C library.
>> The low-level hardware drivers differ, that's all.
> Can you name all these "own" compiler, C library and architecture on
> which the same code is running ?
Architectures, most of them in more than one incarnation:
> Anyway, "hello world" should work fine on most platform (with a useful
> stdout) without requiring any OS/compiler specific tricks. It should be
> the case for any piece of code that doesn't need any hardware/low-level
> interaction. And libavcodec and libavformat fall into this category. The
> fact that it fails to be usable on some common compiler just proves that
> the code has some serious limitations.
It is not a "serious limitation" to require a compiler for the language the
code is written in. In the case of FFmpeg, the language is C99 with some
restrictions. Apparently, MSVC doesn't compile code in this language.
mru at inprovide.com
More information about the ffmpeg-devel