2020-03-09 18:55:41 +01:00
|
|
|
.. namespace:: units
|
|
|
|
|
|
2020-03-26 17:09:26 +01:00
|
|
|
Text Output
|
2020-03-09 18:55:41 +01:00
|
|
|
===========
|
|
|
|
|
|
|
|
|
|
Beside providing dimensional analysis and units conversions, the library
|
|
|
|
|
also tries really hard to print any quantity in the most user friendly way.
|
|
|
|
|
|
2020-08-17 22:23:11 -04:00
|
|
|
.. note::
|
|
|
|
|
|
|
|
|
|
The library provides no text output for quantity points.
|
|
|
|
|
|
2020-03-26 17:09:26 +01:00
|
|
|
Output Streams
|
2020-03-09 18:55:41 +01:00
|
|
|
--------------
|
|
|
|
|
|
|
|
|
|
The easiest way to print a quantity is to provide its object to the output
|
|
|
|
|
stream::
|
|
|
|
|
|
2020-05-08 22:39:24 +02:00
|
|
|
using namespace units::physical::si::literals;
|
2020-09-10 17:14:33 +02:00
|
|
|
using namespace units::physical::si::international::literals;
|
2020-09-09 19:20:35 +02:00
|
|
|
constexpr Speed auto v1 = avg_speed(220._q_km, 2_q_h);
|
|
|
|
|
constexpr Speed auto v2 = avg_speed(140._q_mi, 2_q_h);
|
2020-03-09 18:55:41 +01:00
|
|
|
std::cout << v1 << '\n'; // 110 km/h
|
|
|
|
|
std::cout << v2 << '\n'; // 70 mi/h
|
|
|
|
|
|
|
|
|
|
The text output will always print the :term:`value of a quantity` followed
|
2020-03-19 09:35:18 +01:00
|
|
|
by a space and then the symbol of a :term:`unit` associated with this quantity.
|
2020-03-09 18:55:41 +01:00
|
|
|
|
2020-03-19 09:35:18 +01:00
|
|
|
.. important::
|
2020-03-09 18:55:41 +01:00
|
|
|
|
2020-03-19 09:35:18 +01:00
|
|
|
Remember that it is a good practice to always `quantity_cast()` a quantity
|
|
|
|
|
of an unknown ``auto`` type before passing it to the text output::
|
|
|
|
|
|
|
|
|
|
std::cout << quantity_cast<si::kilometre_per_hour>(v1) << '\n'; // 110 km/h
|
|
|
|
|
std::cout << quantity_cast<si::metre_per_second>(v1) << '\n'; // 30.5556 m/s
|
|
|
|
|
|
|
|
|
|
|
2020-03-26 17:09:26 +01:00
|
|
|
Stream Output Formatting
|
2020-03-19 09:35:18 +01:00
|
|
|
^^^^^^^^^^^^^^^^^^^^^^^^
|
|
|
|
|
|
|
|
|
|
Only a basic formatting can be applied for output streams. It includes control
|
|
|
|
|
over width, fill, and alignment::
|
|
|
|
|
|
2020-09-09 19:20:35 +02:00
|
|
|
os << "|" << std::setw(10) << 123_q_m << "|"; // | 123 m|
|
|
|
|
|
os << "|" << std::setw(10) << std::left << 123_q_m << "|"; // |123 m |
|
|
|
|
|
os << "|" << std::setw(10) << std::setfill('*') << 123_q_m << "|"; // |*****123 m|
|
2020-03-19 09:35:18 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
fmt::format
|
|
|
|
|
-----------
|
|
|
|
|
|
|
|
|
|
The **mp-units** via ``fmt::format`` provides a fine-grained control over what
|
|
|
|
|
and how is being printed on the text output.
|
2020-03-09 18:55:41 +01:00
|
|
|
|
|
|
|
|
|
2020-03-17 15:26:53 +01:00
|
|
|
Grammar
|
|
|
|
|
^^^^^^^
|
2020-03-09 18:55:41 +01:00
|
|
|
|
|
|
|
|
.. productionlist::
|
2020-03-18 12:17:12 +01:00
|
|
|
units-format-spec: [fill-and-align] [width] [units-specs]
|
2020-03-09 18:55:41 +01:00
|
|
|
units-specs: conversion-spec
|
|
|
|
|
: units-specs conversion-spec
|
|
|
|
|
: units-specs literal-char
|
|
|
|
|
literal-char: any character other than '{' or '}'
|
2020-03-18 12:17:12 +01:00
|
|
|
conversion-spec: '%' units-type
|
|
|
|
|
units-type: [units-rep-modifier] 'Q'
|
|
|
|
|
: [units-unit-modifier] 'q'
|
2020-03-18 12:53:41 +01:00
|
|
|
: one of "nt%"
|
2020-03-18 12:17:12 +01:00
|
|
|
units-rep-modifier: [sign] [#] [precision] [units-rep-type]
|
2020-03-18 12:53:41 +01:00
|
|
|
units-rep-type: one of "aAbBdeEfFgGoxX"
|
2020-03-18 12:17:12 +01:00
|
|
|
units-unit-modifier: 'A'
|
2020-03-17 15:26:53 +01:00
|
|
|
|
2020-03-18 12:53:41 +01:00
|
|
|
In the above grammar:
|
|
|
|
|
|
|
|
|
|
- ``fill-and-align``, ``width``, ``sign``, ``#``, and ``precision`` tokens and
|
|
|
|
|
individual tokens of :token:`units-rep-type` are defined in the
|
|
|
|
|
`format.string.std <https://wg21.link/format.string.std>`_ chapter of the C++
|
|
|
|
|
standard specification,
|
|
|
|
|
- tokens ``Q``, ``q``, ``n``, ``t``, and ``%`` of :token:`units-type` are described
|
|
|
|
|
in the `time.format <https://wg21.link/time.format>`_ chapter of the C++ standard
|
|
|
|
|
specification,
|
|
|
|
|
- ``A`` token of :token:`units-unit-modifier` forces ASCII-only output (instead of the
|
|
|
|
|
default Unicode symbols defined by the :term:`SI` specification).
|
2020-03-17 15:26:53 +01:00
|
|
|
|
2020-03-19 09:35:18 +01:00
|
|
|
|
2020-03-17 15:26:53 +01:00
|
|
|
Default formatting
|
|
|
|
|
^^^^^^^^^^^^^^^^^^
|
|
|
|
|
|
|
|
|
|
To format `quantity` values the formatting facility uses :token:`units-format-spec`.
|
|
|
|
|
In case it is left empty the default formatting of ``{:%Q %q}`` is applied. The same
|
2020-03-19 09:35:18 +01:00
|
|
|
default formatting is also applied to the output streams. This is why the following
|
|
|
|
|
code lines produce the same output::
|
2020-03-17 15:26:53 +01:00
|
|
|
|
2020-09-09 19:20:35 +02:00
|
|
|
std::cout << "Distance: " << 123_q_km << "\n";
|
|
|
|
|
fmt::print("Distance: {}\n", 123_q_km);
|
|
|
|
|
fmt::print("Distance: {:%Q %q}\n", 123_q_km);
|
2020-03-19 09:35:18 +01:00
|
|
|
|
|
|
|
|
|
2020-03-26 17:09:26 +01:00
|
|
|
Quantity Value, Symbol, or Both?
|
2020-03-19 09:35:18 +01:00
|
|
|
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
|
|
|
|
|
|
|
|
|
|
The user can easily decide to either print a whole quantity (value and symbol) or
|
|
|
|
|
only its parts. Also a different quantity formatting might be applied::
|
|
|
|
|
|
2020-09-09 19:20:35 +02:00
|
|
|
fmt::print("{:%Q}", 123_q_km); // 123
|
|
|
|
|
fmt::print("{:%q}", 123_q_km); // km
|
|
|
|
|
fmt::print("{:%Q%q}", 123_q_km); // 123km
|
2020-03-19 09:35:18 +01:00
|
|
|
|
|
|
|
|
|
2020-03-26 17:09:26 +01:00
|
|
|
Controlling Width, Fill, and Alignment
|
2020-03-19 09:35:18 +01:00
|
|
|
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
|
|
|
|
|
|
|
|
|
|
To control width, fill, and alignment the C++ standard grammar tokens ``fill-and-align``
|
|
|
|
|
and ``width`` are being used and they treat a quantity value and symbol as a contiguous
|
|
|
|
|
text::
|
|
|
|
|
|
2020-09-09 19:20:35 +02:00
|
|
|
fmt::print("|{:0}|", 123_q_m); // |123 m|
|
|
|
|
|
fmt::print("|{:10}|", 123_q_m); // | 123 m|
|
|
|
|
|
fmt::print("|{:<10}|", 123_q_m); // |123 m |
|
|
|
|
|
fmt::print("|{:>10}|", 123_q_m); // | 123 m|
|
|
|
|
|
fmt::print("|{:^10}|", 123_q_m); // | 123 m |
|
|
|
|
|
fmt::print("|{:*<10}|", 123_q_m); // |123 m*****|
|
|
|
|
|
fmt::print("|{:*>10}|", 123_q_m); // |*****123 m|
|
|
|
|
|
fmt::print("|{:*^10}|", 123_q_m); // |**123 m***|
|
2020-03-19 09:35:18 +01:00
|
|
|
|
|
|
|
|
|
2020-03-26 17:09:26 +01:00
|
|
|
ASCII-only Quantity Symbols
|
2020-03-19 09:35:18 +01:00
|
|
|
^^^^^^^^^^^^^^^^^^^^^^^^^^^
|
|
|
|
|
|
|
|
|
|
Unit symbols of some quantities are specified to use Unicode signs by the :term:`SI`
|
|
|
|
|
standard (i.e. ``Ω`` symbol for the resistance quantity). **mp-units** library follows
|
|
|
|
|
this by default. From the engineering point of view sometimes Unicode text might
|
|
|
|
|
not be a solution as terminals of many (especially embedded) devices are ASCII-only.
|
|
|
|
|
In such a case the unit symbol can be forced to be printed using ASCII-only characters::
|
|
|
|
|
|
2020-09-09 19:20:35 +02:00
|
|
|
fmt::print("{}", 10_q_R); // 10 Ω
|
|
|
|
|
fmt::print("{:%Q %Aq}", 10_q_R); // 10 ohm
|
|
|
|
|
fmt::print("{}", 125_q_us); // 125 µs
|
|
|
|
|
fmt::print("{:%Q %Aq}", 125_q_us); // 125 us
|
|
|
|
|
fmt::print("{}", 9.8_q_m_per_s2); // 9.8 m/s²
|
|
|
|
|
fmt::print("{:%Q %Aq}", 9.8_q_m_per_s2); // 9.8 m/s^2
|
2020-03-19 09:35:18 +01:00
|
|
|
|
|
|
|
|
|
2020-03-26 17:09:26 +01:00
|
|
|
Controlling on How the Quantity Value Is Being Printed
|
2020-03-19 09:35:18 +01:00
|
|
|
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
|
|
|
|
|
|
|
|
|
|
``sign`` token allows us to specify on how the value's sign is being printed::
|
|
|
|
|
|
2020-09-09 19:20:35 +02:00
|
|
|
fmt::print("{0:%Q %q},{0:%+Q %q},{0:%-Q %q},{0:% Q %q}", 1_q_m); // 1 m,+1 m,1 m, 1 m
|
|
|
|
|
fmt::print("{0:%Q %q},{0:%+Q %q},{0:%-Q %q},{0:% Q %q}", -1_q_m); // -1 m,-1 m,-1 m,-1 m
|
2020-03-19 09:35:18 +01:00
|
|
|
|
|
|
|
|
where:
|
|
|
|
|
|
|
|
|
|
- ``+`` indicates that a sign should be used for both non-negative and negative numbers,
|
|
|
|
|
- ``-`` indicates that a sign should be used for negative numbers and negative zero only
|
|
|
|
|
(this is the default behavior),
|
|
|
|
|
- ``<space>`` indicates that a leading space should be used for non-negative numbers other
|
|
|
|
|
than negative zero, and a minus sign for negative numbers and negative zero.
|
|
|
|
|
|
|
|
|
|
``precision`` token is allowed only for floating-point representation types::
|
|
|
|
|
|
2020-09-09 19:20:35 +02:00
|
|
|
fmt::print("{:%.0Q %q}", 1.2345_q_m); // 1 m
|
|
|
|
|
fmt::print("{:%.1Q %q}", 1.2345_q_m); // 1.2 m
|
|
|
|
|
fmt::print("{:%.2Q %q}", 1.2345_q_m); // 1.23 m
|
2020-03-19 09:35:18 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
:token:`units-rep-type` specifies how a value of the representation type is being
|
|
|
|
|
printed. For integral types::
|
|
|
|
|
|
2020-09-09 19:20:35 +02:00
|
|
|
fmt::print("{:%bQ %q}", 42_q_m); // 101010 m
|
|
|
|
|
fmt::print("{:%BQ %q}", 42_q_m); // 101010 m
|
|
|
|
|
fmt::print("{:%dQ %q}", 42_q_m); // 42 m
|
|
|
|
|
fmt::print("{:%oQ %q}", 42_q_m); // 52 m
|
|
|
|
|
fmt::print("{:%xQ %q}", 42_q_m); // 2a m
|
|
|
|
|
fmt::print("{:%XQ %q}", 42_q_m); // 2A m
|
2020-03-19 09:35:18 +01:00
|
|
|
|
|
|
|
|
The above can be printed in an alternate version thanks to the ``#`` token::
|
|
|
|
|
|
2020-09-09 19:20:35 +02:00
|
|
|
fmt::print("{:%#bQ %q}", 42_q_m); // 0b101010 m
|
|
|
|
|
fmt::print("{:%#BQ %q}", 42_q_m); // 0B101010 m
|
|
|
|
|
fmt::print("{:%#oQ %q}", 42_q_m); // 052 m
|
|
|
|
|
fmt::print("{:%#xQ %q}", 42_q_m); // 0x2a m
|
|
|
|
|
fmt::print("{:%#XQ %q}", 42_q_m); // 0X2A m
|
2020-03-19 09:35:18 +01:00
|
|
|
|
|
|
|
|
For floating-point values the :token:`units-rep-type` token works as follows::
|
|
|
|
|
|
2020-09-09 19:20:35 +02:00
|
|
|
fmt::print("{:%aQ %q}", 1.2345678_q_m); // 0x9.e065152d8eae841p-3 m
|
|
|
|
|
fmt::print("{:%.3aQ %q}", 1.2345678_q_m); // 0x9.e06p-3 m
|
|
|
|
|
fmt::print("{:%AQ %q}", 1.2345678_q_m); // 0X9.E065152D8EAE841P-3 m
|
|
|
|
|
fmt::print("{:%.3AQ %q}", 1.2345678_q_m); // 0X9.E06P-3 m
|
|
|
|
|
fmt::print("{:%eQ %q}", 1.2345678_q_m); // 1.234568e+00 m
|
|
|
|
|
fmt::print("{:%.3eQ %q}", 1.2345678_q_m); // 1.235e+00 m
|
|
|
|
|
fmt::print("{:%EQ %q}", 1.2345678_q_m); // 1.234568E+00 m
|
|
|
|
|
fmt::print("{:%.3EQ %q}", 1.2345678_q_m); // 1.235E+00 m
|
|
|
|
|
fmt::print("{:%gQ %q}", 1.2345678_q_m); // 1.23457 m
|
|
|
|
|
fmt::print("{:%gQ %q}", 1.2345678e8_q_m); // 1.23457e+08 m
|
|
|
|
|
fmt::print("{:%.3gQ %q}", 1.2345678_q_m); // 1.23 m
|
|
|
|
|
fmt::print("{:%.3gQ %q}", 1.2345678e8_q_m); // 1.23e+08 m
|
|
|
|
|
fmt::print("{:%GQ %q}", 1.2345678_q_m); // 1.23457 m
|
|
|
|
|
fmt::print("{:%GQ %q}", 1.2345678e8_q_m); // 1.23457E+08 m
|
|
|
|
|
fmt::print("{:%.3GQ %q}", 1.2345678_q_m); // 1.23 m
|
|
|
|
|
fmt::print("{:%.3GQ %q}", 1.2345678e8_q_m); // 1.23E+08 m
|
2020-03-19 09:35:18 +01:00
|
|
|
|
|
|
|
|
|
2020-03-26 17:09:26 +01:00
|
|
|
Special Signs
|
2020-03-19 09:35:18 +01:00
|
|
|
^^^^^^^^^^^^^
|
|
|
|
|
|
|
|
|
|
Beside adding any list of regular characters as a separator between the value and the
|
|
|
|
|
symbol, it is possible to type a few special signs there too::
|
|
|
|
|
|
2020-09-09 19:20:35 +02:00
|
|
|
fmt::print("{:%Q_%q}", 123_q_km); // 123_km
|
|
|
|
|
fmt::print("{:%Q%t%q}", 123_q_km); // 123\tkm <tab>
|
|
|
|
|
fmt::print("{:%Q%n%q}", 123_q_km); // 123\nkm <new line>
|
|
|
|
|
fmt::print("{:%Q%% %q}", 123_q_km); // 123% km
|