[FFmpeg-devel] [PATCH] [RFC] avoid _vscnprintf since it exists only since WinXP.

Derek Buitenhuis derek.buitenhuis at gmail.com
Sun Jul 22 21:59:05 CEST 2012

On 22/07/2012 3:53 PM, Reimar Döffinger wrote
>> Why? Do we really support OSes that MS doesn't even support anymore?
> Well, I see no reason not to try.

I think if it fills the code base with hacks or workarounds, or just
lots of extra code, it's a waste of effort to support an already
unsupported OS.

>> If someone is using Win2k, they're already using an unsupported OS that
>> things will likely not work on. Adding this sort of thing for such a
>> purpose is just silly.
> Well, it actually removes some code that seems completely unnecessary.
> To I believe the code would be nicer and simpler if it didn't rely on
> the vsnprintf return value at all, or at least used it only as a hint.

You're right on this point. Agreed.

>> "Bawwwwwww this binary won't work on my OS from 12 years ago that isn't
>> even supported by it's author!"
> There's no need to be insulting. Obviously people are still using it,
> and while I don't see them seriously complaining (reporting it seems
> very reasonable since the MSDN docs are wrong) that's no reason
> to not discuss simple solutions.
> And we do support e.g. OS/2, BeOS/Haiku and a lot of other stuff that
> I'm sure has fewer users than Win2k (there's a good chance there's
> actually fewer Linux users out there than people using a Windows before
> XP).

Sorry, I'll take off my troll hat. Reporting the doc issue to MS seems like
a fine idea, though I have a feeling they will not give much of a care.

I'm not against supporting things that few people use, but I am against
supporting things that its own author tells people not to use.

- Derek

More information about the ffmpeg-devel mailing list