[Ffmpeg-devel] [PATCH] Correct inttypes.h emulation for VisualStudio
Mon Dec 4 11:42:22 CET 2006
Mike Melanson wrote:
> To be fair, it wasn't until Axel chimed in with his incendiary,
> inflammatory flame that things really went downhill in this thread.
Mike, there seems to be quite a lot fuel around, for my message makes
everybody take fire.
> As long as you think that people who disagree with you on technical
> matters are actively engaging in 'hate', you are in for an emotionally
> painful engineering career.
I'm not convinced that it's a technical matter, at least IMHO not for those
who don't care about the M$ users of lavc/lavf. I fully respect the FFMpeg
team's decision to make gcc to their tool of choice, but I don't see a
technical reason to not offer a workaround (especially when somebody already
offered a patch and most likely will be willing to change it until it fits
for FFMpeg), that makes it possible to use the libs under windows. What is
the technical reason to prohibit self definition of the integer types in
case they aren't there?
And again I know that it's a M$ shortcoming (MSVC not supporting C99). But
why does every windows FFMpeg user have to build his own inttypes.h instead
of accepting a pragmatic patch? What is the technical reason?
But if it's not a technical matter, why then not telling whatever reason it
is (as there are ideology, religion, emotions,...)?
> Me? I do not actually have a technical opinion on the matter.
Okay, so what's your opinion based on?
> I was just
> enjoying the flame skirmish. For more authoritative and constructive
> ideas, revisit the thread items from before Axel got the flames rolling.
Was it in medieval times that they decapitated the bearer of a bad message
More information about the ffmpeg-devel