Put Visual C++ question in a better location.

Originally committed as revision 7827 to svn://svn.ffmpeg.org/ffmpeg/trunk

doc/faq.texi

@@ -261,6 +261,21 @@ It depends. If your compiler is C99-compliant, then patches to support
 it are likely to be welcome if they do not pollute the source code
 with @code{#ifdef}s related to the compiler.
 
+@section Visual C++ produces many errors.
+
+Visual C++ is not compliant to the C standard and does not support
+the inline assembly used in FFmpeg.
+If you wish - for whatever weird reason - to use Visual C++ for your
+project then you can link the Visual C++ code with libav* as long as
+you compile the latter with a working C compiler. For more information, see
+the @emph{Visual C++ compatibility} section in the FFmpeg documentation.
+
+There have been efforts to make FFmpeg compatible with Visual C++ 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
+work with Visual C++ and thus this item is low priority. Should you find
+the silver bullet that solves this problem, feel free to shoot it at us.
+
 @section Can I use FFmpeg or libavcodec under Windows ?
 
 Yes, but the MinGW tools @emph{must} be used to compile FFmpeg. You
@@ -299,21 +314,6 @@ the whole libav*. If you wish, disable some parts with configure switches.
 You can also try to hack it and remove more, but if you had problems fixing
 the compilation failure then you are probably not qualified for this.
 
-@section Visual C++ produces many errors.
-
-Visual C++ is not compliant to the C standard and does not support
-the inline assembly used in FFmpeg.
-If you wish - for whatever weird reason - to use Visual C++ for your
-project then you can link the Visual C++ code with libav* as long as
-you compile the latter with a working C compiler. For more information, see
-the @emph{Visual C++ compatibility} section in the FFmpeg documentation.
-
-There have been efforts to make FFmpeg compatible with Visual C++ 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
-work with Visual C++ and thus this item is low priority. Should you find
-the silver bullet that solves this problem, feel free to shoot it at us.
-
 @section I have a file in memory / a API different from *open/*read/ libc how do i use it with libavformat ?
 
 You have to implement a URLProtocol, see libavformat/file.c in FFmpeg