Outcurses

Line 7:

==Metric prefixes==

Not ncurses-related, but it's UI, so I stuck it here. Fed a <tt>uintmax_t</tt> (large enough to represent any unsigned integer type), a buffer, and a base (almost always 1000 or 1024), <tt>enmetric</tt> renders the number into the buffer such that the characteristic (material to the left of the decimal point) is less than the base. For numbers greater than the base, this means some metric suffix will be employed, and that the displayed number will have a mantissa (e.g. 1234 with a base of 1000 becomes 1.234K). Numbers through 2^89 are properly handled, using the suffixes Y, Z, E, P, T, G, M, and K. Use of base 1024 is necessary to properly employ the [https://en.wikipedia.org/wiki/Kibibyte metric units of digital information]. For instance, a "10 terabyte" hard drive typically has 10,000,000,000,000 (ten trillion) bytes, but 10 * 1,024 * 1,024 * 1,024 is 10,995,116,277,760 bytes aka 10 tibibytes. A kilobyte is 97.7% of a kibibyte, but a terabyte is only 91% of a tibibyte.

Not ncurses-related, but it's UI, so I stuck it here. Fed a <tt>uintmax_t</tt> (large enough to represent any unsigned integer type), a buffer, and a base (almost always 1000 or 1024), <tt>enmetric</tt> renders the number into the buffer such that the characteristic (material to the left of the decimal point) is less than the base. For numbers greater than the base, this means some metric suffix will be employed, and that the displayed number will have a mantissa (e.g. 1234 with a base of 1000 becomes 1.234K). Numbers through 2^89 are properly handled, using the suffixes Y, Z, E, P, T, G, M, and K. Use of base 1024 is necessary to properly employ the [https://en.wikipedia.org/wiki/Kibibyte metric units of digital information]. For instance, a "10 terabyte" hard drive typically has 10^13 == 10,000,000,000,000 (ten trillion) bytes, but 10 * 2^40 == 10 * 1,024 * 1,024 * 1,024 is 10,995,116,277,760 bytes aka 10 tibibytes. A kilobyte is 97.7% of a kibibyte, but a terabyte is only 91% of a tibibyte.

The necessary output buffer is a fixed size for a given base. For 1000, at most 7 <tt>chars</tt> are necessary:

Outcurses: Difference between revisions

Dank (talk | contribs)

@@ Line 7: / Line 7: @@
 ==Metric prefixes==
-Not ncurses-related, but it's UI, so I stuck it here. Fed a <tt>uintmax_t</tt> (large enough to represent any unsigned integer type), a buffer, and a base (almost always 1000 or 1024), <tt>enmetric</tt> renders the number into the buffer such that the characteristic (material to the left of the decimal point) is less than the base. For numbers greater than the base, this means some metric suffix will be employed, and that the displayed number will have a mantissa (e.g. 1234 with a base of 1000 becomes 1.234K). Numbers through 2^89 are properly handled, using the suffixes Y, Z, E, P, T, G, M, and K. Use of base 1024 is necessary to properly employ the [https://en.wikipedia.org/wiki/Kibibyte metric units of digital information]. For instance, a "10 terabyte" hard drive typically has 10,000,000,000,000 (ten trillion) bytes, but 10 * 1,024 * 1,024 * 1,024 is 10,995,116,277,760 bytes aka 10 tibibytes. A kilobyte is 97.7% of a kibibyte, but a terabyte is only 91% of a tibibyte.
+Not ncurses-related, but it's UI, so I stuck it here. Fed a <tt>uintmax_t</tt> (large enough to represent any unsigned integer type), a buffer, and a base (almost always 1000 or 1024), <tt>enmetric</tt> renders the number into the buffer such that the characteristic (material to the left of the decimal point) is less than the base. For numbers greater than the base, this means some metric suffix will be employed, and that the displayed number will have a mantissa (e.g. 1234 with a base of 1000 becomes 1.234K). Numbers through 2^89 are properly handled, using the suffixes Y, Z, E, P, T, G, M, and K. Use of base 1024 is necessary to properly employ the [https://en.wikipedia.org/wiki/Kibibyte metric units of digital information]. For instance, a "10 terabyte" hard drive typically has 10^13 == 10,000,000,000,000 (ten trillion) bytes, but 10 * 2^40 == 10 * 1,024 * 1,024 * 1,024 is 10,995,116,277,760 bytes aka 10 tibibytes. A kilobyte is 97.7% of a kibibyte, but a terabyte is only 91% of a tibibyte.
 The necessary output buffer is a fixed size for a given base. For 1000, at most 7 <tt>chars</tt> are necessary: