3431172fa8
It turns out that units(1) is not as horrible to use in scripts as I initially thought. When the --terse flag is combined with an appropriate output format (set via --output-format), units(1) is actually capable of producing very nice results. For example: units -o %0.f -t '4 gigabytes' bytes is is just going to print out the expected value of 4294967296. There is no time to waste. People have to know about it. I am adding an example for this at the top of the examples section because this is what users are most likely looking for. Approved by: bcr (mentor) Differential Revision: https://reviews.freebsd.org/D24096 |
||
---|---|---|
.. | ||
tests | ||
definitions.units | ||
Makefile | ||
Makefile.depend | ||
README | ||
units.1 | ||
units.c |
# $FreeBSD$ This is a program which I wrote as a clone of the UNIX 'units' command. I threw it together in a couple days, but it seems to work, with some restrictions. I have tested it under DOS with Borland C and Ultrix 4.2, and SunOS 4.1. This program differs from the unix units program in the following ways: it can gracefully handle exponents larger than 9 in output it uses 'e' to denote exponentiation in numbers prefixes are listed in the units file it tries both -s and -es plurals it allows use of * for multiply and ^ for exponentiation in the input the output format is somewhat different Adrian Mariano (adrian@cam.cornell.edu or mariano@geom.umn.edu)