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

[Måns Rullgård]

The Wanderer <inverseparadox at comcast.net> writes:

> Panagiotis Issaris wrote:
>
>> Hi,
>> On zo, 2006-09-17 at 07:19 +0300, Uoti Urpala wrote:
>>
>>> On Sat, 2006-09-16 at 23:58 +0200, Michael Niedermayer wrote:
>>>
>>>> after thinking about this a little id suggest
>>>> 123E3 = 123 * 10^3 and 123P10 = 123 * 2^10 notation, this is also
>>>> almost supported by strtod
>>>> this would free KBM* which we could either drop or leave it at
>>>> the SI units
>>> IMO 5M / 5Mi is easier to use than 5E6 / 5P20.
>> I'd have to agree with that.
>
> But it also involves capitulating to the attempt to change the meaning
> of terminology, in the name of decreased imprecision. I'm normally all
> for being precise (ambiguity is one of my big bugaboos), but I find
> 'kibi' (etc.) to be simply abhorrent.

I can't stand them either.

> As far as I'm concerned, K/k/kilo as a prefix means 1024 when dealing
> with binary data of any type, and 1000 otherwise - period. (The

It means 1024 when dealing with bytes.  When dealing with bits (as in
bitrates), it's usually 1000.

> equivalent is naturally true of the corresponding greater prefixes. The
> capitalization either is irrelevant, or indicates whether we're dealing

In general, the capitalization is important.  With bits and bytes it
is less so, since a millibyte doesn't really make a lot of sense.

> with bytes or with bits.) Any software which enforces a different
> meaning is one I'm going to find highly irritating to use and be less
> favorably inclined towards than I might be - and, by virtue of the fact
> that I don't like feeling upset and resentful about things I can't do
> anything about, one I'm not going to want to even *think* about more
> than I can readily avoid.

I completely agree.

-- 
M?ns Rullg?rd
mru at inprovide.com