[Ffmpeg-devel] Re: [PATCH] Partial port of ffmpeg to MS Visual C - and a note on the inttypes.h issue

François Revol revol
Thu Jan 25 20:57:38 CET 2007

> Yuri Vilmanis wrote:
> >  From the presence of declarations such as
> > 
> > #ifdef __cplusplus
> > extern "C" {
> > #endif
> > 
> > in your public headers, I infer that you want to support linkage to
> > ffmpeg libraries (libav*) from C++ programs. (If this inference is
> > incorrect, feel free to ignore the following)
> You must have had your fun already when you wrote your message, as 
> I'm
> sure you knew in advance that you'd not get much fun out of the 
> answers
> here. ;-)
> Your inference above is obviously wrong. Those source lines in the
> public headers are there for unexplained reasons, as there is nothing
> named C++ anywhere on the radar of the ffmpeg developers. As C is the

First, there is at least one C++ file in ffmpeg, even if it's only for 
BeOS audio support :D
Plus I know at least one C++ project that uses libav*.

> only programming language worth mentioning, and C99 is the one and 
> only
> standard, C++ must be an aberration in the mind of a few misguided
> non-real programmers. ;-)

An aberration that was used in BeOS in most userland parts and didn't 
prevent it to boot and be usable for everyday tasks.

So could you ALL please stop trolling in here about C++!
That's getting really annoying.
Not liking it doesn't allow you to bash it and try to disgust everyone 
from it.

> Of course if ffmpeg complied with C89, an outdated standard that has

Currently IIRC ffmpeg doesn't comply to any standard I know of, as it 
uses several gccisms, not mentionning gas stuff. So much for 
complaining about non-standard VC++.
I didn't say I liked VC++ though.

not in a good mood today.

More information about the ffmpeg-devel mailing list