AuroraMiddleware/fmtlegacy
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Document chrono

Browse Source
This commit is contained in:
Victor Zverovich 2020-11-07 10:19:40 -08:00
parent 0506b328b5
commit 263bb0e68d
2 changed files with 13 additions and 14 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

19
doc/api.rst
View File

@ -415,18 +415,15 @@ For example::
#include <fmt/chrono.h>
int main() {
using namespace std::literals::chrono_literals;
fmt::print("Default format: {} {}\n", 42s, 100ms);
fmt::print("strftime-like format: {:%H:%M:%S}\n", 3h + 15min + 30s);
}
std::time_t t = std::time(nullptr);
// Prints "The date is 2020-11-07." (with the current date):
fmt::print("The date is {:%Y-%m-%d}.", fmt::localtime(t));
prints:
.. code:: none
Default format: 42s 100ms
strftime-like format: 03:15:30
using namespace std::literals::chrono_literals;
// Prints "Default format: 42s 100ms":
fmt::print("Default format: {} {}\n", 42s, 100ms);
// Prints "strftime-like format: 03:15:30":
fmt::print("strftime-like format: {:%H:%M:%S}\n", 3h + 15min + 30s);
Chrono format specifications are described in :ref:`chrono-specs`.

8
doc/syntax.rst
View File

@ -325,9 +325,11 @@ Literal chars are copied unchanged to the output. Precision is valid only for
``std::chrono::duration`` types with a floating-point representation type.
*conversion_spec* are conversion specifiers documented in `strftime
<http://en.cppreference.com/w/cpp/chrono/c/strftime>`_. Specifiers that have a
calendaric component such as `'d'` are valid only for ``std::tm`` and not
durations or time points.
<http://en.cppreference.com/w/cpp/chrono/c/strftime>`_ for ``std::tm`` and
in `Meaning of conversion specifiers <https://eel.is/c++draft/time.format>`
for chrono durations and time points. Specifiers that have a calendaric
component such as `'d'` are valid only for ``std::tm`` and not durations or time
points.
.. _formatexamples: