[Ffmpeg-devel] [PATCH] Remove "bufsize" OptionDef option

The Wanderer inverseparadox
Sun Sep 17 20:19:28 CEST 2006

Gary Corcoran wrote:

> The Wanderer wrote:
>> M?ns Rullg?rd wrote:

>>> It means 1024 when dealing with bytes.  When dealing with bits
>>> (as in bitrates), it's usually 1000.
>> I'm aware of this attempt to draw a line (or I am now, at any
>> rate), but I think I still stand by my statement; I see no
>> particular reason to change the meaning of the prefix just because
>> we've changed the magnitude of the unit.
> It's not the magnitude of the unit - it's the context.  As far as I'm
> concerned, when dealing with memory sizes, be they in RAM or on
> disk, K means 1024.  But dealing with bitrates, K means 1000.  I
> think that's the way most of us on this list think of these.

Yes, I'm aware of that. I was saying that that is *not* the case for me
- in referring to bitrates just the same as when referring to other
types of binary data, I believe that I think of K as being 1024.

However, I could probably stand having the meaning split in that way, as
long as we don't try to change the underlying terms - which, of course,
is precisely what those responsible for "kibi" etc. are trying to do.

> So what's wrong with having the command line interpretations be the
> same as the above?  That is, have the interpretation be context
> sensitive.  Yes, it doesn't lead to nice supposedly 'clean' code
> being able to interpret K in only one way - but so what?  Computers
> should cater to humans, not the other way around...


       The Wanderer

Warning: Simply because I argue an issue does not mean I agree with any
side of it.

Secrecy is the beginning of tyranny.

More information about the ffmpeg-devel mailing list