[Ffmpeg-cvslog] CVS: ffmpeg/doc faq.texi, 1.22, 1.23 ffmpeg-doc.texi, 1.92, 1.93

Rich Felker dalias
Thu Sep 29 16:49:43 CEST 2005

On Thu, Sep 29, 2005 at 12:34:04AM +0200, Alexander Strasser wrote:
> > + at item Write the source code for your application, or, for testing, just
> > +copy the code from an existing sample application into the source file
> > +that Visual C++ has already created for you. (Note that your source
> > +filehas to have a @code{.cpp} extension; otherwise, Visual C++ won't
> > +compile the FFmpeg headers correctly because in C mode, it doesn't
> > +recognize the @code{inline} keyword.)  For example, you can copy
> > + at file{output_example.c} from the FFmpeg distribution (but you will
> > +have to make minor modifications so the code will compile under
> > +C++, see below).
>   I could use the M$ C compiler without problems when eliminating
> the inline keyword by #defining it to nothing. Tho maybe it is not
> a good idea to mention it, i dunno atm.

Compiling C code as C++ is not acceptable. We should not recommend
such an ugly, broken (C is not a subset of C++!!) practice, but
instead the #define inline trick.


More information about the ffmpeg-cvslog mailing list