[FFmpeg-devel] [RFC] extern "C" usage

[Måns Rullgård]

Michael Niedermayer <michaelni at gmx.at> writes:

> Hi
>
> On Sun, May 13, 2007 at 04:59:23PM +0100, M?ns Rullg?rd wrote:
>> Rich Felker <dalias at aerifal.cx> writes:
>> 
>> > On Sun, May 13, 2007 at 04:35:26PM +0200, Alex Beregszaszi wrote:
>> >> Hi,
>> >> 
>> >> some headers are enclosed into extern "C" { }, while others are not.
>> >> Such is aes.h.
>> >> 
>> >> When using ffmpeg libs in a C++ application this brings a confusion, as
>> >> you need to enclose some headers with it, while others not.
>> >> 
>> >> To solve this, I propose to remove all the extern "C" occurances in
>> >> FFmpeg and let this job be done by the developers of C++ applications.
>> >> The other solution would be adding these to the headers which are
>> >> missing it.
>> >
>> > 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?

I wasn't being completely serious...

-- 
M?ns Rullg?rd
mans at mansr.com