Stan Sieler writes:
> > There is an overwhelming majority of respondents that favor KB and MB to be
> > base 2 rather than base 10.  That is, 1KB = 2**10, 1MB = 2**20.
> > Consider it done.
>
> good!

Ditto.

> > There are several people who think that supplying both KB and MB on the
> > same line (,20 output) is redundant and wasteful.  Still under
>
> Me too!  At best, it's a useless waste of space.  At worst, the user
> will look at the two columns, and say: *WHY* is there a second column...
> is it measuring some *other* kind of space?  What's going on?

Ditto.

>  ACCOUNT=  SYS         GROUP=  OTHER
>  FILENAME  CODE   ------------LOGICAL RECORD------------ -------SPACE-------
>                     SIZE  TYP           EOF        LIMIT                # MB
>  TINY                80B  FA              1            1            0.004 MB
>  BIG               1024B  FA           1024         1023            1     MB
>
>
> Tip: the answer is: the last one.

Wrong.

Just say "NO" to decimal points for the same reason that you'd say "NO" to
commas, i.e. because the CI functions/expressions and standard numeric
conversion intrinsics (presently being used by programs that parse existing
:LISTFILE,2 output) won't handle decimal points or commas.  Decimal points or
commas increase the work required to convert ,2 parsers into ,20 parsers.

Regarding KB vs MB: if :LISTFILE,20 is primarily intended for use with very
large files, then MB is the best choice.  But if it's indended as a general
replacement for ,2 and will be used for both small and large files, then
KB is the better choice.
--
Mark Bixby                      E-mail: [log in to unmask]
Coast Community College Dist.   Web: http://www.cccd.edu/~markb/
District Information Services   1370 Adams Ave, Costa Mesa, CA, USA 92626-5429
Technical Support               Voice: +1 714 438-4647
"You can tune a file system, but you can't tune a fish." - tunefs(1M)