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

[Ismail Dönmez]

On Sunday 13 May 2007 20:54:37 M?ns Rullg?rd wrote:
> Ismail D?nmez <ismail at pardus.org.tr> writes:
> > On Sunday 13 May 2007 20:37:19 Michael Niedermayer wrote:
> > [...]
> >
> >> > > 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.

They can do same with the extern "C" anyway, the point is what used to compile 
will not compile now as is. So removal of extern "C" just makes sense now.

/ismail


-- 
Perfect is the enemy of good
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.mplayerhq.hu/pipermail/ffmpeg-devel/attachments/20070513/69e84d19/attachment.pgp>