Rename "time" -> "timestamp" (terminology)
authorPhilippe Proulx <eeppeliteloop@gmail.com>
Mon, 21 Sep 2020 21:04:36 +0000 (17:04 -0400)
committerPhilippe Proulx <eeppeliteloop@gmail.com>
Mon, 21 Sep 2020 21:07:40 +0000 (17:07 -0400)
commit462e49b3ce00ebc92ff1829391470697c6475ebb
tree71ea3bec94b2ee60032f693d68031579c2098d95
parent313a0bd9517a61b4e943cb060f751a2974f6a603
Rename "time" -> "timestamp" (terminology)

This patch renames the "time" concept to "timestamp" throughout.

The term "timestamp" is better to describe what used to be named "time",
for example a packet's beginning and end timestamps, and an event
record's timestamp.

"Time" has many definitions, one of which is duration, whereas the
only definition of "timestamp" in Antidote 10 is:

> a printed or stamped mark indicating a time or date of an event

which is pretty accurate.

Which is also why the timestamp members are named `timestamp_begin`,
`timestamp_end`, and `timestamp` in CTF 1.8.

Signed-off-by: Philippe Proulx <eeppeliteloop@gmail.com>
barectf/cgen.py
barectf/config.py
barectf/config_parse_v2.py
barectf/config_parse_v3.py
barectf/schemas/config/3/config-pre-field-type-expansion.yaml
barectf/schemas/config/3/config.yaml
barectf/templates/c/barectf.c.j2
barectf/templates/c/barectf.h.j2
barectf/templates/c/serialize-write-time-statements.j2 [deleted file]
This page took 0.025223 seconds and 4 git commands to generate.