[FFmpeg-devel] [RFC] extern "C" usage
Sun May 13 20:05:36 CEST 2007
> >> > > I agree strongly with emoving them but I suspect this is
> >> > > controversial. C++ users do not like being reminded that using C
> >> > > libraries is a form of FFI and not native C++
> >> >
> >> > But we never cared about C++ users, did we? If I'm mistaken, and we
> >> > do, it's about time we stopped. I propose using a few C++ keywords
> >> > like new or class in the headers too. That should teach them.
> >> besides the "BOFH because we can" attitude what would we gain by
> >> adding new and class with the intent to break C++ applications?
> > C++ applications are already broken with the usage of INT64_C macro.
> Not true. All they have to do is #define some senselessly long macro
> before #including stdint.h.
Maybe I should write a simple FAQ/howto entry using ffmpeg in c
++/visualc? Anyone not capable enough to care with C from C++ code
should be helped with doing some quirks on our side (like the extern).
This just creates confusion.
More information about the ffmpeg-devel