[FFmpeg-cvslog] r10970 - trunk/doc/faq.texi

[Ramiro Polla]

diego wrote:
> Author: diego
> Date: Fri Nov  9 15:05:43 2007
> New Revision: 10970
> 
> Log:
> Clarify Visual Studio FAQ.
> 
> 
> Modified:
>    trunk/doc/faq.texi
> 
> Modified: trunk/doc/faq.texi
> ==============================================================================
> --- trunk/doc/faq.texi	(original)
> +++ trunk/doc/faq.texi	Fri Nov  9 15:05:43 2007
> @@ -360,10 +360,10 @@ It depends. If your compiler is C99-comp
>  it are likely to be welcome if they do not pollute the source code
>  with @code{#ifdef}s related to the compiler.
>  
> - at section Microsoft Visual C++ produces many errors.
> + at section Is Microsoft Visual C++ supported?
>  
> -Microsoft Visual C++ is not compliant to the C standard and does not support
> -the inline assembly used in FFmpeg.
> +No. Microsoft Visual C++ is not compliant to the C99 standard and does
> +not - among other things - support the inline assembly used in FFmpeg.
>  If you wish - for whatever weird reason - to use MSVC++ for your
>  project then you can link the MSVC++ code with libav* as long as
>  you compile the latter with a working C compiler. For more information, see
> @@ -372,7 +372,7 @@ documentation.
>  
>  There have been efforts to make FFmpeg compatible with MSVC++ in the
>  past. However, they have all been rejected as too intrusive, especially
> -since MinGW does the job perfectly adequately. None of the core developers
> +since MinGW does the job adequately. None of the core developers

I liked that "perfectly" there. It was funnier that way =)

What I don't like though is "- for whatever weird reason -". Ok to apply 
attached patch?

Ramiro Polla
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: msvc.diff
URL: <http://lists.mplayerhq.hu/pipermail/ffmpeg-cvslog/attachments/20071109/0b8d19fc/attachment.txt>