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

Steve Lhomme steve.lhomme
Tue Dec 5 12:30:32 CET 2006

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 ?

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.


More information about the ffmpeg-devel mailing list