[FFmpeg-devel] [PATCH] remove MSVC-specific
Sun Mar 9 10:27:32 CET 2008
On Sun, Mar 09, 2008 at 01:04:33AM -0600, Brian Brice wrote:
> On Sat, Mar 8, 2008 at 3:40 PM, M?ns Rullg?rd <mans at mansr.com> wrote:
> > Michael Niedermayer <michaelni at gmx.at> writes:
> > > No, i was lucky and just had some volunteerly contact with MSVC
> > > which ended after a week or 2 of twice daily hard resets. That was
> > > maybe 10 years or so ago IIRC
Since the combination of Delphi + WinAMP caused regular crashes as well,
crashing must have actually been a much desired feature of development
programs back then.
I still have a CTRL+S -reflex (for saving the current file) from that
time... just proves that even back then IDEs still had a lot to learn
> > The situation hasn't improved.
> These flames are becoming pretty ridiculous and very childish. As
> someone that has successfully compiled ffmpeg with MSVC, and also uses
> mingw compiled libraries with MSVC projects, the stuff you are always
> trying to remove only become very bothersome for someone like me.
Well, since you did that you can surely answer if that stuff is even
necessary. Since MSVC can not compile the inline asm I don't know what
it would be good for...
> I know I'm not alone! I appreciate things like this available in the
> code already. I certainly don't appreciate the removal of these
> things because of your own personal grudges and ignorances.
Well, do you step up and maintain all the MSVC related lines, making
sure they still serve a sense and are correct? If no-one volunteers to
do that I too see no point in keeping them. Better something not there
than something that pretends to work but does not.
> I don't know you or know any of your experience, but I can guarantee
> you that MSVC has improved for the better in 10 years time. In my own
> opinion, I didn't like MSVC 6 very much (10 years ago), but thoroughly
> enjoy the current product. It's certainly a much better improvement
> from using the alternative, MinGW, in a Win32 environment.
I can't see much of a difference here. MSVC still does not include a
memory debugger, MinGW and MSVC share the same broken libc (which as I
had to find out provides no simple way of creating a temporary file,
tmpfile is completely broken for trying to create the file in the
filesystem root, mkstemp does not exist and the others suffer from race
conditions and difficulties of cleaning up e.g. when crashing that needs
loads of code to do correctly. As a result everyone does it
In addition MSVC offers a compiler with such stupidity as far and near
as keywords even though they probably have no effect since about a
> I really do like the ffmpeg project a lot and I appreciate the work
> that you guys and everyone else contributes. It's great that you guys
> prefer gcc as your compiler, but the flaming about other compilers
> (and other languages!) is getting to the point where it's
None of use claim to be professional here I think. But the flaming is no
surprise given how Microsoft absolutely refuses to fix even the simplest
And btw. going by what Microsoft themselves say, you should not use MSVC
for C code, it is only supposed to be used for C++ (yes, they say it in
a more obfuscated way, but still).
More information about the ffmpeg-devel